Salesforce Updated MuleSoft-Platform-Architect-I Exam Questions and Answers by naya

Given that the application is designed to handle only one process at a time to maintain data consistency, here’s why horizontal scaling won’t increase the processing limit:

Single-Process Constraint:

The application limits to processing one transaction at a time due to its design for consistency, meaning horizontal scaling (adding more workers) does not increase processing speed beyond this limit.

Execution Time:

Since each request takes 200 ms, five requests per second is the maximum processing threshold. Increasing the number of workers does not bypass this single-process limitation.

Explanation of Correct Answer (A):

The scalability remains at five requests per second, as this constraint is intrinsic to the application’s design.

Explanation of Incorrect Options:

Option B suggests a change in execution time, which horizontal scaling does not affect.

Option C assumes doubling the throughput, which isn’t possible due to the single-threaded nature of the application.

Option D suggests horizontal scaling cannot apply, which is incorrect; however, scaling does not increase throughput in this context.

ReferencesFor more on understanding scaling and concurrency in Mule applications, see MuleSoft’s documentation on application performance and scaling limitations​.

Explanation

Correct Answer: API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement

*****************************************

>> API Design and Development - Anypoint Studio, Anypoint Design Center, Anypoint Connectors

>> API Runtime Execution and Hosting - Mule Runtimes, CloudHub, Runtime Services

>> API Operations and Management - Anypoint API Manager, Anypoint Exchange

>> API Consumer Management - API Contracts, Public Portals, Anypoint Exchange, API Notebooks

Explanation

Correct Answer: When there is one CloudHub deployment of the API implementation to three CloudHub workers that must share the cache state.

*****************************************

Key details in the scenario:

>> Use the CloudHub Object Store via the Object Store connector

Considering above details:

>> CloudHub Object Stores have one-to-one relationship with CloudHub Mule Applications.

>> We CANNOT use an application's CloudHub Object Store to be shared among multiple Mule applications running in different Regions or Business Groups or Customer-hosted Mule Runtimes by using Object Store connector.

>> If it is really necessary and very badly needed, then Anypoint Platform supports a way by allowing access to CloudHub Object Store of another application using Object Store REST API. But NOT using Object Store connector.

So, the only scenario where we can use the CloudHub Object Store via the Object Store connector to persist the cache’s state is when there is one CloudHub deployment of the API implementation to multiple CloudHub workers that must share the cache state.

Explanation

Correct Answer: TRUE

*****************************************

>> As per MuleSoft proposed IT Operating Model, designing APIs and making sure that they are discoverable and self-servable is VERY VERY IMPORTANT and decides the success of an API and its application network.