MuleSoft Certified Platform Architect MCPA-Level-1 Dumps Full Questions with Free PDF Questions to Pass [Q41-Q63] : Latest Exam Prep : http://certify.vceprep.com

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

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

NEW QUESTION 43
The responses to some HTTP requests can be cached depending on the HTTP verb used in the request. According to the HTTP specification, for what HTTP verbs is this safe to do?

PUT, POST, DELETE

GET, HEAD, POST

GET, PUT, OPTIONS

GET, OPTIONS, HEAD

NEW QUESTION 44
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 45
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 46
An organization wants to make sure only known partners can invoke the organization’s APIs. To achieve this security goal, the organization wants to enforce a Client ID Enforcement policy in API Manager so that only registered partner applications can invoke the organization’s APIs. In what type of API implementation does MuleSoft recommend adding an API proxy to enforce the Client ID Enforcement policy, rather than embedding the policy directly in the application’s JVM?

A Mule 3 application using APIkit

A Mule 3 or Mule 4 application modified with custom Java code

A Mule 4 application with an API specification

A Non-Mule application

NEW QUESTION 47
An API experiences a high rate of client requests (TPS) vwth small message paytoads. How can usage limits be imposed on the API based on the type of client application?

Use an SLA-based rate limiting policy and assign a client application to a matching SLA tier based on its type

Use a spike control policy that limits the number of requests for each client application type

Use a cross-origin resource sharing (CORS) policy to limit resource sharing between client applications, configured by the client application type

Use a rate limiting policy and a client ID enforcement policy, each configured by the client application type

NEW QUESTION 48
A code-centric API documentation environment should allow API consumers to investigate and execute API client source code that demonstrates invoking one or more APIs as part of representative scenarios.
What is the most effective way to provide this type of code-centric API documentation environment using Anypoint Platform?

Enable mocking services for each of the relevant APIs and expose them via their Anypoint Exchange entry

Ensure the APIs are well documented through their Anypoint Exchange entries and API Consoles and share these pages with all API consumers

Create API Notebooks and include them in the relevant Anypoint Exchange entries

Make relevant APIs discoverable via an Anypoint Exchange entry

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

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

NEW QUESTION 51
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 52
In an organization, the InfoSec team is investigating Anypoint Platform related data traffic.
From where does most of the data available to Anypoint Platform for monitoring and alerting originate?

From the Mule runtime or the API implementation, depending on the deployment model

From various components of Anypoint Platform, such as the Shared Load Balancer, VPC, and Mule runtimes

From the Mule runtime or the API Manager, depending on the type of data

From the Mule runtime irrespective of the deployment model

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

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

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

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

NEW QUESTION 57
An API implementation is being designed that must invoke an Order API, which is known to repeatedly experience downtime.
For this reason, a fallback API is to be called when the Order API is unavailable.
What approach to designing the invocation of the fallback API provides the best resilience?

Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order API

Create a separate entry for the Order API in API Manager, and then invoke this API as a fallback API if the primary Order API is unavailable

Redirect client requests through an HTTP 307 Temporary Redirect status code to the fallback API whenever the Order API is unavailable

Set an option in the HTTP Requester component that invokes the Order API to instead invoke a fallback API whenever an HTTP 4xx or 5xx response status code is returned from the Order API

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

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

NEW QUESTION 60
A company uses a hybrid Anypoint Platform deployment model that combines the EU control plane with customer-hosted Mule runtimes. After successfully testing a Mule API implementation in the Staging environment, the Mule API implementation is set with environment-specific properties and must be promoted to the Production environment. What is a way that MuleSoft recommends to configure the Mule API implementation and automate its promotion to the Production environment?

Bundle properties files for each environment into the Mule API implementation’s deployable archive, then promote the Mule API implementation to the Production environment using Anypoint CLI or the Anypoint Platform REST APIsB.

Modify the Mule API implementation’s properties in the API Manager Properties tab, then promote the Mule API implementation to the Production environment using API Manager

Modify the Mule API implementation’s properties in Anypoint Exchange, then promote the Mule API implementation to the Production environment using Runtime Manager

Use an API policy to change properties in the Mule API implementation deployed to the Staging environment and another API policy to deploy the Mule API implementation to the Production environment

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

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

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