Master the MuleSoft Certified Developer - Level 1 (Mule 4) MCD-Level-1 Exam with Confidence!

Option 1 is the only correct choice due to two reasons. 1) Concatenation is always with ++ sign and not with + sign which makes option 2 and 3 wrong 2) hearders can be accessed with attributes. headers and not with only headers which makes option 4 incorrect

Correct answer is async sub flow. Rest are valid flows in Mule.

Sub flow is always synchronous.

Only one of the routes in the Choice router executes, meaning that the first expression that evaluates to true triggers that route1 execution and the others are not checked. If none of the expressions are true, then the default route executes. Hence only Route1 will be executed as it is the first expression. hence output of logger is Route1.

MuleSoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.3/choice-router-concept

The Choice router dynamically routes messages through a flow according to a set of DataWeave expressions that evaluate message content. Each expression is associated with a different routing option. The effect is to add conditional processing to a flow, similar to an if/then/else code block in most programming languages.

Only one of the routes in the Choice router executes, meaning that the first expression that evaluates to true triggers that route’s execution and the others are not checked. If none of the expressions are true, then the default route executes.

Diagram Description automatically generated

Query parameters are a defined set of parameters attached to the end of a url. They are extensions of the URL that are used to help define specific content or actions based on the data being passed. To append query params to the end of a URL, a ‘?’ Is added followed immediately by a query parameter.

To add multiple parameters, an ‘&’ is added in between each.

Hence coming back to question, endpoint would return Patients with name as John and (and is very important here) surname as Bell

Correct answer is 0.1 vCores

MuleSoft Doc Ref : https://docs.mulesoft.com/runtime-manager/cloudhub-architecture#cloudhub-workers

CloudHub Workers

Workers are dedicated instances of Mule runtime engine that run your integration applications on CloudHub. The memory capacity and processing power of a worker depends on how you configure it at the application level.

Worker sizes have different compute, memory, and storage capacities. You can scale workers vertically by selecting one of the available worker sizes:

Table Description automatically generated