Which statement is true when using XML SDK for creating custom message processors?
A.
Properties are fields defined by an end user of the XML SDK component and serve as a global configuration for the entire Mule project in which they are used
B.
An XML SDK provides both inbound and outbound operations
C.
Operations can be reused in recursive calls
D.
All operations are public
All operations are public
Explanation:
When using XML SDK for creating custom message processors, all operations are public by default and can be used by any Mule application that imports them. There is no way to make an operation private or protected in XML SDK.
References: https://docs.mulesoft.com/mule-sdk/1.1/xml-sdk#operations
A company with MuleSoft Titanium develops a Salesforce System API using MuleSoft out-of-the-box Salesforce Connector and deploys the API to CloudHub.
Which steps provide the average number of requests and average response time of the Salesforce Connector?
A.
Access Anypoint Monitoring’s built-in dashboard. Select a resource.
Locate the information under the Connectors tab.
B.
Access Anypoint Monitoring’s built-in dashboard
Seclect a resource.
Create a custom dashboard to retrieve the information.
C.
Access Anypoint Monitoring built-in dashboard.
Select a resource.
Locate the information under Log Manager < Raw Data.
D.
Change the API Implementation to capture the information in the log.
Retrieve the information from the log file.
Access Anypoint Monitoring’s built-in dashboard. Select a resource.
Locate the information under the Connectors tab.
Explanation:
To get the average number of requests and average response time of the Salesforce Connector, the developer should access Anypoint Monitoring’s built-in dashboard, select a resource (such as an application or an API), and locate the information under the Connectors tab. The Connectors tab shows metrics for each connector used by the resource, such as average requests per minute, average response time, and failures.
References:
https://docs.mulesoft.com/monitoring/built-in-dashboard-reference
Which statement is true when working with correlation IDS?
A.
The HTTP Listener regenerates correlation IDs regardless of the HTTP request
B.
The Anypoint MQ Connector automatically propagates correlation IDS
C.
The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request
D.
The VM Connector does not automatically propagate correction IDs
The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request
Explanation:
When working with correlation IDs, the HTTP Listener generates correlation IDs unless a correlation ID is received in the HTTP request. In that case, it propagates the received correlation ID throughout the flow execution. Correlation IDs are used to track events across different flows or applications.
References:
https://docs.mulesoft.com/mule-runtime/4.3/about-mule-message#message-attributes
An order processing system is composed of multiple Mule application responsible for warehouse, sales and shipping. Each application communication using Anypoint MQ. Each message must be correlated against the original order ID for observability and tracing. How should a developer propagate the order ID as the correlation ID across each message?
A.
Use the underlying HTTP request of Anypoint MQ to set the ‘X-CORRELATION_ID’ header to the order ID
B.
Set a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications
C.
Use the default correlation ID, Anypoint MQ will sutomatically propagate it.
D.
Wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID
Wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID
Explanation:
To propagate the order ID as the correlation ID across each message using Anypoint MQ, the developer should wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID. The With CorrelationID scope allows setting a custom correlation ID for any event that occurs within it. The Tracing module also enables distributed tracing across different Mule applications and services using Anypoint Monitoring.
References:
https://docs.mulesoft.com/tracing-module/1.0/tracing-module-reference#with-correlation-id-scope
https://docs.mulesoft.com/tracing-module/1.0/tracing-module-concepts
Which pattern can a web API use to notify its client of state changes as soon as they occur?
A.
HTTP Webhock
B.
Shared database trigger
C.
Schedule Event Publisher
D.
ETL data load
HTTP Webhock
Explanation:
A web API can use HTTP Webhook to notify its client of state changes as soon as they occur. A webhook is an HTTP callback that allows an API to send real-time notifications to another system or application when an event happens. The client registers a URL with the API where it wants to receive notifications, and then the API sends an HTTP request to that URL with information about the event.
References:
https://docs.mulesoft.com/connectors/webhook/webhook-connector
In a Mule project, Flow-1 contains a flow-ref to Flow-2 depends on data from Flow-1 to execute successfully. Which action ensures the test suites and test cases written for Flow-1 and Flow-2 will execute successfully?
A.
Chain together the test suites and test cases for Flow-1 and Flow-2
B.
Use ‘’Set Event to pass the input that is needed, and keep the test cases for Flow-1 and Flow-2 Independent
C.
Use ‘’Before Test Case’’ To collect data from Flow-1 test cases before running Flow-2 test cases
D.
Use ‘After Test Case’ to produce the data needed from Flow-1 test cases to pass to Flow-2 test cases
Use ‘’Set Event to pass the input that is needed, and keep the test cases for Flow-1 and Flow-2 Independent
Explanation
To ensure the test suites and test cases written for Flow-1 and Flow-2 will execute successfully, the developer should use a Set Event processor to pass the input that is needed by Flow-2, and keep the test cases for Flow-1 and Flow-2 independent. This way, the developer can isolate the testing of each flow and avoid coupling them together.
References:
https://docs.mulesoft.com/munit/2.3/munit-test-flow
A new Mule project has been created in Anypoint Studio with the default settings.
Which file inside the Mule project must be modified before using Maven to successfully deploy the application?
A.
Settings.xml
B.
Config.yaml
C.
Pom.xml
D.
Mule.artificact.json
Pom.xml
Explanation
To use Maven to successfully deploy the application, the developer needs to modify the pom.xml file inside the Mule project. The pom.xml file contains the configuration and dependencies of the Mule application, as well as the deployment information such as the CloudHub region, environment, and worker size. The developer needs to specify these properties in the pom.xml file before using Maven to deploy the application.
References:
https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#application-deployment-descriptor
The Center for Enablement team published a common application as a reusable module to the central Nexus repository.
How can the common application be included in all API implementations?
A.
Download the common application from Naxus and copy it to the src/main/resources folder in the API
B.
Copy the common application’s source XML file and out it in a new flow file in the src/main/mule folder
C.
Add a Maven dependency in the PCM file with multiple-plugin as <classifier>
D.
Add a Maven dependency in the POM file with jar as <classifier>
Add a Maven dependency in the POM file with jar as <classifier>
Explanation:
To include a common application as a reusable module in all API implementations, the developer should add a Maven dependency in the POM file with jar as <classifier>. This way, the developer can reuse Mule code from another application by packaging it as a JAR file and adding it as a dependency in the POM file of the API implementation. The classifier element specifies that it is a JAR file.
References:
https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#add-a-maven-dependency-to-the-pom-file
Page 1 out of 6 Pages |