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

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?

• Implement (or generate) an API proxy Mule application for each of the APIs, then deploy the API proxies to the Mule runtimes
  
• Redeploy the API implementations to the same servers running the Mule runtimes
  
• Add an additional endpoint to each API for partner-enablement consumption
  
• Duplicate the APIs as Mule applications, then deploy them to the Mule runtimes
  

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 new upstream API Is being designed to offer an SLA of 500 ms median and 800 ms maximum (99th percentile) response time. The corresponding API implementation needs to sequentially invoke 3 downstream APIs of very similar complexity.The first of these downstream APIs offers the following SLA for its response time: median: 100 ms, 80th percentile: 500 ms, 95th percentile: 1000 ms.If possible, how can a timeout be set in the upstream API for the invocation of the first downstream API to meet the new upstream API's desired SLA?

• Set a timeout of 50 ms; this times out more invocations of that API but gives additional room for retries
  
• Set a timeout of 100 ms; that leaves 400 ms for the other two downstream APIs to complete
  
• No timeout is possible to meet the upstream API's desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API
  
• Do not set a timeout; the Invocation of this API Is mandatory and so we must wait until it responds
  

When must an API implementation be deployed to an Anypoint VPC?

• When the API Implementation must invoke publicly exposed services that are deployed outside of CloudHub in a customer- managed AWS instance
  
• When the API implementation must be accessible within a subnet of a restricted customer-hosted network that does not allow public access
  
• When the API implementation must be deployed to a production AWS VPC using the Mule Maven plugin
  
• When the API Implementation must write to a persistent Object Store
  

An organization has created an API-led architecture that uses various API layers to integrate mobile clients with a backend system. The backend system consists of a number of specialized components and can be accessed via a REST API. The process and experience APIs share the same bounded-context model that is different from the backend data model. What additional canonical models, bounded-context models, or anti-corruption layers are best added to this architecture to help process data consumed from the backend system?

• Create a bounded-context model for every layer and overlap them when the boundary contexts overlap, letting API developers know about the differences between upstream and downstream data models
  
• Create a canonical model that combines the backend and API-led models to simplify and unify data models, and minimize data transformations.
  
• Create a bounded-context model for the system layer to closely match the backend data model, and add an anti-corruption layer to let the different bounded contexts cooperate across the system and process layers
  
• Create an anti-corruption layer for every API to perform transformation for every data model to match each other, and let data simply travel between APIs to avoid the complexity and overhead of building canonical models
  

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
  

Once an API Implementation is ready and the API is registered on API Manager, who should request the access to the API on Anypoint Exchange?

• None
  
• Both
  
• API Client
  
• API Consumer
  

An organization is deploying their new implementation of the OrderStatus System API to multiple workers in CloudHub. This API fronts the organization's on-premises Order Management System, which is accessed by the API implementation over an IPsec tunnel.What type of error typically does NOT result in a service outage of the OrderStatus System API?

• A CloudHub worker fails with an out-of-memory exception
  
• API Manager has an extended outage during the initial deployment of the API implementation
  
• The AWS region goes offline with a major network failure to the relevant AWS data centers
  
• The Order Management System is Inaccessible due to a network outage in the organization's on-premises data center
  

Version 3.0.1 of a REST API implementation represents time values in PST time using ISO 8601 hh:mm:ss format. The API implementation needs to be changed to instead represent time values in CEST time using ISO 8601 hh:mm:ss format. When following the semver.org semantic versioning specification, what version should be assigned to the updated API implementation?

• 3.0.2
  
• 4.0.0
  
• 3.1.0
  
• 3.0.1
  

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