Question 1

Refer to the exhibit. An organization needs to enable access to their customer data from both a mobile app and a web application, which each need access to common fields as well as certain unique fields. The data is available partially in a database and partially in a 3rd-party CRM system. What APIs should be created to best fit these design requirements?A) A Process API that contains the data required by both the web and mobile apps, allowing these applications to invoke it directly and access the data they need thereby providing the flexibility to add more fields in the future without needing API changesB) One set of APIs (Experience API, Process API, and System API) for the web app, and another set for the mobile appC) Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM systemD) A common Experience API used by both the web and mobile apps, but separate Process APIs for the web and mobile apps that interact with the database and the CRM System

Options :

A : Option A

B : Option B

C : Option C

D : Option D

Answer: C

Question 2

A system API has a guaranteed SLA of 100 ms per request. The system API is deployed to a primary environment as well as to a disaster recovery (DR) environment, with different DNS names in each environment. An upstream process API invokes the system API and the main goal of this process API is to respond to client requests in the least possible time. In what order should the system APIs be invoked, and what changes should be made in order to speed up the response time for requests from the process API?

Options :

A : In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment, and ONLY use the first response

B : In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment using a scatter-gather configured with a timeout, and then merge the responses

C : Invoke the system API deployed to the primary environment, and if it fails, invoke the system API deployed to the DR environment

D : Invoke ONLY the system API deployed to the primary environment, and add timeout and retry logic to avoid intermittent failures

Answer: A

Question 3

An API implementation is deployed to CloudHub. What conditions can be alerted on using the default Anypoint Platform functionality, where the alert conditions depend on the end-to-end request processing of the API implementation?

Options :

A : When the API is invoked by an unrecognized API client

B : When a particular API client invokes the API too often within a given time period

C : When the response time of API invocations exceeds a threshold

D : When the API receives a very high number of API invocations

Answer: C

Question 4

When can CloudHub Object Store v2 be used?

Options :

A : To store an unlimited number of key-value pairs

B : To store payloads with an average size greater than 15MB

C : To store information in Mule 4 Object Store v1

D : To store key-value pairs with keys up to 300 characters

Answer: D

Question 5

When designing an upstream API and its implementation, the development team has been advised to NOT set timeouts when invoking a downstream API, because that downstream API has no SLA that can be relied upon. This is the only downstream API dependency of that upstream API. Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?

Options :

A : An SLA for the upstream API CANNOT be provided

B : The invocation of the downstream API will run to completion without timing out

C : A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes

D : A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes

Answer: A

Free Mule-Arch-201 Mock Exam – Practice Online Confidently

Buying Options: