MuleSoft Certified Developer - Level 1 (Mule 4)

Using breakpoints

Checking RAML

By Deploying apps on production

Cannot do it

Attributes do not change.

Previous attributes are passed unchanged.

Attributes are replaced with new attributes from the HTTP Request response.

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

Email the owners of the API.

Create a new client application.

No additional steps needed.

Request access to the API in Anypoint Exchange.

Sync flow has no error handling of its own and subflow does.

Subflow has no error handling of its own and sync flow does.

Subflow is synchronous and sync flow is asynchronous.

No difference.

Exchange

Template

Example

Connector

import dw::core

Not needed

None of these

import core

-1

0

Null

Last value from flow

Payload

Attributes

Inbound Properties

Variables

Mule runtime

All APIs

Flow Designer

Exchange

To save the most recent records retrieved from a database to enable database caching.

To enable duplicate processing of records in a database.

To avoid duplicate processing of records in a database.

To delete the most recent records retrieved from a database to enable database caching.

200.1234 as string {format: ".0#"}

200.1234 as string as format: ".0#"

200.1234 as String {format: ".0#"}

200.1234 as String as format: ".0#"

Classloader isolation does not exist between the application, the runtime and connectors, and policies.

Classloader isolation exists between the application, the runtime and connectors, and policies.

None of these.

Classloader isolation partially exists between the application, the runtime and connectors, and policies.

Products

Code

SOAP services

Organizations

MINOR

PATCH

MAJOR

No change

Facilitates communication between third-party systems and Mule applications.

No use.

Offers connector end user support in a few aspects of Mule app design.

Enables the development of Anypoint Connectors.

An Object containing three Mule event Objects.

An Array of three Mule event Objects.

An Object containing three JSON payload Objects.

An array of three JSON payload Objects.

0.8

1

2

1.8

Patient with id 2021

All patients

No patients

Patients from year 2021

Implements line of business projects to enforce common security requirements.

Centrally manages partners and consultants to implement line of business projects.

Produces and manages API policies for line of business deployments

Creates and manages discoverable assets to be consumed by line of business developers.

Sync flow

Subflow

Async flow

Async sub flow

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

None of these.

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

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

API

API Portals

Mule Apps

API Fragments

Publish consume: Synchronous. Publish: Asynchronous.

Publish consume: Asynchronous. Publish: Synchronous.

Publish consume: Asynchronous. Publish: Asynchronous.

Publish consume: Synchronous. Publish: Synchronous.

None of these

Test Policies

Test API functions

Test RAML

#["Content-Type: " ++ attributes.headers.'content-type']

#["Content-Type: " ++ headers.'content-type']

#["Content-Type: " + headers.'content-type']

#["Content-Type: " + attributes.headers.'content-type']

headers

client-id

client-id-required

we do not specify in RAML

Enables API Manager to discover the published API on Anypoint Exchange.

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

Enables an API to be directly managed in API Manager.

Allows the Mule application to be automatically discovered on Anypoint Exchange.

Attributes

Payload

inboundProperties

Message

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

To design API RAML files in a graphical way.

To design and mock Mule application templates that must be implemented using Anypoint Studio.

To define API lifecycle management in a graphical way.

Array

Object

String

Map

If the architecture mandates.

It is up to the integration specialist.

Successful/retry logic for reliable messaging functionality.

It is part of agile methodology.

API Manager

The proxy created by API Manager

The Mule runtime's embedded API Gateway

Anypoint Access Control

function

fun

func

None of these

Non-persistent queue

Horizontal Scaling

VPN Mock Services

None of these

At most one

None of these

Depends

At least one

Serves as an API implementation.

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

Creates native connectors using a 3rd party Java library.

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

GET

PATCH

POST

PUT

Validation module's Is number operation

Filter module's Is number operation

None of these

Validation module's Is not a number operation

#[value]

#[vars]

#[var]

#[values]

The Batch Job scope stops processing all records

The second Batch Step scope is retried with the same data

All existing in-flight records are discardeed, but new records are still passed to the first Batch Step scope and processed.

The second Batch Step scope’s error is reversed and the repaired records are passed to the third Batch Step scpoe for processing.

Decrements the value by one.

Removes items from a list.

Increments the value by one.

Removes characters from a string.

Data layer

System layer

Process layer

Experience layer

None of these

Integration Apps

CloudHub Workers

Rest API

CloudHub worker

API Manager

Design Center

Exchange

An event source

RAML file

An event processor

Logger Component

Exchange

API Manager

Anypoint MQ

Within the API

Object

Array

String

Map

Runtime Manager

Exchange

API Notebook

API Designer

Minifies the size of value using encoding.

None of these.

Merges elements of two objects into a single object.

Merges elements of two lists (arrays) into a single list.

None of these

Runtime Manager Console

Integration Apps

CloudHub Workers

API is rapidly prototyped following AGILE methodology.

API follows the RESTful architecture.

API is designed first using an API specification for rapid feedback.

API has a mechanism to accept feedback and suggestions for improvement.

120000

10

100

1000

Set the watermark column to the login_date_time column

Set the target value to the last retrieved login_date_time value

Set the target value to the last retrieved user_id value

Set the watermark column to the user_id column

/orders/{PO5555}

/orders/order=PO5555

/orders?order=PO5555

/orders/PO5555

attributes.queryParams.dept

attributes.dept

message.queryParams.dept

vars.dept

The file is moved to a different folder

The file stays in the same folder unchanged

The file is renamed in the same folder

The file is deleted from the folder

Both are multi-threaded

Both are single-threaded

Batch Job is single-threaded and For Each is multi-threaded

For each is single-threaded and Batch Job is multi-threaded

fun newProdCode(itemID: Number, productCategory: String) = "PC?" ++ productCategory ++ (itemID as String)

var newProdCode(itemID: Number, productCategory: String) -> "PC-" ++ productCategory ++ (itemID as String)

fun newProdCode(itemID: Number, productCategory: String) -> "PC-" ++ productCategory ++ (itemID as String)

function newProdCode(itemID: Number, productCategory: String) = "PC-" ++ productCategory ++ (itemID as String)

A global element

The mule-artifact.json file

A flow attribute

The pom.xml file

required: false

optional: true

provided: false

mandatory: false

Modify the Mule application to use autodiscovery to register with API Manager

Deploy the Mule application behind a VPC and configure the VPC to connect to API Manager

Upload the Mule application’s JAR file to the API instance in API Manager

Register the same Mule application in Runtime Manager to connect to API Manager

Restart the API proxy to clear the API policy cache

Add new property placeholders and redeploy the API proxy

Add required headers to the RAML specification and redeploy the new API proxy

Add new environment variables and restart the API proxy

Inbound Properties

Variables

Attributes

Payload

#%RAML 1.0
title: Books

Book: BookDataType.raml

/books:
post:
body:
application/json:
type: Book
examples:
input: BookExample.raml
responses:
201:
body:
application/json:
example:
message: Book added

#%RAML 1.0
title: Books

Book: !include BookDataType.raml

/books:
post:
body:
application/json:
type: Book
examples:
input: !include BookExample.raml
responses:
201:
body:
application/json:
example:
message: Book added

#%RAML 1.0
title: Books

types:
Book: ABC/DataTypes/BookDataType.raml

/books:
post:
body:
application/json:
type: Book
examples:
input: ABC/examples/BookExample.raml
responses:
201:
body:
application/json:
example:
message: Book added

#%RAML 1.0
title: Books

types:
Book: !include BookDataType.raml

/books:
post:
body:
application/json:
type: Book
examples:
input: !include BookExample.raml
responses:
201:
body:
application/json:
example:
message: Book added

API Specifications

Mule Applications

API Fragments

API Portals

Variable

Set Payload

Property

Record Variable

Attachment

In an attribute in the main mule element

In a Property Placeholder element

As a -M-D placeholder when starting the Mule runtime

In an attribute in the HTTP Listener element

Center for Enablement

Center of Excellence

Central API Review Board

MuleSoft Support Center

Performance tune and optimize the backend systems and network

Create an API specification and get feedback from stakeholders

Create a prototype of the API implementation

Gather a list of requirements to secure the API

RAML

JSON

WSDL

YAML

%dw 2.0
output application/json
import * from modules::MyModule
---
MyModule::formatString("annie point")

%dw 2.0
output application/json
import * from modules.MyModule
---
MyModule.formatString("annie point")

%dw 2.0
output application/json
import * from modules::MyModule
---
MyModule.formatString("annie point")

%dw 2.0
output application/json
import * from modules.MyModule
---
formatString("annie point")

1

2

4

8

attributes.bookISBN

flowVars.bookISBN

vars.bookISBN

bookISBN

mule-artifact.json

Pom.xml

mule-app.properties

global.xml

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

Create and manage high availability and fault tolerent services and infrastructure

Central IT delivers complete point-to-point solutions with master data management

Create and manage a collection of JMS messaging services and infrastructure

Java

JSON

XML

CSV

example: !include BankAccountsExample.raml

example: #import BankAccountsExample.raml

example: !include examples/BankAccountsExample.raml

example: #import examples/BankAccountsExample.raml

New outbound properties are added from the HTTP response headers

Previous outbound properties are passed through unchanged

Outbound properties are replaced with all the previous inbound properties

All previous outbound properties are removed

/departments:
/deptId:
patch:

/departments:
patch:
/deptId:

/departments:
patch:
queryParameters:
deptId:

/departments:
/{deptId}:
patch:

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.

Rate limiting

Throttling

Cross-origin resource sharing

LDAP security manager

RAML

WSDL

JSON

OAS

Remove the blank line on row 7

Enclose the {flight_id} resource in parentheses () instead of curly braces {}

Indent the get method under {flight_id} resource

Outdent the {flight_id} resource

${ssl.port}

${ssl.listener.port}

${https.listener.port}

${https.port}

8081

81

80

8080

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

Apply runtime policies to enforce governance

Measure the traffic flowing through to the API backend service

Determine which response message is allowed to pass back from the API backend service

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

#[attributes.uriParams.state]

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

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

#[state]

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

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

#[message.payload.inboundProperties].

#[message.inboundProperties.state]

Attachments

Outbound properties

Session variables

Payload

Inbound properties

Flow variables

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

It can have its own exception strategy

It is executed synchronously

An external client can send messages directly to it

It must be in the same configuration file as the parent flow

Queued-asynchronous

Synchronous

Non-blocking

Thread-per-processor

Queued-thread-per-processor

Put the Mule applications in the same Anypoint Platform environment

Put the Mule applications in the same Anypoint Platform business group

Put the Mule applications in the same non-default Mule domain

Put the Mule applications in the same default Mule domain

In two flow variables

As outbound properties

As inbound properties

In the message payload

As attachments

Set URI parameters in the HTTP Request component

Set inbound properties before the HTTP Request component

Set query parameters in the HTTP Request component

Set outbound properties before the HTTP Request component

To all exceptions whose conditions evaluate to true

To the first exception strategy whose condition evaluates to true

To the first exception strategy whose condition evaluates to true and to the default exception strategy

To the first exception strategy whose condition evaluates to true and to the global exception strategy

In a configuration global element in any Mule configuration XML file

In the mule-app.properties file

As an attribute of one or more flow configuration elements in one or more Mule configuration XML files

As an attribute of a global exception strategy

As a JVM system environment variable

To find the first true condition, then routes the message to that and all subsequent target message processors.

To select a set of target message processors to which to route the same message

To find the first true condition, then routes the message to the matched Choice target message processor

To select from the responses after routing the message to every Choice target message processor

An array of JSON objects

An array of array objects

An object that contains JSON objects

The last JSON object

The entire message is sent to each route and processed sequentially

The message is split and different pieces are routed and processed in parallel

The message is split and different pieces are routed and processed sequentially

The entire message is sent to each route and processed in parallel

The Mule application stops

The message is replayed from the start of the flow

The message is passed to subsequent message processors

All subsequent message processors are skipped

Is Number validator

Is Not Number validator

Is Number filter

Is Not Number filter

Outbound property

Inbound property

Payload

Attachment

Flow variable

Async scope

Message source

For Each scope

Message Enricher scope

In a session variable

In an outbound property

In an inbound property

In a flow variable

In a header

The file is moved to /mule/output

The file is deleted from the input directory, but is not moved anywhere

The file is moved to /tmp

The file stays in the input directory

Input

Load and Dispatch

Process Records

On Complete

The payload is changed to the modified payload

The modified payload is stored in a flow variable

The modified payload is stored as an inbound property

The payload returns to the original payload

The modified payload is stored as an outbound property

Continues to the third batch step

Stops processing the entire batch job

Retries the second batch step

Retries the first batch step

In a single batch step, but not in the other batch steps

In all batch steps, but not in the On Complete phase

In the message source, each batch step, and the On Complete phase

In all batch steps, and the On Complete phase

Deploy the API to a Maven repository

Enable autodiscovery in API Manager

Publish the API from inside flow designer

Publish the API to Anypoint Exchange

Message

Payload

OutboundProperties

Attributes

Creates a separate flow for each resource

Creates a separate flow for each resource that contains child resources

Creates a separate flow for each HTTP method

Creates one flow for the entire API spec

Creates a separate flow for each response status code

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

Previous attributes are passed 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]

#["Content-Type: " ++ attributes.headers.'content-type']

#["Content-Type: " + headers.'content-type']

#["Content-Type: " + attributes.headers.'content-type']

#["Content-Type: " ++ headers.'content-type']

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 seen 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 variable is accessible in childFlow but is immutable

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

The variable is NOT accessible in childFlow

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

error: ${env}.properties cannot be opened because it does not exist

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 Pro-perties 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

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

CloudHub workers CANNOT download ALL possible project dependencies a pro-ject may contain

CloudHub workers needs 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

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

As query parameters in the HTTP Request operation

As URI parameters in the HTTP Request operation

In the Mule 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

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