[Oct-2022] Pass MuleSoft MCPA-Level-1 Exam in First Attempt Guaranteed! [Q25-Q47]

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

Q26. Refer to the exhibit. An organization is running a Mule standalone runtime and has configured Active Directory as the Anypoint Platform external Identity Provider. The organization does not have budget for other system components.

What policy should be applied to all instances of APIs in the organization to most effecuvelyKestrict access to a specific group of internal users?

Apply a basic authentication – LDAP policy; the internal Active Directory will be configured as the LDAP source for authenticating users

Apply a client ID enforcement policy; the specific group of users will configure their client applications to use their specific client credentials

Apply an IP whitelist policy; only the specific users’ workstations will be in the whitelist

Apply an OAuth 2.0 access token enforcement policy; the internal Active Directory will be configured as the OAuth server

Q27. An organization wants MuleSoft-hosted runtime plane features (such as HTTP load balancing, zero downtime, and horizontal and vertical scaling) in its Azure environment. What runtime plane minimizes the organization’s effort to achieve these features?

Anypoint Runtime Fabric

Anypoint Platform for Pivotal Cloud Foundry

CloudHub

A hybrid combination of customer-hosted and MuleSoft-hosted Mule runtimes

Q28. 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 Permanently to inform API clients they should be calling the new API implementation

Q29. Refer to the exhibit.

What is the best way to decompose one end-to-end business process into a collaboration of Experience, Process, and System APIs?
A) Handle customizations for the end-user application at the Process API level rather than the Experience API level

B) Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs

C) Always use a tiered approach by creating exactly one API for each of the 3 layers (Experience, Process and System APIs)

D) Use a Process API to orchestrate calls to multiple System APIs, but NOT to other Process APIs

Option A

Option B

Option C

Option D

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

Q31. Refer to the exhibit.

A RAML definition has been proposed for a new Promotions Process API, and has been published to Anypoint Exchange.
The Marketing Department, who will be an important consumer of the Promotions API, has important requirements and expectations that must be met.
What is the most effective way to use Anypoint Platform features to involve the Marketing Department in this early API design phase?
A) Ask the Marketing Department to interact with a mocking implementation of the API using the automatically generated API Console

B) Organize a design workshop with the DBAs of the Marketing Department in which the database schema of the Marketing IT systems is translated into RAML

C) Use Anypoint Studio to Implement the API as a Mule application, then deploy that API implementation to CloudHub and ask the Marketing Department to interact with it

D) Export an integration test suite from API designer and have the Marketing Department execute the tests In that suite to ensure they pass

Option A

Option B

Option C

Option D

Q32. An organization makes a strategic decision to move towards an IT operating model that emphasizes consumption of reusable IT assets using modern APIs (as defined by MuleSoft).
What best describes each modern API in relation to this new IT operating model?

Each modern API has its own software development lifecycle, which reduces the need for documentation and automation

Each modem API must be treated like a product and designed for a particular target audience (for instance, mobile app developers)

Each modern API must be easy to consume, so should avoid complex authentication mechanisms such as SAML or JWT D

Each modern API must be REST and HTTP based

Q33. Say, there is a legacy CRM system called CRM-Z which is offering below functions:
1. Customer creation
2. Amend details of an existing customer
3. Retrieve details of a customer
4. Suspend a customer

Implement a system API named customerManagement which has all the functionalities wrapped in it as various operations/resources

Implement different system APIs named createCustomer, amendCustomer, retrieveCustomer and suspendCustomer as they are modular and has seperation of concerns

Implement different system APIs named createCustomerInCRMZ, amendCustomerInCRMZ, retrieveCustomerFromCRMZ and suspendCustomerInCRMZ as they are modular and has seperation of concerns

Q34. Refer to the exhibit.

What is a valid API in the sense of API-led connectivity and application networks?

Java RMI over TCP

XML over HTTP

CORBA over IIOP

XML over UDP

Q35. An API implementation is deployed on a single worker on CloudHub and invoked by external API clients (outside of CloudHub). How can an alert be set up that is guaranteed to trigger AS SOON AS that API implementation stops responding to API invocations?

Implement a heartbeat/health check within the API and invoke it from outside the Anypoint Platform and alert when the heartbeat does not respond

Configure a “worker not responding” alert in Anypoint Runtime Manager

Handle API invocation exceptions within the calling API client and raise an alert from that API client when the API Is unavailable

Create an alert for when the API receives no requests within a specified time period

Q36. 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 API’s 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 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

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

Q38. What condition requires using a CloudHub Dedicated Load Balancer?

When cross-region load balancing is required between separate deployments of the same Mule application

When custom DNS names are required for API implementations deployed to customer-hosted Mule runtimes

When API invocations across multiple CloudHub workers must be load balanced

When server-side load-balanced TLS mutual authentication is required between API implementations and API clients

Q39. An Order API must be designed that contains significant amounts of integration logic and involves the invocation of the Product API.
The power relationship between Order API and Product API is one of “Customer/Supplier”, because the Product API is used heavily throughout the organization and is developed by a dedicated development team located in the office of the CTO.
What strategy should be used to deal with the API data model of the Product API within the Order API?

Convince the development team of the Product API to adopt the API data model of the Order API such that the integration logic of the Order API can work with one consistent internal data model

Work with the API data types of the Product API directly when implementing the integration logic of the Order API such that the Order API uses the same (unchanged) data types as the Product API

Implement an anti-corruption layer in the Order API that transforms the Product API data model into internal data types of the Order API

Start an organization-wide data modeling initiative that will result in an Enterprise Data Model that will then be used in both the Product API and the Order API

Q40. What do the API invocation metrics provided by Anypoint Platform provide?

ROI metrics from APIs that can be directly shared with business users

Measurements of the effectiveness of the application network based on the level of reuse

Data on past API invocations to help identify anomalies and usage patterns across various APIs

Proactive identification of likely future policy violations that exceed a given threat threshold

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

Q42. What should be ensured before sharing an API through a public Anypoint Exchange portal?

The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility

The users needing access to the API should be added to the appropriate role in Anypoint Platform

The API should be functional with at least an initial implementation deployed and accessible for users to interact with

The API should be secured using one of the supported authentication/authorization mechanisms to ensure that data is not compromised

Q43. Refer to the exhibit.

What is a valid API in the sense of API-led connectivity and application networks?
A) Java RMI over TCP

B) Java RMI over TCP

C) CORBA over HOP

D) XML over UDP

Option A

Option B

Option C

Option D

Q44. When using CloudHub with the Shared Load Balancer, what is managed EXCLUSIVELY by the API implementation (the Mule application) and NOT by Anypoint Platform?

The assignment of each HTTP request to a particular CloudHub worker

The logging configuration that enables log entries to be visible in Runtime Manager

The SSL certificates used by the API implementation to expose HTTPS endpoints

The number of DNS entries allocated to the API implementation

Q45. How are an API implementation, API client, and API consumer combined to invoke and process an API?

The API consumer creates an API implementation, which receives API invocations from an API such that they are processed for an API client

The API client creates an API consumer, which receives API invocations from an API such that they are processed for an API implementation

The ApI consumer creates an API client, which sends API invocations to an API such that they are processed by an API implementation

The ApI client creates an API consumer, which sends API invocations to an API such that they are processed by an API implementation

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

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

Leave a Reply Cancel reply