Explanation:
The First Successful router iterates through a list of configured processing routes until one of the routes executes successfully. This is sequential execution. In all other options mentioned in the question ,we can achieve parallel execution.

Explanation:
Lets revise few concepts RAML which can help us to find the answer of this question.
URI Parameters
Lets have a look at below example.
/foos:
/{id}:
/name/{name}:
Here, the braces { } around property names define URI parameters. They represent placeholders in each URI and do not reference root-level RAML file properties as we saw above in the base Uri declaration. The added lines represent the resources /foos/{id} and /foos/name/{name}.
Query Parameters
Now we'll define a way to query the foos collection using query parameters. Note that query parameters are defined using the same syntax that we used above for data types:
/foos:
get:
description: List all Foos matching query criteria, if provided; otherwise list all Foos queryParameters:
name?: string ownerName?: string
Based on the above information , below is the only option which defines storeid as uri parameter and department as query parameter.
/{storeId}:
get:
queryParameter:
department:

Explanation:
lookup(String, Any, Number)
This function enables you to execute a flow within a Mule app and retrieve the resulting payload. It works in Mule apps that are running on Mule Runtime version 4.1.4 and later.
Similar to the Flow Reference component (recommended), the lookup function enables you to execute another flow within your app and to retrieve the resulting payload. It takes the flow’s name and an input payload as parameters. For example, lookup("anotherFlow", payload) executes a flow named anotherFlow.
Correct answer is
lookup( "createCustomerObject", {first: "Aice, last: "Green"})

Explanation:
In this case three configurations will be required each for port 8000, 6000 and 7000. There would be three global elements defined for HTTP connections.
Each HTTP connection will have host and port.
To use an HTTP listener, you need to declare a configuration with a corresponding connection. This declaration establishes the HTTP server that will listen to requests. Additionally, you can configure a base path that applies to all listeners using the configuration.

Explanation:
Correct answer is 0.1 vCores
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:

Explanation: The List operation returns an array of messages in which: Each message holds the file’s content in its payload. The file’s attributes section carries the file’s metadata (such as name, creation time, and size). The payload is empty if the element is a folder.