[Dec 31, 2022] Pass MCPA-Level-1 Review Guide, Reliable MCPA-Level-1 Test Engine [Q46-Q60]

5/5 - (1 vote)

[Dec 31, 2022] Pass MCPA-Level-1 Review Guide, Reliable MCPA-Level-1 Test Engine

MCPA-Level-1 Test Engine Practice Test Questions, Exam Dumps

NEW QUESTION 46
What best explains the use of auto-discovery in API implementations?

It makes API Manager aware of API implementations and hence enables it to enforce policies

It enables Anypoint Studio to discover API definitions configured in Anypoint Platform

It enables Anypoint Exchange to discover assets and makes them available for reuse

It enables Anypoint Analytics to gain insight into the usage of APIs

NEW QUESTION 47
A Mule application exposes an HTTPS endpoint and is deployed to the CloudHub Shared Worker Cloud. All traffic to that Mule application must stay inside the AWS VPC.
To what TCP port do API invocations to that Mule application need to be sent?

443

8081

8091

8082

NEW QUESTION 48
A Mule application exposes an HTTPS endpoint and is deployed to the CloudHub Shared Worker Cloud. All traffic to that Mule application must stay inside the AWS VPC.
To what TCP port do API invocations to that Mule application need to be sent?

443

8081

8091

8092

NEW QUESTION 49
An API implementation is updated. When must the RAML definition of the API also be updated?

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

NEW QUESTION 50
Refer to the exhibit.

Three business processes need to be implemented, and the implementations need to communicate with several different SaaS applications.
These processes are owned by separate (siloed) LOBs and are mainly independent of each other, but do share a few business entities. Each LOB has one development team and their own budget In this organizational context, what is the most effective approach to choose the API data models for the APIs that will implement these business processes with minimal redundancy of the data models?
A) Build several Bounded Context Data Models that align with coherent parts of the business processes and the definitions of associated business entities

B) Build distinct data models for each API to follow established micro-services and Agile API-centric practices

C) Build all API data models using XML schema to drive consistency and reuse across the organization

D) Build one centralized Canonical Data Model (Enterprise Data Model) that unifies all the data types from all three business processes, ensuring the data model is consistent and non-redundant

Option A

Option B

Option C

Option D

NEW QUESTION 51
Which layer in the API-led connectivity focuses on unlocking key systems, legacy systems, data sources etc and exposes the functionality?

Experience Layer

Process Layer

System Layer

NEW QUESTION 52
What correctly characterizes unit tests of Mule applications?

They test the validity of input and output of source and target systems

They must be run in a unit testing environment with dedicated Mule runtimes for the environment

They must be triggered by an external client tool or event source

They are typically written using MUnit to run in an embedded Mule runtime that does not require external connectivity

NEW QUESTION 53
Refer to the exhibit. An organization needs to enable access to their customer data from both a mobile app and a web application, which each need access to common fields as well as certain unique fields.
The data is available partially in a database and partially in a 3rd-party CRM system.
What APIs should be created to best fit these design requirements?

A) A Process API that contains the data required by both the web and mobile apps, allowing these applications to invoke it directly and access the data they need thereby providing the flexibility to add more fields in the future without needing API changes

B) One set of APIs (Experience API, Process API, and System API) for the web app, and another set for the mobile app

C) Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system

D) A common Experience API used by both the web and mobile apps, but separate Process APIs for the web and mobile apps that interact with the database and the CRM System

Option A

Option B

Option C

Option D

NEW QUESTION 54
Refer to the exhibit.

Three business processes need to be implemented, and the implementations need to communicate with several different SaaS applications.
These processes are owned by separate (siloed) LOBs and are mainly independent of each other, but do share a few business entities. Each LOB has one development team and their own budget In this organizational context, what is the most effective approach to choose the API data models for the APIs that will implement these business processes with minimal redundancy of the data models?
A) Build several Bounded Context Data Models that align with coherent parts of the business processes and the definitions of associated business entities

B) Build distinct data models for each API to follow established micro-services and Agile API-centric practices

C) Build all API data models using XML schema to drive consistency and reuse across the organization

D) Build one centralized Canonical Data Model (Enterprise Data Model) that unifies all the data types from all three business processes, ensuring the data model is consistent and non-redundant

Option A

Option B

Option C

Option D

NEW QUESTION 55
The implementation of a Process API must change.
What is a valid approach that minimizes the impact of this change on API clients?

Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition.

Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version.

Implement required changes to the Process API implementation so that, whenever possible, the Process API’s RAML definition remains unchanged.

Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 – Moved Permanentlyto inform API clients they should be calling the new API implementation.

NEW QUESTION 56
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

NEW QUESTION 57
What Mule application deployment scenario requires using Anypoint Platform Private Cloud Edition or Anypoint Platform for Pivotal Cloud Foundry?

When it Is required to make ALL applications highly available across multiple data centers

When it is required that ALL APIs are private and NOT exposed to the public cloud

When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data

When ALL backend systems in the application network are deployed in the organization’s intranet

NEW QUESTION 58
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

NEW QUESTION 59
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

Correct answer: 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
*****************************************
There is one important consideration to be noted in the question which is – System API in DR environment provides only 20% of the rate limiting offered by the primary environment. So, comparitively, very less calls will be allowed into the DR environment API opposed to its primary environment. With this in mind, lets analyse what is the right and best fault-tolerant invocation strategy.
1. Invoking both the system APIs in parallel is definitely NOT a feasible approach because of the 20% limitation we have on DR environment. Calling in parallel every time would easily and quickly exhaust the rate limits on DR environment and may not give chance to genuine intermittent error scenarios to let in during the time of need.
2. Another option given is suggesting to add timeout and retry logic to process API while invoking primary environment’s system API. This is good so far. However, when all retries failed, the option is suggesting to invoke the copy of process API on DR environment which is not right or recommended. Only system API is the one to be considered for fallback and not the whole process API. Process APIs usually have lot of heavy orchestration calling many other APIs which we do not want to repeat again by calling DR’s process API. So this option is NOT right.
3. One more option given is suggesting to add the retry (no timeout) logic to process API to directly retry on DR environment’s system API instead of retrying the primary environment system API first. This is not at all a proper fallback. A proper fallback should occur only after all retries are performed and exhausted on Primary environment first. But here, the option is suggesting to directly retry fallback API on first failure itself without trying main API. So, this option is NOT right too.
This leaves us one option which is right and best fit.
– Invoke the system API deployed to the primary environment
– Add Timeout and Retry logic on it in process API
– If it fails even after all retries, then invoke the system API deployed to the DR environment.

NEW QUESTION 60
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?