Correct answer is A global element

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.

Steps to create 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

Graphical user interface, text, application, chat or text message Description automatically generated

3) From the dialog, select Global Configuration -→ Configuration, and then click OK to open the Configuration dialog.

Graphical user interface, text, application, email Description automatically generated

4) From the select Configuration dialog, select allErrorHandler for the Default Error Handler field, and click OK.

In this case as outbound call is made using HTTP: POST /child , all attributes will be replaced by this invocation. Hence query parameter will not be accessible at logger.

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

Empty array is returned when no rows are matched.

MuleSoft Doc Ref : https://docs.mulesoft.com/db-connector/1.9/database-connector-select

Correct answer is 200.1234 as String {format: ".0#"} . Rest all options are not syntactically correct.

String is the correct answer as XML is of an Object type String

Correct answer is Creates and manages discoverable assets to be consumed by line of business developers.

C4E does not get directly involved in projects.

This question validates you knowledge on Batch Processing. Before we analyze the question , lets revise a bit about batch filters.

Batch Filters

You can apply one or more filters as attributes to any number of batch steps.Imagine a batch job whose first batch step checks if a Salesforce contact exists for a record, and a second batch step that updates each existing Salesforce contact with new information. You can apply a filter to the second batch step to ensure it only processes records that didn’t fail during the first batch step.By having batch steps accept only some records for processing, you streamline the batch job so the Mule runtime engine can focus only on the relevant data for a particular batch step.

A batch step uses two attributes to filter records:

acceptExpression

acceptPolicy

Each batch step can accept one acceptExpression and one acceptPolicy attributes to filter records.

Use the acceptExpression attribute to process only records that evaluate to true; if the record evaluates to false, the batch step skips the record and sends it to the next one. In other words, the records with an accept expression that resolves to false are the ones that Mule filters out.

The example below filters out all records where the age is less than 21; the batch step does not process those records.

• ...

Mule Ref Doc : Refining Batch Steps Processing | MuleSoft Documentation

As we are clear with above concepts , now lets understand this solution step by step.

1) Batch Step (Less than 50)

Accept expression for this batch step is less than 50. Hence elements which will go in this batch step are amount value 40 and 2. Hence output of logger in first batch step is

{amount=140}

{amount=102}

2) Batch Step (Greater than 20)

Accept condition for this batch step is greater than 20. Note that input amount values for this batch step are 100 , 140 and 102 (last two values have been updated in batch step less than 50)

As all values satisfy this condition out put of second logger is

{step2amount=100}

{step2amount=140}

{step2amount=102}

Hence correct answer to this question is

• {amount=140}
• {amount=102}
• {step2amount=100}
• {step2amount=140}
• {step2amount=102}

2) Batch Step (Greater than 20)

Accept condition for this batch step is greater than 20. Note that input amount values for this batch step are 100 , 140 and 102 (last two values have been updated in batch step less than 50)

As all values satisfy this condition out put of second logger is

{step2amount=100}

{step2amount=140}

{step2amount=102}

Hence correct answer to this question is

{amount=140}

{amount=102}

{step2amount=100}

{step2amount=140}

{step2amount=102}

Correct answer is Creates a mock service for an API

API Notebook is an open source, shareable web application for API documentation, interactive API tutorial and example generatation, and a client for your API endpoints. Using API Notebook, you can make requests and quickly transform the responses into readable format. However it cannot be used to mock service for an API.

MuleSoft Doc Ref : https://docs.mulesoft.com/api-manager/1.x/api-notebook-concept

Option 2 is the correct answer as /api/* accespts everything starting with /api/

This is a trcik question. On complete phase pyalod consists of summary of records processed which gives insight on which records failed or passed. Hence option 4 is correct answer

MuleSoft Documentation Reference : https://docs.mulesoft.com/mule-runtime/4.3/batch-processing-concept#on-complete

Correct answer is Anypoint Visualizer

MuleSoft Doc Ref : https://docs.mulesoft.com/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.

Diagram Description automatically generated

Returns an array that is the result of applying a transformation function (lambda) to each of the elements.

MuleSoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.3/dataweave-cookbook-map

The map operator is a function in Dataweave which iterates over the items in an array and outputs them into a new array. It basically accepts input as a list of items in an array and manipulates the items in the array in order to form a new array as an output.

I have created below chart for your easier understanding:

Table Description automatically generated

Correct answer is Attributes.

Query parameters , URI parameters and headers are some of examples which are part of attributes.

Diagram Description automatically generated

Bottom of Form

Top of Form

Correct answer is Products

Modern API has three features 1) Treated as products for easy consumption 2) Discoverable and accessible through self-service 3) Easily managed for security , scalability and performance

Correct answer is as below as it follows the correct syntax.

• http:
• basepath: "api"
• host : "localhost"
• port : "8081"

Mule Doc Reference : https://docs.mulesoft.com/mule-runtime/4.3/mule-app-properties-to-configure

Gold is not valid category for connector types.

MuleSoft Doc Ref : https://docs.mulesoft.co m/mule-runtime/3.7/anypoint-connectors#connector-support-categories

Text Description automatically generated with medium confidence

Correct answer is Subflow has no error handling implementation where as sync flow has.

Subflow

A subflow processes messages synchronously (relative to the flow that triggered its execution) and always inherits both the processing strategy and exception strategy employed by the triggering flow. While a subflow is running, processing on the triggering flow pauses, then resumes only after the subflow completes its processing and hands the message back to the triggering flow.

Synchronous Flow

A synchronous flow, like a subflow, processes messages synchronously (relative to the flow that triggered its execution). While a synchronous flow is running, processing on the triggering flow pauses, then resumes only after the synchronous flow completes its processing and hands the message back to the triggering flow. However, unlike a subflow, this type of flow does not inherit processing or exception strategies from the triggering flow.

This type of flow processes messages along a single thread, which is ideally suited to transactional processing

This helps CloudHub to dynamically allocates a port at deployment time.

MuleSoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.3/deploy-to-cloudhub#prerequisites

Attributes are replaced with new attributes from the HTTP Request response.

Attributes include everything apart from Payload/body. For ex: Headers, query parameters, URI parameters.

So, when outbound HTTP request is made, new attributes need to pass the outbound HTTP request and old attributes are replaced.

I have created below diagram to make it easy for you to understand:

Diagram Description automatically generated

WSDL is used to define the contract in case of SOAP . RAML/OAS is used to REST services

Correct answer is Nothing needs to be changed in the other APIs or their associated applications

This is the benefit of having separate interface layer. As there are no changes to interface , no changes are required on the API's which consumes this API in context

The current version of the RAML specification is 1.0

You can check RAML version in RAML definition by referring to first comment. See highlighted part in below image.

Graphical user interface, text, application, email Description automatically generated

POM.xml contains info about the project and configurationn details used by Maven to build the project

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.

Anypoint Exchange provided a way to publish , share and search API's.

MuleSoft Doc Ref : https://docs.mulesoft.com/exchange/

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

Sub flow is always synchronous.

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

Correct answer is vars."customer"."firstName"

Please note that you can also access firstName using this syntax vars.customer.firstName.

Mule Ref Doc : Variables in Mule Apps | MuleSoft Documentation

The HTTP 415 Unsupported Media Type client error response code indicates that the server refuses to accept the request because the payload format is in an unsupported format. The format problem might be due to the request's indicated Content-Type or Content-Encoding , or as a result of inspecting the data directly. In this case as per RAML specification data is expected in application/json and in request Content-Type is set as "text/plain" which is incorrect. Hence solution is set the request Content-Type header to application/json

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/415

Correct answer is Change the method attributes value to "POST".

It can be fixed in either of the two ways as below.

1) Changing method attribute to POST in ClientRequestFlow

2) Setting allowedMethods as PUT in ShippingFlow (but doesn't fit as question mentions about changing ClientRequestFlow)

In this case both the flows can start without any error and requests can be received on both ports. Flow names httpListener1 can call other flow using HTTP request without any issues.

Hence correct answer is

The mule application start successfully

Web client requests can  be received at URI on port 2222 and on port 3333.

Lets check why other options are incorrect

1) The mule application fails to start. There is URL path conflict because both HTTP Listeners are configured with same path  ---- This is incorrect as port value is different in both listeners

2) The mule application start successfully. Web client requests can only be received at URI on port 2222 but not on port 3333  --- This is incorrect as there is no reason for not receiving requests on port 3333

3) The mule application fails to start because of the port binding conflict as HTTP request also use same port i.e. 3333 --- Port binding conflict will not happen in this case. It would have if both listener configurations would have been on same port . But that is not the case here.

Mule Ref Doc : HTTP Listener Reference - Mule 4 | MuleSoft Documentation

Correct answer is Mule runtime

DataWeave is the MuleSoft expression language for accessing and transforming data that travels through a Mule app. DataWeave is tightly integrated with the Mule runtime engine, which runs the scripts and expressions in your Mule app.

Mule Doc Reference : https://docs.mulesoft.com/mule-runtime/4.3/dataweave

Centre for Enablement (C4E) is an IT operating model that enables an enterprise to build reusable assets, accumulate API’s, leverage best practices and knowledge to enable self service and efficient delivery in the organization and implement new solutions faster

MuleSoft Documentation Reference : https://docs.mulesoft.com/db-connector/1.9/database-connector-select

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.

Graphical user interface, text, application, email Description automatically generated

Publish consume: Synchronous. Publish: Asynchronous.

Process section is must to get compiles. Process section must have one or more processors

Diagram Description automatically generated

option 3 is the correct syntz to access application properties

Core (dw::Core) This module contains core DataWeave functions for data transformations. It is automatically imported into any DataWeave script.

Cloudhub expose services on port 8081 and override value in http.port with this one .

Sample log in Runtime Manager is below

21:15:53.148 08/08/2021 Worker-0 ArtifactDeployer.start.01 INFO

Listening for connections on 'http://0.0.0.0:8081 '

Creates reusable APIs and assets designed to be consumed by other business units

Transform Message Add write_date is coverting payload in JSON format and same JSON payload is avaialble to file write processor. However, if the payload is a different format (for example, not CSV) , you can place the transformation inside the Write operation to generate content that will be written without producing a side effect on the message in transit. This is not done in this case. By default, the connector writes whatever is in the message payload. Hence JSON payload will be written to file.

Scatter-Gather Router

The Scatter-Gather component is a routing event processor that processes a Mule event through different parallel processing routes that contain different event processors. Each route receives a reference to the Mule event and executes a sequence of one or more event processors. Each of these routes uses a separate thread to execute the event processors, and the resulting Mule event can be either the same Mule event without modifications or a new Mule event with its own payload, attributes, and variables. The Scatter-Gather component then combines the Mule events returned by each processing route into a new Mule event that is passed to the next event processor only after every route completes successfully.

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.

Mule Ref Doc : https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept

API portal are created by API Exchange and cannot be created by Design Center

vars: Keyword for accessing a variable, for example, through a DataWeave expression in a Mule component, such as the Logger, or from an Input or Output parameter of an operation. If the name of your variable is myVar, you can access it like this: vars.myVar

Hence correct answer is Account Type: #[vars.accountType]

This kind of questions are best solved with filtering technique. Key thing to note here is XML attributes are always access by @ notation. So in this example orderId can be accessed as @OrderId which makes option 3 and option 4 false. Now difference in optin and option 2 is in mapping of lineItemPrice. Correct syntax to format a String in Numbse is value.price as Number. Hence option 2 is correct

Allowed methods is an optional configuration. If nothing is specified then all HTTP methods are supported.

Rest all are mandatory.

Correct answer is The API interfaces are specified at a granularity intended for developers to consume specific aspect of integration processes