Free MuleSoft Certified Platform Architect – Level 1 MAINTENANCE Exam MCPA-Level-1-Maintenance Exam Practice Test

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?

• 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
• 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
• Invoke the system API deployed to the primary environment, and if it fails, invoke the system API deployed to the DR environment
• Invoke ONLY the system API deployed to the primary environment, and add timeout and retry logic to avoid intermittent failures

A set of tests must be performed prior to deploying API implementations to a staging environment. Due to data security and access restrictions, untested APIs cannot be granted access to the backend systems, so instead mocked data must be used for these tests. The amount of available mocked data and its contents is sufficient to entirely test the API implementations with no active connections to the backend systems. What type of tests should be used to incorporate this mocked data?

• Integration tests
• Performance tests
• Functional tests (Blackbox)
• Unit tests (Whitebox)

An Anypoint Platform organization has been configured with an external identity provider (IdP) for identity management and client management. What credentials or token must be provided to Anypoint CLI to execute commands against the Anypoint Platform APIs?

• The credentials provided by the IdP for identity management
• The credentials provided by the IdP for client management
• An OAuth 2.0 token generated using the credentials provided by the IdP for client management
• An OAuth 2.0 token generated using the credentials provided by the IdP for identity management

What is true about where an API policy is defined in Anypoint Platform and how it is then applied to API instances?

• The API policy Is defined In Runtime Manager as part of the API deployment to a Mule runtime, and then ONLY applied to the specific API Instance
• The API policy Is defined In API Manager for a specific API Instance, and then ONLY applied to the specific API instance
• The API policy Is defined in API Manager and then automatically applied to ALL API instances
• The API policy is defined in API Manager, and then applied to ALL API instances in the specified environment

An API experiences a high rate of client requests (TPS) vwth small message paytoads. How can usage limits be imposed on the API based on the type of client application?

• Use an SLA-based rate limiting policy and assign a client application to a matching SLA tier based on its type
• Use a spike control policy that limits the number of requests for each client application type
• Use a cross-origin resource sharing (CORS) policy to limit resource sharing between client applications, configured by the client application type
• Use a rate limiting policy and a client ID enforcement policy, each configured by the client application type

What is true about API implementations when dealing with legal regulations that require all data processing to be performed within a certain jurisdiction (such as in the USA or the EU)?

• They must avoid using the Object Store as it depends on services deployed ONLY to the US East region
• They must use a Jurisdiction-local external messaging system such as Active MQ rather than Anypoint MQ
• They must te deployed to Anypoint Platform runtime planes that are managed by Anypoint Platform control planes, with both planes in the same Jurisdiction
• They must ensure ALL data is encrypted both in transit and at rest

What is a typical result of using a fine-grained rather than a coarse-grained API deployment model to implement a given business process?

• A decrease in the number of connections within the application network supporting the business process
• A higher number of discoverable API-related assets in the application network
• A better response time for the end user as a result of the APIs being smaller in scope and complexity
• An overall tower usage of resources because each fine-grained API consumes less resources

What is a best practice when building System APIs?

• Document the API using an easily consumable asset like a RAML definition
• Model all API resources and methods to closely mimic the operations of the backend system
• Build an Enterprise Data Model (Canonical Data Model) for each backend system and apply it to System APIs
• Expose to API clients all technical details of the API implementation's interaction wifch the backend system

An API has been updated in Anypoint exchange by its API producer from version 3.1.1 to 3.2.0 following accepted semantic versioning practices and the changes have been communicated via the APIs public portal. The API endpoint does NOT change in the new version. How should the developer of an API client respond to this change?

• The API producer should be requested to run the old version in parallel with the new one
• The API producer should be contacted to understand the change to existing functionality
• The API client code only needs to be changed if it needs to take advantage of the new features
• The API clients need to update the code on their side and need to do full regression

A system API is deployed to a primary environment as well as to a disaster recovery (DR) environment, with different DNS names in each environment. A process API is a client to the system API and is being rate limited by the system API, with different limits in each of the environments. The system API's DR environment provides only 20% of the rate limiting offered by the primary environment. What is the best API fault-tolerant invocation strategy to reduce overall errors in the process API, given these conditions and constraints?

• Invoke the system API deployed to the primary environment; add timeout and retry logic to the process API to avoid intermittent failures; if it still fails, invoke the system API deployed to the DR environment
• Invoke the system API deployed to the primary environment; add retry logic to the process API to handle intermittent failures by invoking the system API deployed to the DR environment
• In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment; add timeout and retry logic to the process API to avoid intermittent failures; add logic to the process API to combine the results
• Invoke the system API deployed to the primary environment; add timeout and retry logic to the process API to avoid intermittent failures; if it still fails, invoke a copy of the process API deployed to the DR environment