An external REST client periodically sends an array of records in a single POST request to a Mule application's API endpoint. The Mule application must validate each record of the request against a JSON schema before sending it to a downstream system in the same order that it was received in the array.
Record processing will take place inside a router or scope that calls a child flow. The child flow has its own error handling defined. Any validation or communication failures should not prevent further processing of the remaining records.
Which router or scope should be used in the parent flow, and which type of error handler should be used in the child flow in order to meet these requirements?

• A. Choice router in the parent flow
• B. Until Successful router in the parent flow
• C. For Each scope in the parent flow
• D. Parallel For Each scope in the parent flow

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 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.
• 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 web store back end sends a correlation ID value in the HTTP request body in the way required by the Experience API.

What role does back-pressure play in streaming in Mule applications?

• A. It compresses data to save bandwidth.
• B. It encrypts data to prevent unauthorized access.
• C. It duplicates messages to ensure delivery.
• D. It prevents the system from becoming overloaded by regulating data flow.

A company uses CloudHub for API application deployment so that experience APIs and/or API proxies are publicly exposed using custom mTLS. The company's InfoSec team requires isolated, restricted access that is limited internally to system APIs deployed to CloudHub and the company's data center.
What are the minimum infrastructure, component, connection, and software requirements to meet the company's goal and the InfoSec team's requirements?

• A. Virtual Private Cloud
• B. Virtual Private Cloud
• C. Virtual Private Cloud
• D. Virtual Private Cloud

A large enterprise customer operating in a high regulated industry is planning to implement Salesforce for customer facing associates in both Sales and Service, and back-office staff. The business processes that Salesforce supports are critical to the business.
Salesforce will be integrated to multiple back-office systems to provide a single interface for associates. Reliability and monitoring of these integrations are required as associates support customers.
Which integration solution should the architect consider when planning the implementation?

• A. Decouple back-office system callouts into separate distinct services that have inbuilt error logging and monitoring frameworks.
• B. Build a custom integration gateway to support back-office system integrations and ensure reliability and monitoring capabilities.
• C. Leverage Middleware for all back-office system integrations ensuring real time alerting, monitoring and reporting capabilities.
• D. Architect Services in back-office systems to support callouts from Salesforce and build reliability, monitoring and reporting capabilities.