Exam Code : MCPA-Level-1
Exam Name : MuleSoft Certified Platform Architect - Level 1
Vendor Name :
"MuleSoft"
MCPA-Level-1 Dumps MCPA-Level-1 Braindumps
MCPA-Level-1 Real Questions MCPA-Level-1 Practice Test MCPA-Level-1 dumps free
MuleSoft Certified Platform Architect – Level 1
https://killexams.com/pass4sure/exam-detail/MCPA-Level-1
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 pluginD. When the API implementation must write to a persistent Object Store
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 be 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.
Reference: https://docs.mulesoft.com/eu-control-plane/
The API endpoint does NOT change in the new version.
How should the developer of an API client respond to this change?
The update should be identified as a project risk and full regression testing of the functionality that uses this API should be run.
The API producer should be contacted to understand the change to existing functionality.
The API producer should be requested to run the old version in parallel with the new one.
The API client code ONLY needs to be changed if it needs to take advantage of new features.
Reference: https://docs.mulesoft.com/exchange/to-change-raml-version
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.
When could the API data model of a System API reasonably mimic the data model exposed by the corresponding backend system, with minimal improvements over the backend system's data model?
When there is an existing Enterprise Data Model widely used across the organization.
When the System API can be assigned to a bounded context with a corresponding data model.
When a pragmatic approach with only limited isolation from the backend system is deemed appropriate.
When the corresponding backend system is expected to be replaced in the near future.
Refer to the exhibit.
An organization uses one specific CloudHub (AWS) region for all CloudHub deployments.
How are CloudHub workers assigned to availability zones (AZs) when the organization's Mule applications are deployed to CloudHub in that region?
Workers belonging to a given environment are assigned to the same AZ within that region.
AZs are selected as part of the Mule application's deployment configuration.
Workers are randomly distributed across available AZs within that region.
An AZ is randomly selected for a Mule application, and all the Mule application's CloudHub workers are assigned to that one AZ.
The test needs all source and/or target systems configured and accessible.
The test runs immediately after the Mule application has been compiled and packaged.
The test is triggered by an external HTTP request.
The test prepares a known request payload and validates the response payload.
When the API implementation changes the structure of the request or response messages.
When the API implementation changes from interacting with a legacy backend system deployed on-premises to a modern, cloud-based (SaaS) system.
When the API implementation is migrated from an older to a newer version of the Mule runtime.
When the API implementation is optimized to improve its average response time.
A Mule application that accepts JSON requests over TCP but is NOT required to provide a response.
A Mule application that accepts JSON requests over WebSocket.
A Mule application that accepts gRPC requests over HTTP/2