A Mule application uses API autodiscovery to access and enforce policies for a RESTful implementation.
A. Northing because flowRef is an optional attribute which can be passed runtime
B. The name of the flow that has APlkit Console to receive all incoming RESTful operation requests.
C. Any of the APIkit generate implement flows
D. The name of the flow that has HTTP listener to receive all incoming RESTful operation requests
Explanation:
To use API autodiscovery to access and enforce policies for a RESTful implementation, flowRef must be set to the name of the flow that has HTTP listener to receive all incoming RESTful operation requests. This way, API autodiscovery can identify the API implementation and associate it with the corresponding API specification and policies in API Manager. The flow that has HTTP listener is usually the main flow that contains the APIKit Router. References: https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept#flowref
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.
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
An organization uses CloudHub to deploy all of its applications. How can a common-global-handler flow be configured so that it can be reused across all of the organization’s deployed applications?
A. Create a Mule plugin project
Create a common-global-error-handler flow inside the plugin project.
Use this plugin as a dependency in all Mute applications.
Import that configuration file in Mute applications.
B. Create a common-global-error-handler flow in all Mule Applications Refer to it flow-ref wherever needed.
C. Create a Mule Plugin project
Create a common-global-error-handler flow inside the plugin project.
Use this plugin as a dependency in all Mule applications
D. Create a Mule daman project.
Create a common-global-error-handler flow inside the domain project.
Use this domain project as a dependency.
Explanation:
To configure a common-global-handler flow that can be reused across all of the organization’s deployed applications, the developer should create a Mule Plugin project, create a common-global-error-handler flow inside the plugin project, and use this plugin as a dependency in all Mule applications. This way, the developer can import the common-global-error-handler flow in any application that needs it and avoid duplicating the error handling logic. References: https://docs.mulesoft.com/mule-runtime/4.3/error-handling#global-error-handler
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
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
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
D. Add a Maven dependency in the POM file with jar as
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 . 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 2 out of 13 Pages |
Previous |