Pick First is not valid type.  Rest three are valid types of routers
Choice Router
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.
Round Robin Router
The Round Robin router iterates through a list of two or more routes in order, but it only routes to one of the routes each time it is executed. It keeps track of the previously selected route and never selects the same route consecutively. For example, the first time Round Robin executes, it selects the first route. The next time, it selects the second route. If the previously selected route is the last route in the list, Round Robin jumps to the first route.
First Successful Router
The First Successful router iterates through a list of configured processing routes until one of the routes executes successfully. If any processing route fails execution (throws an error), the router executes the next configured route. If none of the configured routes execute successfully, the First Successful router throws an error.

Validate Null Fails if the value is not null and not an instance of Null Payload.
The Validations module provides an easy out-of-the-box way to verify that the content of a message in your flow matches a given set of criteria.
The validations module was designed following these principles:
1) If the message doesn’t meet the specified criteria, the validation fails and a ValidationException is thrown.
2) By default, this exception has a meaningful message attached. You can optionally customize this message and change the type of exception thrown, as long as the new exception type has a constructor that overrides Exception(String).
Validate Null Fails if the value is not null and not an instance of Null Payload.

WSDL is used to define the contract in case of SOAP . RAML/OAS is used to define contract for REST services.
WSDL stands for Web Services Description Language. It is the standard format for describing a web service. WSDL was developed jointly by Microsoft and IBM.
Features of WSDL :
– WSDL is an XML-based protocol for information exchange in decentralized and distributed environments.
– WSDL definitions describe how to access a web service and what operations it will perform.
– WSDL is a language for describing how to interface with XML-based services.
– WSDL is an integral part of Universal Description, Discovery, and Integration (UDDI), an XML-based worldwide business registry.
– WSDL is the language that UDDI uses.

Correct answer is client-id-required
When applying a client ID-based policies implies that all requests coming to your API include a client ID and client Secret (by default expected as query parameters). To prevent user requests from being rejected, create a trait in the RAML root and then reference this trait in every operation of your API. The trait might look like this:
traits:
– client-id-required:
queryParameters:
client_id:
type: string
client_secret:
type: string
And then you can apply this trait in each individual operation like this:
/products:
get:
is: [client-id-required]
description: Gets a list of all the inventory products.

API Gateway is responsible for below functions.
1) Determine which traffic is authorized
2) Meter the traffic
3) Logs transaction
4) Apply throttling and other policies (Not specifying. These are specified in API Manager)
Hence specify throttling , security and other policies is the correct answer here as it is not function of API Gateway

Application properties can be defined in .yaml or in .properties file

Debugger can be used to debug applications to see event data moving from one flow to other

Its primary function is to design and develop fully functional Mule applications in a hosted development environment
In Flow Designer, you create Mule applications to integrate systems into workflows. You create them as projects that have one or more flows
Overview of Flow Designer

Correct answer is Publish consume: Synchronous. Publish: Asynchronous.
Request and reply is a very common pattern between applications, thus the JMS connector provides the publish-consume operation specifically for that. The publish-consume operation lets you publish a message to any destination, and then wait for a reply on a different destination
For the cases where you need an asynchronous reply to the Message being sent, the JMS publish operation allows us to declare any reply-to destination. This destination will be communicated as a JMS Header to the consumer of the Message, and is the destination were we should expect a reply to be sent.

Metadata is stored in application-types.xml file located under src/main/resources

Correct answer is Array of Mule event objects
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.

Organization Administrators can approve/revoke/delete SLA tier access requests via API Manager only.

SLA Tiers are created in API Manager.
To add an SLA tier:
From the left menu in API Manager, click API Group.
Expand the API Group list and click the API Group instance to which you want to add the SLA tier.
From the left menu, click SLA Tiers and then click Add SLA tier on the details page.
The illustration shows the Add SLA tier window.

The APIkit Router is a key message processor that validates requests against the provided definition, enriches messages (for example by adding default values to the messages) and routes requests to a particular flow. Also, the Router raises errors messages if errors occurs while routing, validating or processing the user request.

Gold is not valid category for connector type.
Connectors fall into one of the following categories.
Community
MuleSoft or members of the MuleSoft community write and maintain the Community connectors. Connectors built by the community or MuleSoft are generally open-source, although each package may vary. Partner-built connectors may not be open-source. Contact the partner directly for more information. You do not need any special account or license to use a Community connector.
MuleSoft Certified
For MuleSoft Certified connectors are developed by MuleSoft’s partners and developer community and are reviewed and certified by MuleSoft. For support, customers should contact the MuleSoft partner that created the MuleSoft Certified connector.
Select
MuleSoft maintains Select connectors. Connectors included in the open source Mule distribution can be used by everyone, however support is only included in an Anypoint Platform subscription. To use all other Select Connectors and access support, you must have an active Anypoint Platform subscription.
Premium
MuleSoft maintains Premium connectors; you must have an active CloudHub Premium plan or an Enterprise subscription with an entitlement for the specific connector you wish to use.

Anypoint Studio Visual Debugger allows you to run your application in Debug mode, setting breakpoints to stop execution to check the contents of an event at a previously-specified event processor.
When debugging on your local machine, Studio Visual Debugger listens for incoming TCP connections on localhost port 6666. This port must be available on your machine. This means not blocked by a firewall or other security software.
If you plan to remotely debug an application running in an external Mule server, you will need connectivity between your machine and the server’s debug port, which by default is configured to 6666.
https://docs.mulesoft.com/studio/7.5/visual-debugger-concept

Correct answer is Creates reusable APIs and assets designed to be consumed by other business units.
Expectations from an application network as per Mulesoft are as follows
In order to serve the needs of the business and provide the benefits that organizations need to thrive in today’s connected, competitive environment, an application network must be:
› Clearly defined: A well-defined operating model enables the business to get the most value from the IT assets on the network.
› Broadly deployed: It empowers the whole organization not just IT — to discover and access the data and assets tofuel applications, reporting, analytics, business processes and automation.
› Accessible and modular: Every application is accessible and recomposable to fit the rapidly changing needs of the business.
› Seamless: Is a seamless network of applications, data sources, devices and APIs, whether in the cloud or on premises, home-grown or acquired.
› Elastic: The application network is elastic and can grow or shrink depending on the demands of its consumers.
› Scalable: It allows companies to introduce new applications more easily because the application network already defines how to access, expose and share new application data.
› Secure: It can be organized to reflect the security and governance constraints in a business of any size.
› Monitored end to end: Data running through the network can be tracked end-to-end, monitored and analyzed. The impact of a request from one node in the network can be traced back to all the other nodes that take part in that request. Analytical: The network understands dependencies between applications and can perform impact analyses on changes made to applications on the network. This gives organizations a real-time enterprise wiring diagram that can be inspected. Measurable: The value of an application network can be explicitly measured through a set of built-in KPIs that track reuse, utilization, adoption and redundancy.
› Organic growth and reuse: As the first applications are connected to the application, data and functionality is made available for reuse. IT and the business can plug in more applications over time. Each application adds more value to the network, more reusable building blocks for building applications, services, and business processes. The business and IT can use the existing assets to build new assets which are also made available through the application network.

Choice router finds the FIRST true condition, then distribute the event to the ONE matched route.
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.

PUT is the correct answer. PUT replaces the original version of the resource, whereas the PATCH method supplies a set of instructions to modify the resource

Entire event would be sent to each route in parallel.
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.
The following diagram details the behavior of the Scatter-Gather component:
1. The Scatter-Gather component receives a Mule event and sends a reference of this Mule event to each processing route.
2. Each of the processing routes starts executing in parallel. After all processors inside a route finish processing, the route returns a Mule event, which can be either the same Mule event without modifications or a new Mule event created by the processors in the route as a result of the modifications applied.
3. After all processing routes have finished execution, the Scatter-Gather component creates a new Mule event that combines all resulting Mule events from each route, and then passes the new Mule event to the next component in the flow.

All processing of the batch job stops is the correct answer.
Batch Processing Strategies for Error Handling
Mule has three options for handling a record-level error:
Finish processing (Default behavior) Stop the execution of the current job instance. Finish the execution of the records currently in-flight, but do not pull any more records from the queues and set the job instance into a FAILURE state. The On Complete phase is invoked.
Continue processing the batch regardless of any failed records, using the acceptExpression and acceptPolicy attributes to instruct subsequent batch steps how to handle failed records.
Continue processing the batch regardless of any failed records (using the acceptExpression and acceptPolicy attributes to instruct subsequent batch steps how to handle failed records), until the batch job accumulates a maximum number of failed records at which point the execution will halt just like in option 1.
By default, Mule’s batch jobs follow the first error handling strategy which halts the batch instance execution

fun is the correct answer.
You can define your own DataWeave functions using the fun declaration in the header of a DataWeave script. Sample is as below. —————————————- %dw 2.0 output application/json fun toUpper(aString) = upper(aString) — toUpper(“hello”)

Process section is must to get compiled. Process section must have one or more processors. Event source and error handling are optional areas.
Mule application is a sequence of Mule event processors. Mule event processors
Flow has three main areas
Source : Controls how a flow is triggered
Process  : This determines the business logic implementation
Error : Handling of errors

Project Object Model file that defines settings for a Maven project describing an application. It includes all settings necessary to build the application such as build plugin configurations. Note that the pom.xml exists on a per-project basis and is distributed along with a project.

One Cloudhub worker can host one Mule application only.
Applications on CloudHub are run by one or more instances of Mule, called workers. Each worker is a dedicated instance of Mule that runs your integration application.
The memory capacity and processing power of a worker depends on how you configure it at the application level.

Mule applications can be scaled vertically by changing worker size. Mule applications can be scaled horizontally by adding more workers.

Root element is always required while creating XML response in DataWeave transformation.
Without a single key to serve as a root node for XML output ,the transformation to XML will fail with a yellow warning (!) in the source code area. The warning message is Trying to output non-whitespace characters outside main element tree.
If you like, you can try to produce this warning on your own.

Correct answer is  dw::Core
This module contains core DataWeave functions for data transformations. It is automatically imported into any DataWeave script.
You can refer to below link to see the details functions included in Core module
DW::Core Module

Correct answer is As query parameters in the HTTP Request operation
In General > Request > Query Parameters, click the plus icon (+) to add a parameter to a request. Type a name and value for the parameter or use a DataWeave expression to define the name and value.

Correct answer is Array
Map operator returns an array that is the result of applying a transformation function (lambda) to each of the elements.
Iterates over items in an array and outputs the results into a new array.
Example
This example iterates over an input array ([“jose”, “pedro”, “mateo”]) to produce an array of DataWeave objects. The anonymous function (value, index) ? {index: value} maps each item in the input to an object. As {index: value} shows, each index from the input array becomes a key for an output object, and each value of the input array becomes the value of that object.
Source
%dw 2.0
output application/json
—
[“jose”, “pedro”, “mateo”] map (value, index) -> { (index) : value}
Output
[ { “0”: “jose” }, { “1”: “pedro” }, { “2”: “mateo” } ]

Correct answer is Not possible in Mule 4
You can call only flows from DataWeave using lookup function. Note that lookup function does not support calling subflows.

Correct answer is Attributes are replaced with new attributes from the HTTP Request response

Correct answer is Creates a separate flow for each HTTP method
APIKIt Creates a separate flow for each HTTP method.
The following graphics illustrate the APIkit scaffolding:
In Studio, the REST API APIkit project looks like this:
The five items illustrated here show:
1) The project files in the Package Explorer of Studio with the api.raml file under src/main/resources/api folder.
2) The main flow, with the APIkit Router.
3) APIkit Console
4) Error Handling
5) Generated flows for each resource method.
The generated minimal flows meets the communication operations required by a REST contract

Correct answer is 0.1 vCores
Each worker is a dedicated instance of Mule that runs your integration application. The memory capacity and processing power of a worker depends on how you configure it at the application level. Minimum size that can be specified is 0.1 vCore which has Heap Memory of 500 MB and Storage of 8 GB

Correct answer is API Portals
API portal are created by API Exchange and cannot be created by Design Center.
Below screenshot the artefacts we can create when we click on create new application button in design center

Mule event is correct answer. Mule event has two parts which are as follows
1) Message (which contains payload and attributes like headers and query/uri parameters
2) Variables

File is not updated when FTP read operations is performed. Hence the correct answer is The file stays in the same folder unchanged

Correct answer is Allows CloudHub to automatically change the HTTP port to allow external clients to connect to the HTTP Listener
This helps CloudHub to dynamically allocates a port at deployment time.
Configuration properties can be overwritten. The Mule runtime engine uses the following hierarchy to determine which properties take precedence if they have the same name. In this hierarchy, deployment properties are at the top, so they take precedence over the other types of properties
1) Deployment properties
2) System properties
3) Environment properties
4) Application properties (includes configuration properties, secure configuration properties, and other custom configuration properties)
5) Global Properties

Correct answer is A global element
When we create a configuration file , that file needs to added as Global Configuration file in Global element. A global element is a reusable object containing parameters that any number of elements in a flow can share. You reference a global element from Anypoint Connectors or components in your Mule application.

Correct answer is System Layer
System APIs provide a means for insulating the data consumers from the complexity or changes to the underlying backend systems.
In MuleSoft API-led this approach, the APIs are based on three distinct layers: System, Process, and Experience
System APIs – these usually access the core systems of record and provide a means of insulating the user from the complexity or any changes to the underlying systems. Once built, many users, can access data without any need to learn the underlying systems and can reuse these APIs in multiple projects.
Process APIs – These APIs interact with and shape data within a single system or across systems (breaking down data silos) and are created here without a dependence on the source systems from which that data originates, as well as the target channels through which that data is delivered.
Experience APIs – Experience APIs are the means by which data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source, rather than setting up separate point-to-point integrations for each channel. An Experience API is usually created with API-first design principles where the API is designed for the specific user experience in mind.

Correct answer is Save the payload from the Database SELECT operation to a variable
Response from HTTP request will override the payload and hence response of database SELECT can be lost. Best way to preserve is to assign payload of first operation to variable using TransformMessage.
To achieve this
1) In the Transform Message properties view, click the Add new target button.
2) In the Selection dialog box, change the output to Variable.
3) Set Variable name to DWoutput and click OK
4) Click the drop-down menu for the output; you should see that you can switch between the two transformations. You can switch to variable to save data to it.

Correct answer is An Object containing all three Mule event Objects
Scatter-Gather sends the event to each routes concurrently and returns a collection of all results.  Collection is an Object of Objects. Each object contains attributes and payload from each Mule event returned from a flow.
The following diagram details the behavior of the Scatter-Gather component:
The Scatter-Gather component receives a Mule event and sends a reference of this Mule event to each processing route.Each of the processing routes starts executing in parallel.
After all processors inside a route finish processing, the route returns a Mule event, which can be either the same Mule event without modifications or a new Mule event created by the processors in the route as a result of the modifications applied.
After all processing routes have finished execution, the Scatter-Gather component creates a new Mule event that combines all resulting Mule events from each route, and then passes the new Mule event to the next component in the flow.
Output looks like below.

Correct answer is Anypoint Visualizer
Anypoint Visualizer provides a real-time, graphical representation of the APIs, and Mule applications that are running and discoverable. It also displays third-party systems that are invoked by a Mule API, proxy, or application within your application network. The data displayed in the graph is dynamically updated and does not require prior configuration. Additionally, the data displayed is secure, as only users with the proper permissions can view the application network graph.

Center for Enablement is correct answer .It  is a cross-functional team ?typically staffed with members from central IT, line-of-business departments, and digital innovation teams ?charged with productizing, publishing, and harvesting reusable assets and best practices. In this case , app team would have checked first with Center for Enablement before developing their own API’s.Hence could have avoided re-work

Empty array is the correct answer as it is returned when no rows are matched

Correct answer is Publish the API to Anypoint Exchange
Anypoint Exchange makes this possible by making it discoverable in below ways 1) In private exchange for internal developers 2) In a public portal for external developers/clients

Correct answer is Modify the API implementation to use auto-discovery to register with API Manager
Configuring autodiscovery has two major benefits 1) IT allows a deployed Mule runtime engine (Mule) application to connect with API Manager to download and manage policies and to generate analytics data 2) Additionally, with autodiscovery, you can configure your Mule applications to act as their own API proxy.

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.
Correct answer is Create an API specification and get feedback from stakeholders

The current version of the RAML specification is 1.0

A global element is the correct answer. Global error handlers are to be created in global element .  Quick note to remember here is Global error handlers come in to picture only when there are no error handlers specified as flow level.
Below steps needs to be followed in order to set global error handler.
1) Click Global Elements to open Global Configuration Elements.
Global Elements is located below the Studio canvas.
2) In Global Configuration Elements, click Create to open the Choose Global Type dialog.
3. From the dialog, select Global Configuration -? Configuration, and then click OK to open the Configuration dialog.
4. From the select Configuration dialog, select allErrorHandler for the Default Error Handler field, and click OK.

Because the SLA based  policy is client ID-based, you need to set up the client ID and secret as query parameters. Add traits to RAML for enforcing the policies. Redeployment is required in order to implement it on the API.
Hence correct answer is Add required headers to RAML specification and redeploy new API proxy

Correct answer is Enables the development of Anypoint Connectors
The MuleSoft Anypoint DevKit, or simply DevKit, enables the development of MuleSoft Anypoint Connectors.
DevKit Features
Features DevKit provides:
– Visual design and implementation using Anypoint Studio with an Eclipse-based interface that simplifies – and speeds up development.
– Maven support.
– Connector packaging tools.
– Authentication support for multiple types of authentication, including OAuth and username and password authentication.
– DataSense support to acquire remote metadata.
– Extensive testing capability.
– Examples, training, and support to simplify development startup.
– Batch, Query Pagination, and DataSense Query Language support.
DevKit is a annotations-based tool, with a wide set of available annotations to support its features. For a complete list of DevKit annotations, see the Annotation Reference.

API Exchange creates REST connector automatically once API is published. Hence correct answer is Publish the API specification to Any point Exchange

Correct answer is For Each is single-threaded and Batch Job is multi-threaded.
For Each Scope
The For Each scope splits a payload into elements and processes them one by one through the components that you place in the scope. It is similar to a for-each/for loop code block in most programming languages and can process any collection, including lists and arrays. The collection can be any supported content type, such as application/json, application/java, or application/xml.
Batch Scope
Within a Mule application, batch processing provides a construct for asynchronously processing larger-than-memory data sets that are split into individual records. Batch jobs allow for the description of a reliable process that automatically splits up source data and stores it into persistent queues, which makes it possible to process large data sets while providing reliability.