Refer to the exhibit.

A shopping cart checkout process consists of a web store back end that sends a sequence of HTTPS POST requests to an Experience API, which in turn invokes a Process API using HTTPS. The web store back end executes in a Java EE application server. 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 checkout instance is required. This is to be done through a common correlation ID so that all log entries written by the web store back end, 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 back end 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?

• A. The web store back end sends a correlation ID value in the HTTP request body in the way required by the Experience API.
• B. The web store back end, being a Java EE application, automatically uses the thread-local correlation ID generated by the Java EE application server and automatically transmits that to the Experience API using standard HTTP headers.
• C. The web store back end generates a new correlation ID value at the start of checkout and sets it on the X-Correlation-ID HTTP request header in each API invocation belonging to that checkout.
• D. The Experience API implementation generates a correlation ID for each incoming HTTP request and passes it to the web store back end in the HTTP response, which includes it in all subsequent API invocations to the Experience API.

An external web UI application currently accepts occasional HTTP requests from client web browsers to change (insert, update, or delete) inventory pricing information in an inventory system's database. Each inventory pricing change must be transformed and then synchronized with multiple customer experience systems in near real-time (in under 10 seconds).
New customer experience systems are expected to be added in the future. The database is used heavily and limits the number of SELECT queries that can be made to the database to 10 requests per hour per user.
How can inventory pricing changes synchronize with the various customer experience systems in near real-time using an integration mechanism that is scalable, decoupled, reusable, and maintainable?

• A. Write a Mule application with a Database On Table Row event source configured for the inventory pricing database, with the ID attribute set to an appropriate database column.
• B. Replace the external web UI application with a Mule application to accept HTTP requests from client web browsers.
• C. Write a Mule application with a Database On Table Row event source configured for the inventory pricing database, with the watermark attribute set to an appropriate database column.
• D. Add a trigger to the inventory-pricing database table so that for each change to the inventory pricing database, a stored procedure is called that makes a REST call to a Mule application.

An automation engineer must write scripts to automate the steps of the API lifecycle, including steps to create, publish, deploy, and manage APIs and their implementations in Anypoint Platform.
Which Anypoint Platform feature can be most easily used to automate the execution of all these actions in scripts without needing to directly invoke the Anypoint Platform REST APIs?

• A. Mule Maven plugin
• B. Anypoint CLI
• C. Custom-developed Postman scripts
• D. GitHub actions

An organization uses MuleSoft extensively and has about 2,000 employees. Many of them work on MuleSoft APIs. The organization has approximately 500 APIs in production.
The organization's leadership strictly discourages direct API modification (for example, stop/start/delete in production); however, there have been a few instances where modifications in production occurred. Now leadership wants to know every instance when this occurred in the past year and include timestamps and user IDs.
What is the easiest way to retrieve this information?

• A. Invoke the Runtime Manager Platform API for each production API and check access_history one-by-one
• B. Invoke Audit Log Query Platform API and using a combination of filters such as timeframe and actionType to extract a user list
• C. Submit a support ticket to the MuleSoft product team to create a custom report
• D. Use MuleSoft audit logs; however, the audit logs only store data for six months