Salesforce MuleSoft-Platform-Architect-I Exam Questions
Salesforce Certified MuleSoft Platform Architect I (Page 5 )

Updated On: 28-Feb-2026

In an organization, the InfoSec team is investigating Anypoint Platform related data traffic.
From where does most of the data available to Anypoint Platform for monitoring and alerting originate?

  1. From the Mule runtime or the API implementation, depending on the deployment model
  2. From various components of Anypoint Platform, such as the Shared Load Balancer, VPC, and Mule runtimes
  3. From the Mule runtime or the API Manager, depending on the type of data
  4. From the Mule runtime irrespective of the deployment model

Answer(s): D

Explanation:

Correct Answer: From the Mule runtime irrespective of the deployment model
*****************************************
>> Monitoring and Alerting metrics are always originated from Mule Runtimes irrespective of the deployment model.
>> It may seems that some metrics (Runtime Manager) are originated from Mule Runtime and some are (API Invocations/ API Analytics) from API Manager. However, this is realistically NOT TRUE. The reason is, API manager is just a management tool for API instances but all policies upon applying on APIs eventually gets executed on Mule Runtimes only (Either Embedded or API Proxy).
>> Similarly all API Implementations also run on Mule Runtimes.
So, most of the day required for monitoring and alerts are originated fron Mule Runtimes only irrespective of whether the deployment model is MuleSoft-hosted or Customer-hosted or Hybrid.



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?

  1. An SLA for the upstream API CANNOT be provided
  2. The invocation of the downstream API will run to completion without timing out
  3. A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes
  4. A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes

Answer(s): A

Explanation:

Correct Answer: An SLA for the upstream API CANNOT be provided.
*****************************************
>> First thing first, the default HTTP response timeout for HTTP connector is 10000 ms (10 seconds). NOT 500 ms.
>> Mule runtime does NOT apply any such "load-dependent" timeouts. There is no such behavior currently in Mule.
>> As there is default 10000 ms time out for HTTP connector, we CANNOT always guarantee that the invocation of the downstream API will run to completion without timing out due to its unreliable SLA times. If the response time crosses 10 seconds then the request may time out.
The main impact due to this is that a proper SLA for the upstream API CANNOT be provided. Reference:
https://docs.mulesoft.com/http-connector/1.5/http-documentation#parameters-3



What best explains the use of auto-discovery in API implementations?

  1. It makes API Manager aware of API implementations and hence enables it to enforce policies
  2. It enables Anypoint Studio to discover API definitions configured in Anypoint Platform
  3. It enables Anypoint Exchange to discover assets and makes them available for reuse
  4. It enables Anypoint Analytics to gain insight into the usage of APIs

Answer(s): A

Explanation:

Correct Answer: It makes API Manager aware of API implementations and hence enables it to enforce policies.
*****************************************
>> API Autodiscovery is a mechanism that manages an API from API Manager by pairing the deployed application to an API created on the platform.
>> API Management includes tracking, enforcing policies if you apply any, and reporting API analytics.
>> Critical to the Autodiscovery process is identifying the API by providing the API name and version.


Reference:

https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept https://docs.mulesoft.com/api-manager/1.x/api-auto-discovery https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept



What should be ensured before sharing an API through a public Anypoint Exchange portal?

  1. The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility
  2. The users needing access to the API should be added to the appropriate role in Anypoint Platform
  3. The API should be functional with at least an initial implementation deployed and accessible for users to interact with
  4. The API should be secured using one of the supported authentication/authorization mechanisms to ensure that data is not compromised

Answer(s): A

Explanation:


Correct Answer: The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility.
*****************************************


Reference:

https://docs.mulesoft.com/exchange/to-share-api-asset-to-portal https://docs.mulesoft.com/exchange/to-share-api-asset-to-portal



Refer to the exhibit.

A RAML definition has been proposed for a new Promotions Process API, and has been published to Anypoint Exchange.
The Marketing Department, who will be an important consumer of the Promotions API, has important requirements and expectations that must be met.
What is the most effective way to use Anypoint Platform features to involve the Marketing Department in this early API design phase?

A) Ask the Marketing Department to interact with a mocking implementation of the API using the automatically generated API Console

B) Organize a design workshop with the DBAs of the Marketing Department in which the database schema of the Marketing IT systems is translated into RAML

C) Use Anypoint Studio to Implement the API as a Mule application, then deploy that API implementation to CloudHub and ask the Marketing Department to interact with it

D) Export an integration test suite from API designer and have the Marketing Department execute the tests In that suite to ensure they pass

  1. Option A
  2. Option B
  3. Option C
  4. Option D

Answer(s): A

Explanation:

Correct Answer: Ask the Marketing Department to interact with a mocking implementation of the API using the automatically generated API Console.
***************************************** As per MuleSoft's IT Operating Model:
>> API consumers need NOT wait until the full API implementation is ready.
>> NO technical test-suites needs to be shared with end users to interact with APIs.
>> Anypoint Platform offers a mocking capability on all the published API specifications to Anypoint Exchange which also will be rich in documentation covering all details of API functionalities and working nature.
>> No needs of arranging days of workshops with end users for feedback.
API consumers can use Anypoint Exchange features on the platform and interact with the API using its mocking feature. The feedback can be shared quickly on the same to incorporate any changes.



Viewing page 5 of 20
Viewing questions 21 - 25 out of 152 questions



Post your Comments and Discuss Salesforce MuleSoft-Platform-Architect-I exam dumps with other Community members:

MuleSoft-Platform-Architect-I Exam Discussions & Posts

AI Tutor