Ultimate Guide to the MCPA-Level-1 - Latest Oct 02, 2024 Edition Available Now [Q47-Q61] : Exams Labs Braindumps : http://blog.examslabs.com

NEW QUESTION 47
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 48
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

NEW QUESTION 49
In which layer of API-led connectivity, does the business logic orchestration reside?

System Layer

Experience Layer

Process Layer

NEW QUESTION 50
What CANNOT be effectively enforced using an API policy in Anypoint Platform?

Guarding against Denial of Service attacks

Maintaining tamper-proof credentials between APIs

Logging HTTP requests and responses

Backend system overloading

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

NEW QUESTION 52
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 53
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?

IP whitelist

SLA-based rate limiting

OAuth 2 token enforcement

Client ID enforcement

NEW QUESTION 54
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 55
Due to a limitation in the backend system, a system API can only handle up to 500 requests per second. What is the best type of API policy to apply to the system API to avoid overloading the backend system?

Rate limiting

HTTP caching

Rate limiting – SLA based

Spike control

NEW QUESTION 56
An organization is implementing a Quote of the Day API that caches today’s quote.

What scenario can use the GoudHub Object Store via the Object Store connector to persist the cache’s state?

When there are three CloudHub deployments of the API implementation to three separate CloudHub regions that must share the cache state

When there are two CloudHub deployments of the API implementation by two Anypoint Platform business groups to the same CloudHub region that must share the cache state

When there is one deployment of the API implementation to CloudHub and anottV deployment to a customer-hosted Mule runtime that must share the cache state

When there is one CloudHub deployment of the API implementation to three CloudHub workers that must share the cache state

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

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

Each modern API must be REST and HTTP based.

NEW QUESTION 59
When designing an upstream API and its implementation, the development team has been advised to NOT set timeouts when invoking a downstream API, because that downstream API has no SLA that can be relied upon.
This is the only downstream API dependency of that upstream API.
Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?

An SLA for the upstream API CANNOT be provided

The invocation of the downstream API will run to completion without timing out

A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes

A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes

NEW QUESTION 60
Traffic is routed through an API proxy to an API implementation. The API proxy is managed by API Manager and the API implementation is deployed to a CloudHub VPC using Runtime Manager. API policies have been applied to this API. In this deployment scenario, at what point are the API policies enforced on incoming API client requests?

At the API proxy

At the API implementation

At both the API proxy and the API implementation

At a MuleSoft-hosted load balancer

NEW QUESTION 61
When designing an upstream API and its implementation, the development team has been advised to NOT set timeouts when invoking a downstream API, because that downstream API has no SLA that can be relied upon.
This is the only downstream API dependency of that upstream API.

Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?

An SLA for the upstream API CANNOT be provided

The invocation of the downstream API will run to completion without timing out

A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes

A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes