Mulesoft MCPA-Level-1 Exam Questions

True or False. We should always make sure that the APIs being designed and developed are self-servable even if it needs more man-day effort and resources.

A.

FALSE

B.

TRUE

Mule applications that implement a number of REST APIs are deployed to their own subnet
that is inaccessible from outside the organization.
External business-partners need to access these APIs, which are only allowed to be
invoked from a separate subnet dedicated to partners - called Partner-subnet. This subnet
is accessible from the public internet, which allows these external partners to reach it.
Anypoint Platform and Mule runtimes are already deployed in Partner-subnet. These Mule
runtimes can already access the APIs.
What is the most resource-efficient solution to comply with these requirements, while
having the least impact on other applications that are currently using the APIs?

A.

Implement (or generate) an API proxy Mule application for each of the APIs, then deploy the API proxies to the Mule runtimes

B.

Redeploy the API implementations to the same servers running the Mule runtimes

C.

Add an additional endpoint to each API for partner-enablement consumption

D.

Duplicate the APIs as Mule applications, then deploy them to the Mule runtimes

An application updates an inventory running only one process at any given time to keep the inventory consistent. This process takes 200 milliseconds (.2 seconds) to execute; therefore, the scalability threshold of the application is five requests per second. What is the impact on the application if horizontal scaling is applied, thereby increasing the number of Mule workers?

A. The application scalability threshold is five requests per second regardless of the horizontal scaling

B. The total process execution time is now 100 milliseconds (.1 seconds)

C. The application scalability threshold is now 10 requests per second

D. Horizontal scaling cannot be applied to an already-running application

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?

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

What CANNOT be effectively enforced using an API policy in Anypoint Platform?

A.

Guarding against Denial of Service attacks

B.

Maintaining tamper-proof credentials between APIs

C.

Logging HTTP requests and responses

D.

Backend system overloading

An online store's marketing team has noticed an increase in customers leaving online baskets without checking out. They suspect a technology issue is at the root cause of the baskets being left behind. They approach the Center for Enablement to ask for help identifying the issue. Multiple APIs from across all the layers of their application network are involved in the shopping application. Which feature of the Anypoint Platform can be used to view metrics from all involved APIs at the same time?

A. Custom dashboards

B. Built-in dashboards

C. Functional monitoring

D. API Manager

Refer to the exhibit.

A.

Option A

B.

Option B

C.

Option C

D.

Option D

Refer to the exhibit.

What is the best way to decompose one end-to-end business process into a collaboration of Experience, Process, and System APIs?
A) Handle customizations for the end-user application at the Process API level rather than the Experience API level
B) Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs
C) Always use a tiered approach by creating exactly one API for each of the 3 layers (Experience, Process and System APIs)
D) Use a Process API to orchestrate calls to multiple System APIs, but NOT to other Process APIs

A. Option A

B. Option B

C. Option C

D. Option D

Explanation:
Correct Answer: Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs.

• All customizations for the end-user application should be handled in "Experience API" only. Not in Process API
• We should use tiered approach but NOT always by creating exactly one API for each of the 3 layers. Experience APIs might be one but Process APIs and System APIs are often more than one. System APIs for sure will be more than one all the time as they are the smallest modular APIs built in front of end systems.
• Process APIs can call System APIs as well as other Process APIs. There is no such anti-design pattern in API-Led connectivity saying Process APIs should not call other Process APIs.

So, the right answer in the given set of options that makes sense as per API-Led connectivity principles is to allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs. This way, some future Process APIs can make use of that data from System APIs and we need NOT touch the System layer APIs again and again.