Study with Salesforce : MuleSoft-Integration-Architect-I Exam Torrent as your best preparation materials

A rale limiting policy has been applied to a soap VI.2 API published in Clondhub. The API implementation catches errors in a global error handler on error propagate in the main flow for HTTP:
RETRY_EXHAUSTED with HTTP status set to 429 and any with the HTTP status set to 500.
What is the expected H1TP status when the client exceeds the quota of the API calls?

• A. HTTP status 500 as defined in the ANY error handler in the API since an API:RETRY_EXHAUSTED will be generated
• B. HTTP status 400 from the rate-limiting policy violation since the call does not reach the back-end
• C. HTTP status 429 as defined in the HTTP:RETRY EXHAUSTED error handler in the API
• D. HTTP status 401 unauthorized for policy violation

An organization plans to use the Anypoint Platform audit logging service to log Anypoint MQ actions.
What consideration must be kept in mind when leveraging Anypoint MQ Audit Logs?

• A. Anypoint MQ Audit Logs include logs for sending, receiving, or browsing messages
• B. Anypoint MQ Audit Logs include fogs for failed Anypoint MQ operations
• C. Anypoint MQ Audit Logs include logs for queue create, delete, modify, and purge operations

What aspects of a CI/CD pipeline for Mule applications can be automated using MuleSoft-provided Maven plugins?

• A. Compile, package, unit test, validate unit test coverage, deploy
• B. Import from API designer, compile, package, unit test, deploy, publish to Anypoint Exchange
• C. Compile, package, unit test, deploy, create associated API instances in API Manager
• D. Compile, package, unit test, deploy, integration test (Incorrect)

According to MuleSoft, which deployment characteristic applies to a microservices application architecture?

• A. Core business capabilities are encapsulated in a single, deployable application
• B. A deployment to enhance one capability requires a redeployment of all capabilities
• C. Services exist as independent deployment artifacts and can be scaled -independently of other services
• D. All services of an application can be deployed together as single Java WAR file

A leading eCommerce giant will use MuleSoft APIs on Runtime Fabric (RTF) to process customer orders.
Some customer-sensitive information, such as credit card information, is required in request payloads or is included in response payloads in some of the APIs. Other API requests and responses are not authorized to access some of this customer-sensitive information but have been implemented to validate and transform based on the structure and format of this customer-sensitive information (such as account IDs, phone numbers, and postal codes).
What approach configures an API gateway to hide sensitive data exchanged between API consumers and API implementations, but can convert tokenized fields back to their original value for other API requests or responses, without having to recode the API implementations?
Later, the project team requires all API specifications to be augmented with an additional non-functional requirement (NFR) to protect the backend services from a high rate of requests, according to defined service- level agreements (SLAs). The NFR's SLAs are based on a new tiered subscription level "Gold", "Silver", or
"Platinum" that must be tied to a new parameter that is being added to the Accounts object in their enterprise data model.
Following MuleSoft's recommended best practices, how should the project team now convey the necessary non-functional requirement to stakeholders?

• A. Create and deploy API proxies in API Manager for the NFR, change the baseurl in eachAPI specification to the corresponding API proxy implementation endpoint, and publish each modified API specification to Exchange
• B. Create a shared RAML fragment required to implement the NFR, list each API implementation endpoint in the RAML fragment, and publish the RAML fragment to Exchange
• C. Update each API specification with a shared RAML fragment required to implement the NFR and publish the RAML fragment and each modified API specification to Exchange
• D. Update each API specification with comments about the NFR's SLAs and publish each modified API specification to Exchange