Pass the MuleSoft MuleSoft Certified Developer MCD-Level-1 Questions and answers with CertsForce

Correct answer is String is not blank.

-------------------------------------------------------------------------------------------------------------------------------------------------

Here’s specifically what is happening here:

1) Payload is successfully set to “Start”

2) The Is Blank String validator creates an Error Object because the payload is string "Start". Execution stops

#[error.description] = “String is not blank”

3) Because no error handler is defined, the Mule default error handler handles the error. Remember, at its heart, the Mule Default Error handler is an error handling scope with just an on error propagate

4) “String is not blank” is the error message returned to the requestor in the body of the HTTP requestHTTP Status Code: 500

Reference Diagram:

A picture containing diagram Description automatically generated

The correct answer is To avoid duplicate processing of records in a database.

If a watermark column is provided, the values taken from that column are used to filter the contents of the next poll, so that only rows with a greater watermark value are returned. If an ID column is provided, this component automatically verifies that the same row is not picked twice by concurrent polls.

Mule doc reference : https://docs.mulesoft.com/db-connector/1.8/database-documentation#listener

Correct answer is Add required headers to RAML specification and redeploy new API proxy

MuleSoft Doc Ref : https://docs.mulesoft.com/api-manager/2.x/tutorial-manage-an-api

Steps are as below :

Add the Required RAML Snippet

SLA-based rate limiting requires adding a RAML or OAS snippet to your API. This procedure demonstrates adding a RAML snippet.

Specify the client ID and secret as query parameters.

Add a section called traits: at the RAML root level to define query parameters:

traits:

- client-id-required:

queryParameters:

client_id:

type: string

client_secret:

type: string

Add the client-id-required trait to every method that requires these query parameters:

/users:

get:

is: [client-id-required]

description: Gets a list of JSONPlaceholder users.

Step 2 : Add the SLA Tier in API Manager

Step 3 : Apply the policy and redeploy

Scatter-Gather Router

The Scatter-Gather component is a routing event processor that processes a Mule event through different parallel processing routes that contain different event processors. Each route receives a reference to the Mule event and executes a sequence of one or more event processors. Each of these routes uses a separate thread to execute the event processors, and the resulting Mule event can be either the same Mule event without modifications or a new Mule event with its own payload, attributes, and variables. The Scatter-Gather component then combines the Mule events returned by each processing route into a new Mule event that is passed to the next event processor only after every route completes successfully.

The Scatter-Gather component executes each route in parallel, not sequentially. Parallel execution of routes can greatly increase the efficiency of your Mule application and may provide more information than sequential processing.

Mule Ref Doc : https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept

Scatter-Gather sends the event to each routes concurrently. Hence both route in this example will start in parallel. So total time to complete processing is 40 seconds

The Scatter-Gather component is a routing event processor that processes a Mule event through different parallel processing routes that contain different event processors. Each route receives a reference to the Mule event and executes a sequence of one or more event processors. Each of these routes uses a separate thread to execute the event processors, and the resulting Mule event can be either the same Mule event without modifications or a new Mule event with its own payload, attributes, and variables. The Scatter-Gather component then combines the Mule events returned by each processing route into a new Mule event that is passed to the next event processor only after every route completes successfully.

The Scatter-Gather component executes each route in parallel, not sequentially. Parallel execution of routes can greatly increase the efficiency of your Mule application and may provide more information than sequential processing.

Mule Ref Doc : https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept

API portal are created by API Exchange and cannot be created by Design Center

First step in creating Modern API is to create an API specification and get feedback from stakeholders so that any future issues can be identified at early stage thereby reducing overall delivery time