Free MCD-ASSOC sample questions

Correct answer: Anypoint VPN or VPC Peering

To connect a Mule application running in the public CloudHub to a private, on-premises resource like a database, a secure network extension is required. Anypoint VPN provides a secure IPsec tunnel between the Anypoint VPC and the private network. VPC Peering is an alternative for connecting to resources in another AWS VPC. Anypoint MQ is for messaging, and Object Store is for key-value storage; neither provides network connectivity.

Correct answer: An error is thrown because the `transactionId` variable is not in scope.

Variables created or modified within a batch step are local to that specific record's processing thread and are discarded once the record moves to the next step or finishes processing. They are not accessible in the On Complete phase. The On Complete phase only has access to the original payload that initiated the batch job and the final summary object.

Correct answer: An `On Error Continue` scope containing a Logger and a Set Payload component.

The `On Error Continue` scope is designed to handle an error and then allow the flow to continue as if it were successful. By placing a Logger inside this scope, the original error (`error` object) can be logged. Following the Logger, a Set Payload component can create the generic JSON error message. The flow then concludes successfully from the perspective of the HTTP Listener, which returns a 200 OK status by default. To return a 500, a Set Variable component should be used to set an 'httpStatus' variable to 500 within the error scope, which the HTTP Listener will then use.

Correct answer: /users/{userId}: uriParameters: userId: type: integer minimum: 1

In RAML, URI parameters are defined at the resource level where they appear. The correct syntax is to define the resource `/users/{userId}` and then, at the same indentation level, use the `uriParameters` facet. Inside this facet, you define the parameter `userId` and apply constraints like `type: integer` and `minimum: 1`.

Correct answer: As a flow variable

Flow variables are the standard mechanism for storing transient data within a flow. They are part of the Mule event but separate from the payload, allowing the main data to be processed independently. Unlike attributes, they are user-defined and mutable. Outbound properties are a deprecated concept from Mule 3.

Correct answers: Response Timeout; Connection Idle Timeout

The Response Timeout setting dictates the maximum time (in milliseconds) the connector will wait for a response after sending the request. This directly addresses the 5-second maximum response time requirement.

The Connection Idle Timeout setting specifies the maximum time a connection can remain idle in the connection pool before being closed. This prevents connections from being held open indefinitely, satisfying the second requirement.

Correct answer: An error in a subflow is passed to the calling flow's error handler, while an error in a private flow is handled by the private flow's own error handler.

Subflows do not have their own error handling scope. Any error occurring in a subflow is immediately passed to the error handler of the flow that called it. Private flows, like main flows, have their own processing strategy and error handling scope. If an error occurs and is not handled within the private flow, it is then re-thrown and can be caught by the calling flow.

Correct answer: Use the `filter` function to select the desired products first, and then use the `map` function on the result to create the XML structure.

The most idiomatic and efficient approach in DataWeave is to first reduce the dataset using the `filter` function based on the condition (`item.inStock == true`). Then, the `map` function is used on the smaller, filtered array to perform the structural transformation to XML. This avoids iterating over items that will be discarded.

Correct answer: Set the Scatter-Gather's timeout to 8 seconds and wrap each route in a Try scope with an On Error Continue handler.

Setting the Scatter-Gather's timeout to 8000ms ensures the router does not wait longer than 8 seconds. Wrapping each route in a Try scope with an On Error Continue handler allows a failing route to complete 'successfully' from the Scatter-Gather's perspective, returning an error object instead of failing the entire component. This allows the aggregation phase to proceed as long as the timeout is not reached, and the developer can then inspect the results to see which routes succeeded or failed.

Correct answer: False

The scheduler's execution is not guaranteed to be perfectly timed. Factors such as worker resource availability, thread contention, and the duration of the flow's execution can cause slight delays or 'jitter'. Furthermore, if the flow execution takes longer than the scheduled interval (e.g., 12 seconds), the next scheduled run might be skipped or delayed depending on the configured scheduling strategy. Therefore, it is not guaranteed to run exactly 6 times.