Question 1

The ABC company has an Anypoint Runtime Fabric on VMs/Bare Metal (RTF-VM) appliance installed on its own customer-hosted AWS infrastructure. Mule applications are deployed to this RTF-VM appliance. As part of the company standards, the Mule application logs must be forwarded to an external log management tool (LMT). Given the company's current setup and requirements, what is the most idiomatic (used for its intended purpose) way to send Mule application logs to the external LMT?

Options :

A : In RTF-VM, install and configure the external LTM-s log-forwarding agent

B : In RTF-VM, edit the pod configuration to automatically install and configure an Anypoint Monitoring agent

C : In each Mule application, configure custom Log4j settings

D : In RTF-VM. configure the out-of-the-box external log forwarder

Answer: A

Question 2

According to MuleSoft's IT delivery and operating model, which approach can an organization adopt in order to reduce the frequency of IT project delivery failures?

Options :

A : Decouple central IT projects from the innovation that happens within each line of business

B : Adopt an enterprise data model

C : Prevent technology sprawl by reducing production of API assets

D : Stop scope creep by centralizing requirements-gathering

Answer: A

Question 3

A company is planning to migrate its deployment environment from on-premises cluster to a Runtime Fabric (RTF) cluster. It also has a requirement to enable Mule applications deployed to a Mule runtime instance to store and share data across application replicas and restarts. How can these requirements be met?

Options :

A : Anypoint object store V2 to share data between replicas in the RTF cluster

B : Install the object store pod on one of the cluster nodes

C : Configure Persistence Gateway in any of the servers using Mule Object Store

D : Configure Persistent Gateway at the RTF

Answer: A

Question 4

Refer to the exhibit. A shopping cart checkout process consists of a web store backend sending a sequence of API invocations to an Experience API, which in turn invokes a Process API. All API invocations are over HTTPS POST. The Java web store backend executes in a Java EE application server, while all API implementations are Mule applications executing in a customer -hosted Mule runtime. End-to-end correlation of all HTTP requests and responses belonging to each individual checkout Instance is required. This is to be done through a common correlation ID, so that all log entries written by the web store backend, Experience API implementation, and Process API implementation include the same correlation ID for all requests and responses belonging to the same checkout instance. What is the most efficient way (using the least amount of custom coding or configuration) for the web store backend and the implementations of the Experience API and Process API to participate in end-to-end correlation of the API invocations for each checkout instance?

Options :

A : The web store backend, being a Java EE application, automatically makes use of the thread-local correlation ID generated by the Java EE application server and automatically transmits that to the Experience API using HTTP-standard headers No special code or configuration is included in the web store backend, Experience API, and Process API implementations to generate and manage the correlation ID

B : The web store backend generates a new correlation ID value at the start of checkout and sets it on the X-CORRELATlON-lt HTTP request header In each API invocation belonging to that checkout No special code or configuration is included in the Experience API and Process API implementations to generate and manage the correlation ID

C : The Experience API implementation generates a correlation ID for each incoming HTTP request and passes it to the web store backend in the HTTP response, which includes it in all subsequent API invocations to the Experience API. The Experience API implementation must be coded to also propagate the correlation ID to the Process API in a suitable HTTP request header

D : The web store backend sends a correlation ID value in the HTTP request body In the way required by the Experience API The Experience API and Process API implementations must be coded to receive the custom correlation ID In the HTTP requests and propagate It in suitable HTTP request headers

Answer: B

Question 5

A Mule application uses the Database connector. What condition can the Mule application automatically adjust to or recover from without needing to restart or redeploy the Mule application?

Options :

A : One of the stored procedures being called by the Mule application has been renamed

B : The database server was unavailable for four hours due to a major outage but is now fully operational again

C : The credentials for accessing the database have been updated and the previous credentials are no longer valid

D : The database server has been updated and hence the database driver library/JAR needs a minor version upgrade

Answer: B

Higher Test Marks with Free Online Mule-Arch-202 Exam Practice

Buying Options: