MCD-Level-1 Exam Dumps - MuleSoft Certified Developer - Level 1 (Mule 4)

The flow can be described as below. 1) First HTTP POST requets is made in which paylaod is set to 1 and it gets returned to our mail flow. 2) Second call is initiated for JMS Publish Consume JMS: num1 which add 1 to the payload which makes it as 2. Note that pubih consume is a synchronous operation. Hence paylaod is returned to main flow. 3) Third call is initiated for JMS Publish JMS: num2 which add 1 to the payload . Note that pubih is asynchronous operation. Hence paylaod is never returned to main flow. So payload in main flow is still 2. 4) Finally Set Payload increments payload by 1 making payload as 3 which is returned by the flow. Hence option 3 is the correct answer.

Correct syntax to use where clause is WHERE city = :city AND state = :state

This question validates knowledge on using dynamic queries in DB select operation.

Configure Dynamic Queries in the Select Operation

When you need to parameterize not only the WHERE clause but also parts of the query itself (for example, queries that compare tables that depend on a condition, or complex queries for which the project table columns need to vary), you can configure dynamic queries.

In the following example, you configure a dynamic query by using a full expression with a string in which the table depends on a variable $(vars.table). Although some of the query text is dynamic ("SELECT * FROM $(vars.table)), the WHERE clause still defines the WHERE condition using input parameters: in this case, WHERE name = :name.

In your Studio flow, select the Select operation.

In the operation configuration screen, set the SQL Query Text field to SELECT * FROM $(vars.table) WHERE name = :name.

Set the Input Parameters field to {'name' : payload}.

The following screenshot shows the configuration in Studio:

Graphical user interface, application Description automatically generated

Figure 3. Dynamic query configuration

In the XML editor, the  configuration looks like this:

• #["SELECT * FROM $(vars.table) WHERE name = :name"]
• #[{'name' : payload}]

You can apply input parameters only to parameters in a WHERE clause. To modify any other part of the query, use the DataWeave interpolation operator.

Mule Ref Doc: Query a Database Examples - Mule 4 | MuleSoft Documentation

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

Setting Breakpoints

To set breakpoints, right-click a building block, then select Toggle Breakpoint.

Studio applies a red dot to the building block’s icon on the canvas.

When you run your application in Debug mode, Studio stops the flow execution at the breakpoint you have set, allowing you to check the Mule Event content in the Mule Debugger View.

Mule Ref Doc : Setting Breakpoints | MuleSoft Documentation

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

Pick First is not valid type. Rest all are valid type of event processor.

Choice : https://docs.mulesoft.com/mule-runtime/4.3/choice-router-concept

Round Robin : https://docs.mulesoft.com/mule-runtime/4.3/round-robin

First Successful : https://docs.mulesoft.com/mule-runtime/4.3/first-successful

In case of an error , batch job completes in flight steps and stops further processing.

MuleSoft Doc Ref : Handling Errors During Batch Job | MuleSoft Documentation

The default is all processing will stop but we can change it by Max Failed Record field.

General -> Max Failed Records: Mule has three options for handling a record-level error: Finish processing, Continue processing and Continue processing until the batch job accumulates a maximum number of failed records. This behavior can be controlled by Max Failed Records.

The default value is Zero which corresponds to Finish processing.

The value -1, corresponds to Continue processing.

The value +ve integer, corresponds to Continue processing until the batch job accumulates a maximum number of failed records