(2023) PASS MCPA-Level-1-Maintenance Exam Free Practice Test with 100% Accurate Answers [Q13-Q27]

Q13. What is a key requirement when using an external Identity Provider for Client Management in Anypoint Platform?

Single sign-on is required to sign in to Anypoint Platform

The application network must include System APIs that interact with the Identity Provider

To invoke OAuth 2.0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider

APIs managed by Anypoint Platform must be protected by SAML 2.0 policies

Q14. An organization uses various cloud-based SaaS systems and multiple on-premises systems. The on-premises systems are an important part of the organization’s application network and can only be accessed from within the organization’s intranet.
What is the best way to configure and use Anypoint Platform to support integrations with both the cloud-based SaaS systems and on-premises systems?
A) Use CloudHub-deployed Mule runtimes in an Anypoint VPC managed by Anypoint Platform Private Cloud Edition control plane

B) Use CloudHub-deployed Mule runtimes in the shared worker cloud managed by the MuleSoft-hosted Anypoint Platform control plane

C) Use an on-premises installation of Mule runtimes that are completely isolated with NO external network access, managed by the Anypoint Platform Private Cloud Edition control plane

D) Use a combination of Cloud Hub-deployed and manually provisioned on-premises Mule runtimes managed by the MuleSoft-hosted Anypoint Platform control plane

Option A

Option B

Option C

Option D

Q15. A company wants to move its Mule API implementations into production as quickly as possible. To protect access to all Mule application data and metadata, the company requires that all Mule applications be deployed to the company’s customer-hosted infrastructure within the corporate firewall. What combination of runtime plane and control plane options meets these project lifecycle goals?

Manually provisioned customer-hosted runtime plane and customer-hosted control plane

MuleSoft-hosted runtime plane and customer-hosted control plane

Manually provisioned customer-hosted runtime plane and MuleSoft-hosted control plane

iPaaS provisioned customer-hosted runtime plane and MuleSoft-hosted control plane

Q16. What is typically NOT a function of the APIs created within the framework called API-led connectivity?

They provide an additional layer of resilience on top of the underlying backend system, thereby insulating clients from extended failure of these systems.

They allow for innovation at the user Interface level by consuming the underlying assets without being aware of how data Is being extracted from backend systems.

They reduce the dependency on the underlying backend systems by helping unlock data from backend systems In a reusable and consumable way.

They can compose data from various sources and combine them with orchestration logic to create higher level value.

Q17. 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

Q18. Refer to the exhibit.

what is true when using customer-hosted Mule runtimes with the MuleSoft-hosted Anypoint Platform control plane (hybrid deployment)?

Anypoint Runtime Manager initiates a network connection to a Mule runtime in order to deploy Mule applications

The MuleSoft-hosted Shared Load Balancer can be used to load balance API invocations to the Mule runtimes

API implementations can run successfully in customer-hosted Mule runtimes, even when they are unable to communicate with the control plane

Anypoint Runtime Manager automatically ensures HA in the control plane by creating a new Mule runtime instance in case of a node failure

Q19. 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

Q20. 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

When a pragmatic approach with only limited isolation from the backend system is deemed appropriate.
*****************************************
General guidance w.r.t choosing Data Models:
>> If an Enterprise Data Model is in use then the API data model of System APIs should make use of data types from that Enterprise Data Model and the corresponding API implementation should translate between these data types from the Enterprise Data Model and the native data model of the backend system.
>> If no Enterprise Data Model is in use then each System API should be assigned to a Bounded Context, the API data model of System APIs should make use of data types from the corresponding Bounded Context Data Model and the corresponding API implementation should translate between these data types from the Bounded Context Data Model and the native data model of the backend system. In this scenario, the data types in the Bounded Context Data Model are defined purely in terms of their business characteristics and are typically not related to the native data model of the backend system. In other words, the translation effort may be significant.
>> If no Enterprise Data Model is in use, and the definition of a clean Bounded Context Data Model is considered too much effort, then the API data model of System APIs should make use of data types that approximately mirror those from the backend system, same semantics and naming as backend system, lightly sanitized, expose all fields needed for the given System API’s functionality, but not significantly more and making good use of REST conventions.
The latter approach, i.e., exposing in System APIs an API data model that basically mirrors that of the backend system, does not provide satisfactory isolation from backend systems through the System API tier on its own.
In particular, it will typically not be possible to “swap out” a backend system without significantly changing all System APIs in front of that backend system and therefore the API implementations of all Process APIs that depend on those System APIs! This is so because it is not desirable to prolong the life of a previous backend system’s data model in the form of the API data model of System APIs that now front a new backend system.
The API data models of System APIs following this approach must therefore change when the backend system is replaced.
On the other hand:
>> It is a very pragmatic approach that adds comparatively little overhead over accessing the backend system directly
>> Isolates API clients from intricacies of the backend system outside the data model (protocol, authentication, connection pooling, network address, …)
>> Allows the usual API policies to be applied to System APIs
>> Makes the API data model for interacting with the backend system explicit and visible, by exposing it in the RAML definitions of the System APIs
>> Further isolation from the backend system data model does occur in the API implementations of the Process API tier

Q21. What are 4 important Platform Capabilities offered by Anypoint Platform?

API Versioning, API Runtime Execution and Hosting, API Invocation, API Consumer Engagement

API Design and Development, API Runtime Execution and Hosting, API Versioning, API Deprecation

API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement

API Design and Development, API Deprecation, API Versioning, API Consumer Engagement

Q22. What is the most performant out-of-the-box solution in Anypoint Platform to track transaction state in an asynchronously executing long-running process implemented as a Mule application deployed to multiple CloudHub workers?

Redis distributed cache

java.util.WeakHashMap

Persistent Object Store

File-based storage

Q23. 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

Q24. A System API is designed to retrieve data from a backend system that has scalability challenges. What API policy can best safeguard the backend system?

IPwhitelist

SLA-based rate limiting

Auth 2 token enforcement

Client ID enforcement

Q25. True or False. We should always make sure that the APIs being designed and developed are self-servable even if it needs more man-day effort and resources.

FALSE

TRUE

Q26. What is true about automating interactions with Anypoint Platform using tools such as Anypoint Platform REST APIs, Anypoint CU, or the Mule Maven plugin?

Access to Anypoint Platform APIs and Anypoint CU can be controlled separately through the roles and permissions in Anypoint Platform, so that specific users can get access to Anypoint CLI white others get access to the platform APIs

Anypoint Platform APIs can ONLY automate interactions with CloudHub, while the Mule Maven plugin is required for deployment to customer-hosted Mule runtimes

By default, the Anypoint CLI and Mule Maven plugin are NOT included in the Mule runtime, so are NOT available to be used by deployed Mule applications

API policies can be applied to the Anypoint Platform APIs so that ONLY certain LOBs have access to specific functions

Q27. What best describes the Fully Qualified Domain Names (FQDNs), also known as DNS entries, created when a Mule application is deployed to the CloudHub Shared Worker Cloud?

A fixed number of FQDNs are created, IRRESPECTIVE of the environment and VPC design

The FQDNs are determined by the application name chosen, IRRESPECTIVE of the region

The FQDNs are determined by the application name, but can be modified by an administrator after deployment

The FQDNs are determined by both the application name and the Anypoint Platform organization