Mulesoft.U Development Fundamentals Trivia Training Quiz

Experience

Data

System

Process

Security

PATCH

PUT

POST

GET

Create reusable APIs and assets designed to be consumed by other business units

Creates and manages availability and fault tolerant services and infrastructure

Leverages Central IT to deliver complete point-to-point solutions with master data management

Creates and manages a collection of JMS messaging services and infrastructure

Creates and manages assets to be consumed by of business developers

Centrally manages partners and consultants to implement line of business projects

Implements line of business projects to enforce common security requirements

Produces & manages API policies for line of business deployments

API is designed first using an API specification for rapid feedback

API is rapidly prototyped following AGILE methodology

API follows the RESTful architecture

API has a mechanism to accept feedback and suggestions for improvement

GET Method api.php?action=search&query=einstein&format=xml AUTH

GET Method api.php?&query=einstein&format=xml AUTH

GET Method api.php?action=search&query=einstein&format=xml NO AUTH

POST Method api.php?action=search&query=einstein&format=xml AUTH

Design API RAML files in a graphical way

To design and Develop fully functional Mule applications in a hosted development environment

Define API lifecycle management in a graphical way

Design and mock Mule application templates that must be implemented using Anypoint Studio

Exchange

Clouhhub Worker

API Manager

Design Center

API Designer

API MUnit

Anypoint Exchange

API Notebook

API Specifications

Mule Applications

API Fragments

API portals

Inbound properties

Variables

Attributes

Payload

Deploy the API to a Maven repository

Enable autodiscovery in API Manager

Publish the API from inside flow designert

Publish the API to Anypoint Exchange

Http://dev.acme.com/patients?year=2016

Http://dev.acme.com/api/patients

Http://dev.acme.com/patients

Http://dev.acme.com/api/patients?year=2016

Example: !include BankAccountsExample.raml

Example: #import BankAccountsExample.raml

Example: !include examples/BankAccountsExample.raml

Example: #import examples/BankAccountsExample.raml

Remove blank line on row 9

Enclose flight_id with parenthesis () instead of curly braces {}

Indent the get method under the {flight_id} resource

Outdent the {flight_id} resource

Remove the curly braces {} around flight_id

Option 1

Option 2

Option 3

Option 4

Routes requests to API implementations, but does not validate them against RAML API specifications

Routes responses to the caller, but does not validate them against RAML API specifications

Validates requests against RAML API specifications and routes them to API implementations

Validates responses returned from API requests and routes them to the caller

An event processor/A message processor in the Process section of a flow

An event/message processor in the Source section of a flow

An empty flow

A message processor in both the Source and Process sections of a flow

Java

JSON

XML

CSV

Message

Payload

InboundProperties

Attributes

Creates a separate flow for each HTTP method

Creates a separate flow for each resource

Creates a separate flow for each resource that contains child resources

Creates one flow for the entire API spec

Creates a separate flow for each response status code

Enables API Manager to discover the published API on Anypoint Exchange

Allows the Mule application to be automatically discovered on Anypoint Exchange

Enables the API to be directly manage in API Manager

Allows a deployed Mule application to connect with API Manager to download policies and act as its own API proxy

At most one

At least one

Depends on the vCores

Depends on the number of CloudHub workers configured

Determine which request Mule event is allowed to pass through to the API backend service

Apply runtime policies to enforce governance

Determine which response Mule event is allowed to pass through to the API backend service

Measure the traffic flowing through the proxy

Anypoint Access Control

The proxy created by API Manager

API Manager

The Mule runtime’s embedded API Gateway

POST a JSON object to the /api/register endpoint of the API proxy

Request access to the API in Anypoint Exchange

Email the organization administrators to request access to the API

Add a client application to the Anypoint Platform organization

New attributes may be added from the HTTP response headers, but no headers are ever removed

New attributes may be added from the HTTP response, but previous attributes are passed through unchanged

Attributes do not change

Attributes are replaced with new attributes from the HTTP Request response (which might be null)

#[payload.images]

#[images]

#[flowVars.images]

#[vars.images] (vars is a DataWeave predefined variable)

#[message.payload.inboundProperties.'http.query.params’.state]

#[message.inboundProperties.'http.uri.params'.state]

#[attributes.uriParams.state]

#[attributes.’http.uri.params’.state]

#[state]

#[“Content-Type: “ ++ attributes.headers.’content-type’]

#[“Content-Type: “ + headers.’content-type’]

#[“Content-Type: “ + attributes.headers.’content-type’]

#[“Content-Type: “ ++ headers.’content-type’]

#[payload[2].city]

#[payload[1].city]

#[payload.city[1]]

#[payload.city[2]]

Message

OutboundProperties

Attributes

Variables

Payload

The variable is accessible. All the attributes passed to childFlow are removed or replaced

The variable is NOT accessible. All the attributes passed to childFlow are removed or replaced

The variable is NOT accessible. All the attributes passed to childFlow are preserved

The variable is accessible. All the attributes passed to childFlow are preserved

The variable is accessible in the server but is immutable

The variable is accessible in the server, can be changed, and changes are see back in parentFlow

The variable is NOT accessible in the server

The variable is accessible in the server, can be changed but changes are not seen back in parentFlow

The flow variable is accessible in childFlow but is immutable

The flow variable is accessible in childFlow, can be changed, and changes are seen back in parentFlow

The flow variable is NOT accessible in childFlow

The flow variable is accessible in childFlow, can be changed, but changes are NOT seen back in parentFlow

The property files were NOT saved at the root level of the deployable archive

The env property is NOT set in the Runtime Manager in the Mule application's Properties tab

A file named ${env}.properties is NOT included in the deployable archive file

The dev.properties and prod.properties files were NOT uploaded to Runtime Manager

${ssl.port}

${ssl.listener.port}

${https.listener.port}

${https.port}

The online logging service requires access to ALL project dependencies to log the appropriate Java classes used in the Mile application

CloudHub workers CANNOT download ALL possible project dependencies a project may contain

CloudHub workers need to compare the current dependencies with the LATEST project dependencies from the Mulesoft repository

Mulesoft support requires access to ALL project dependencies for future online troubleshooting

Mule-artifact.json

Pom.xml

Mule-app.properties

Global.xml

Preserve variables as the Mule event gets passed to another flow

Allow a flow to pass events to another flow synchronously

Preserve the original payload when the VM connector returns a response from a flow

Allow a flow to pass events to another flow asynchronously

RAML

WSDL

JSON

OAS

As query parameters in the HTTP Request operation

As URI parameters in the HTTP Request operation

In the Mule’s event’s payload

As flow variables

As attributes in a Transform Message component before the HTTP Request operation

As attributes in the HTTP Listener operation

Set Property

Build SOAP

Transform Message

JSON to XML

Set Attachment

Add the Account object metadata to the output and use the drag-and-drop feature to transform the incoming JSON data

Change the output type to the Java Account object type

Add the Account object metadata to the input and the Transform Message component will automatically convert the JSON objects to Account objects

Change the input type to the Java Account object type

Develop the API in flow designer and publish the API to Exchange

Design the API in Anypoint Studio and upload the API to Runtime Manager

Design the API In Design Center and publish the API to Exchange

Develop the API in Anypoint Studio and export the connector as a jar file

To find the FIRST true condition, then route the same event to the matched route and ALL FOLLOWING routes

To route the same event to the matched route of EVERY true condition

To find the FIRST true condition, then distribute the event to the ONE matched route

To filter and aggregate the responses after copying the event to EVERY route

An Object containing all three Mule event Objects

An array of three JSON payload Objects

An array of the three Mule event Objects

An Object containing all three JSON payload Objects

The last JSON payload Object

The last Mule event object

The ENTIRE event is sent to each route and processed SEQUENTIALLY

The event is SPLIT and different SMALLER events are routed and processed in PARALLEL

The event is SPLIT and different SMALLER events are routed and processed SEQUENTIALLY

The ENTIRE event is sent to each route and processed in PARALLEL

Validation module's Is number operation

Validation module's Is not number operation

Filter module's Is number operation

Filter module's Is not number operation

The flow silently stops processing its Mule event

The flow stops processing its Mule event and returns an error message to the HTTP Listener operation

The flow logs the error message in the console and continues processing its Mule event

The flow continues processing its Mule event and appends the error message to the end of the payload