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

During a planning session with the executive leadership, the development team director presents plans for a new API to expose the data in the company’s order database. An earlier effort to build an API on top of this data failed, so the director is recommending a design-first approach. Which characteristics of a design-first approach will help make this API successful?

Options :

A : Building MUnit tests so administrators can confirm code coverage percentage during deployment

B : Publishing the fully implemented API to Exchange so all developers can reuse the API

C : Adding global policies to the API so all developers automatically secure the implementation before coding anything

D : Developing a specification so consumers can test before the implementation is built

Answer: D

Question 3

What limits if a particular Anypoint Platform user can discover an asset in Anypoint Exchange?

Options :

A : Design Center and RAML were both used to create the asset

B : The existence of a public Anypoint Exchange portal to which the asset has been published

C : The type of the asset in Anypoint Exchange

D : The business groups to which the user belongs

Answer: D

Question 4

A new upstream API Is being designed to offer an SLA of 500 ms median and 800 ms maximum (99th percentile) response time. The corresponding API implementation needs to sequentially invoke 3 downstream APIs of very similar complexity. The first of these downstream APIs offers the following SLA for its response time: median: 100 ms, 80th percentile: 500 ms, 95th percentile: 1000 ms. If possible, how can a timeout be set in the upstream API for the invocation of the first downstream API to meet the new upstream API's desired SLA?

Options :

A : Set a timeout of 100 ms; that leaves 400 ms for the other two downstream APIs to complete

B : Do not set a timeout; the Invocation of this API Is mandatory and so we must wait until it responds

C : Set a timeout of 50 ms; this times out more invocations of that API but gives additional room for retries

D : No timeout is possible to meet the upstream API-s desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API

Answer: D

Question 5

A manufacturing company is planning to deploy Mule applications to its own Azure Kubernetes Service infrastructure. The organization wants to make the Mule applications more available and robust by deploying each Mule application to an isolated Mule runtime in a Docker container while managing all the Mule applications from the MuleSoft-hosted control plane. What is the most idiomatic (used for its intended purpose) choice of runtime plane to meet these organizational requirements?

Options :

A : Anypoint Platform Private Cloud Edition

B : Anypoint Runtime Fabric

C : CloudHub

D : Anypoint Service Mesh

Answer: B

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

Buying Options: