Question 1

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 2

A corporation has deployed Mule applications to different customer-hosted Mule runtimes. Mule applications deployed to these Mule runtimes are managed by Anypoint Platform. What needs to be installed or configured (if anything) to monitor these Mule applications from Anypoint Monitoring, and how is monitoring data from each Mule application sent to Anypoint Monitoring?

Options :

A : Enable monitoring of individual Mule applications from the Runtime Manager application settings. Runtime Manager sends monitoring data to Anypoint Monitoring for each deployed Mule application.

B : Install a Runtime Manager agent on each Mule runtime. Each Runtime Manager agent sends monitoring data from the Mule applications running in its Mule runtime to Runtime Manager, then Runtime Manager sends monitoring data to Anypoint Monitoring.

C : Leave the out-of-the-box Anypoint Monitoring agent unchanged in its default Mule runtime installation. Each Anypoint Monitoring agent sends monitoring data from the Mule applications running in its Mule runtime to Runtime Manager, then Runtime Manager sends monitoring data to Anypoint Monitoring

D : Install an Anypoint Monitoring agent on each Mule runtime. Each Anypoint Monitoring agent sends monitoring data from the Mule applications running in its Mule runtime to Anypoint Monitoring.

Answer: D

Question 3

An organization is creating a set of new services that are critical for their business. The project team prefers using REST for all services but is willing to use SOAP with common WS-" standards if a particular service requires it. What requirement would drive the team to use SOAP/WS-* for a particular service?

Options :

A : Must use XML payloads for the service and ensure that it adheres to a specific schema

B : Must publish and share the service specification (including data formats) with the consumers of the service

C : Must support message acknowledgement and retry as part of the protocol

D : Must secure the service, requiring all consumers to submit a valid SAML token

Answer: D

Question 4

A leading e-commerce giant will use Mulesoft API's on runtime fabric (RTF) to process customer orders. Some customer's sensitive information such as credit card information is also there as a part of a API payload. What approach minimizes the risk of matching sensitive data to the original and can convert back to the original value whenever and wherever required?

Options :

A : Apply masking to hide the sensitive information and then use API

B : manager to detokenize the masking format to return the original value

C : create a tokenization format and apply a tokenization policy to the API Gateway

D : Used both masking and tokenization

E : Apply a field level encryption policy in the API Gateway

Answer: C

Question 5

Customer has deployed mule applications to different customer hosted mule run times. Mule applications are managed from Anypoint platform. What needs to be configured to monitor these Mule applications from Anypoint monitoring and what sends monitoring data to Anypoint monitoring?

Options :

A : Enable monitoring of individual applications from runtime manager application settings Runtime manager agent sends monitoring data from the mule applications to Anypoint monitoring

B : Install runtime manager agent on each mule runtime Runtime manager agent since monitoring data from the mule applications to Anypoint monitoring

C : Anypoint monitoring agent on each mule runtime Anypoint monitoring agent sends monitoring data from the mule applications to Anypoint monitoring

D : By default, Anypoint monitoring agent will be installed on each Mule run time Anypoint Monitoring agent automatically sends monitoring data from the Mule applications to Anypoint monitoring

Answer: A