Try Free and Start Using Realistic Verified MCPA-Level-1 Dumps Instantly
MCPA-Level-1 Actual Questions - Instant Download 97 Questions
NEW QUESTION 24
Refer to the exhibit.
What is the best way to decompose one end-to-end business process into a collaboration of Experience, Process, and of System APIs?
- A. Use a Process API to orchestrate calls to multiple System APIs, but NOT to other Process APIs.
- B. Handle customizations for the end-user application at the Process API level rather than the Experience API level.
- C. Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs.
- D. Always use a tiered approach by creating exactly one API for each of the 3 layers (Experience, Process and System APIs).
Answer: D
NEW QUESTION 25
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
- A. Option C
- B. Option D
- C. Option A
- D. Option B
Answer: D
NEW QUESTION 26
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?
- A. IPwhitelist
- B. SLA-based rate limiting
- C. Auth 2 token enforcement
- D. Client ID enforcement
Answer: A
Explanation:
Explanation
https://dzone.com/articles/how-to-secure-apis
NEW QUESTION 27
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. The FQDNs are determined by the application name chosen, IRRESPECTIVE of the region
- B. The FQDNs are determined by both the application name and the Anypoint Platform organization
- C. A fixed number of FQDNs are created, IRRESPECTIVE of the environment and VPC design
- D. The FQDNs are determined by the application name, but can be modified by an administrator after deployment
Answer: A
Explanation:
Correct answer: The FQDNs are determined by the application name chosen, IRRESPECTIVE of the region
*****************************************
>> When deploying applications to Shared Worker Cloud, the FQDN are always determined by application name chosen.
>> It does NOT matter what region the app is being deployed to.
>> Although it is fact and true that the generated FQDN will have the region included in it (Ex: exp-salesorder-api.au-s1.cloudhub.io), it does NOT mean that the same name can be used when deploying to another CloudHub region.
>> Application name should be universally unique irrespective of Region and Organization and solely determines the FQDN for Shared Load Balancers.
NEW QUESTION 28
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. A higher number of discoverable API-related assets in the application network
- B. An overall tower usage of resources because each fine-grained API consumes less resources
- C. A better response time for the end user as a result of the APIs being smaller in scope and complexity
- D. A decrease in the number of connections within the application network supporting the business process
Answer: C
NEW QUESTION 29
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. A better response time for the end user as a result of the APIs being smaller in scope and complexity
- B. A higher number of discoverable API-related assets in the application network
- C. An overall tower usage of resources because each fine-grained API consumes less resources
- D. A decrease in the number of connections within the application network supporting the business process
Answer: C
NEW QUESTION 30
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?
- A. 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
- B. 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
- C. Implement an anti-corruption layer in the Order API that transforms the Product API data model into internal data types of the Order API
- D. 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
Answer: C
Explanation:
Correct answer: Convince the development team of the product API to adopt the API data model of the Order API such that integration logic of the Order API can work with one consistent internal data model
*****************************************
Key details to note from the given scenario:
>> Power relationship between Order API and Product API is customer/supplier So, as per below rules of "Power Relationships", the caller (in this case Order API) would request for features to the called (Product API team) and the Product API team would need to accomodate those requests.
NEW QUESTION 31
What condition requires using a CloudHub Dedicated Load Balancer?
- A. When custom DNS names are required for API implementations deployed to customer-hosted Mule runtimes
- B. When server-side load-balanced TLS mutual authentication is required between API implementations and API clients
- C. When API invocations across multiple CloudHub workers must be load balanced
- D. When cross-region load balancing is required between separate deployments of the same Mule application
Answer: A
NEW QUESTION 32
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?
- A. From the Mule runtime or the API Manager, depending on the type of data
- B. From various components of Anypoint Platform, such as the Shared Load Balancer, VPC, and Mule runtimes
- C. From the Mule runtime irrespective of the deployment model
- D. From the Mule runtime or the API implementation, depending on the deployment model
Answer: C
Explanation:
Correct answer: From the Mule runtime irrespective of the deployment model
*****************************************
>> Monitoring and Alerting metrics are always originated from Mule Runtimes irrespective of the deployment model.
>> It may seems that some metrics (Runtime Manager) are originated from Mule Runtime and some are (API Invocations/ API Analytics) from API Manager. However, this is realistically NOT TRUE. The reason is, API manager is just a management tool for API instances but all policies upon applying on APIs eventually gets executed on Mule Runtimes only (Either Embedded or API Proxy).
>> Similarly all API Implementations also run on Mule Runtimes.
So, most of the day required for monitoring and alerts are originated fron Mule Runtimes only irrespective of whether the deployment model is MuleSoft-hosted or Customer-hosted or Hybrid.
NEW QUESTION 33
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?
- A. 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
- B. Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order API
- C. Redirect client requests through an HTTP 307 Temporary Redirect status code to the fallback API whenever the Order API is unavailable
- D. 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
Answer: B
Explanation:
Correct answer: Search Anypoint exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the order API
*****************************************
>> It is not ideal and good approach, until unless there is a pre-approved agreement with the API clients that they will receive a HTTP 3xx temporary redirect status code and they have to implement fallback logic their side to call another API.
>> Creating separate entry of same Order API in API manager would just create an another instance of it on top of same API implementation. So, it does NO GOOD by using clone od same API as a fallback API. Fallback API should be ideally a different API implementation that is not same as primary one.
>> There is NO option currently provided by Anypoint HTTP Connector that allows us to invoke a fallback API when we receive certain HTTP status codes in response.
The only statement TRUE in the given options is to Search Anypoint exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the order API.
NEW QUESTION 34
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?
- A. The API producer should be contacted to understand the change to existing functionality
- B. The API client code ONLY needs to be changed if it needs to take advantage of new features
- C. The API producer should be requested to run the old version in parallel with the new one
- D. The update should be identified as a project risk and full regression testing of the functionality that uses this API should be run
Answer: B
NEW QUESTION 35
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?
- A. Implement a heartbeat/health check within the API and invoke it from outside the Anypoint Platform and alert when the heartbeat does not respond
- B. Handle API invocation exceptions within the calling API client and raise an alert from that API client when the API Is unavailable
- C. Create an alert for when the API receives no requests within a specified time period
- D. Configure a "worker not responding" alert in Anypoint Runtime Manager
Answer: D
Explanation:
Correct answer: Configure a "Worker not responding" alert in Anypoint Runtime Manager.
*****************************************
>> All the options eventually helps to generate the alert required when the application stops responding.
>> However, handling exceptions within calling API and then raising alert from API client is inappropriate and silly. There could be many API clients invoking the API implementation and it is not ideal to have this setup consistently in all of them. Not a realistic way to do.
>> Implementing a health check/ heartbeat with in the API and calling from outside to detmine the health sounds OK but needs extra setup for it and same time there are very good chances of generating false alarms when there are any intermittent network issues between external tool calling the health check API on API implementation. The API implementation itself may not have any issues but due to some other factors some false alarms may go out.
>> Creating an alert in API Manager when the API receives no requests within a specified time period would actually generate realistic alerts but even here some false alarms may go out when there are genuinely no requests from API clients.
The best and right way to achieve this requirement is to setup an alert on Runtime Manager with a condition "Worker not responding". This would generate an alert AS SOON AS the workers become unresponsive.
NEW QUESTION 36
What Mule application can have API policies applied by Anypoint Platform to the endpoint exposed by that Mule application?
- A. A Mule application that accepts JSON requests over WebSocket.
- B. A Mule application that accepts requests over HTTP/1x.
- C. A Mule application that accepts gRPC requests over HTTP/2
- D. A Mule application that accepts JSON requests over TCP but is NOT required to provide a response.
Answer: C
Explanation:
Explanation/Reference:
NEW QUESTION 37
What should be ensured before sharing an API through a public Anypoint Exchange portal?
- A. The API should be secured using one of the supported authentication/authorization mechanisms to ensure that data is not compromised
- B. The API should be functional with at least an initial implementation deployed and accessible for users to interact with
- C. The users needing access to the API should be added to the appropriate role in Anypoint Platform
- D. The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility
Answer: D
Explanation:
Correct answer: The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility.
*****************************************
Reference:
https://docs.mulesoft.com/exchange/to-share-api-asset-to-portal
NEW QUESTION 38
What API policy would be LEAST LIKELY used when designing an Experience API that is intended to work with a consumer mobile phone or tablet application?
- A. IPwhitellst
- B. OAuth 2.0 access token enforcement
- C. JSON threat protection
- D. Client ID enforcement
Answer: C
NEW QUESTION 39
What Anypoint Connectors support transactions?
- A. Database, VM, File
- B. Database, JMS, VM, SFTP
- C. Database, 3MS, HTTP
- D. Database, JMS, VM
Answer: D
NEW QUESTION 40
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?
- A. When there is one CloudHub deployment of the API implementation to three CloudHub workers that must share the cache state
- B. 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
- C. 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
- D. When there are three CloudHub deployments of the API implementation to three separate CloudHub regions that must share the cache state
Answer: B
NEW QUESTION 41
Which of the following sequence is correct?
- A. API Consumer implementes logic to call an API >> API Client requests access to API >> API Implementation routes the request to >> API
- B. API Consumer requests access to API >> API Client implementes logic to call an API >> API routes the request to >> API Implementation
- C. API Client implementes logic to call an API >> API Consumer requests access to API >> API routes the request to >> API Implementation
- D. API Client implementes logic to call an API >> API Consumer requests access to API >> API Implementation routes the request to >> API
Answer: B
Explanation:
Correct answer: API Consumer requests access to API >> API Client implementes logic to call an API >> API routes the request to >> API Implementation
*****************************************
>> API consumer does not implement any logic to invoke APIs. It is just a role. So, the option stating "API Consumer implementes logic to call an API" is INVALID.
>> API Implementation does not route any requests. It is a final piece of logic where functionality of target systems is exposed. So, the requests should be routed to the API implementation by some other entity. So, the options stating "API Implementation routes the request to >> API" is INVALID
>> The statements in one of the options are correct but sequence is wrong. The sequence is given as "API Client implementes logic to call an API >> API Consumer requests access to API >> API routes the request to >> API Implementation". Here, the statements in the options are VALID but sequence is WRONG.
>> Right option and sequence is the one where API consumer first requests access to API on Anypoint Exchange and obtains client credentials. API client then writes logic to call an API by using the access client credentials requested by API consumer and the requests will be routed to API implementation via the API which is managed by API Manager.
NEW QUESTION 42
What condition requires using a CloudHub Dedicated Load Balancer?
- A. When cross-region load balancing is required between separate deployments of the same Mule application
- B. When custom DNS names are required for API implementations deployed to customer-hosted Mule runtimes
- C. When server-side load-balanced TLS mutual authentication is required between API implementations and API clients
- D. When API invocations across multiple CloudHub workers must be load balanced
Answer: A
NEW QUESTION 43
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?
- A. iPaaS provisioned customer-hosted runtime plane and MuleSoft-hosted control plane
- B. MuleSoft-hosted runtime plane and customer-hosted control plane
- C. Manually provisioned customer-hosted runtime plane and MuleSoft-hosted control plane
- D. Manually provisioned customer-hosted runtime plane and customer-hosted control plane
Answer: D
Explanation:
Correct answer: Manually provisioned customer-hosted runtime plane and customer-hosted control plane
*****************************************
There are two key factors that are to be taken into consideration from the scenario given in the question.
>> Company requires both data and metadata to be resided within the corporate firewall
>> Company would like to go with customer-hosted infrastructure.
Any deployment model that is to deal with the cloud directly or indirectly (Mulesoft-hosted or Customer's own cloud like Azure, AWS) will have to share atleast the metadata.
Application data can be controlled inside firewall by having Mule Runtimes on customer hosted runtime plane. But if we go with Mulsoft-hosted/ Cloud-based control plane, the control plane required atleast some minimum level of metadata to be sent outside the corporate firewall.
As the customer requirement is pretty clear about the data and metadata both to be within the corporate firewall, even though customer wants to move to production as quickly as possible, unfortunately due to the nature of their security requirements, they have no other option but to go with manually provisioned customer-hosted runtime plane and customer-hosted control plane.
NEW QUESTION 44
The application network is recomposable: it is built for change because it "bends but does not break"
- A. TRUE
- B. FALSE
Answer: A
Explanation:
*****************************************
>> Application Network is a disposable architecture.
>> Which means, it can be altered without disturbing entire architecture and its components.
>> It bends as per requirements or design changes but does not break
NEW QUESTION 45
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?
- A. An AZ is randomly selected for a Mule application, and all the Mule application's CloudHub workers are assigned to that one AZ
- B. Workers are randomly distributed across available AZs within that region
- C. AZs are selected as part of the Mule application's deployment configuration
- D. Workers belonging to a given environment are assigned to the same AZ within that region
Answer: B
NEW QUESTION 46
An Anypoint Platform organization has been configured with an external identity provider (IdP) for identity management and client management. What credentials or token must be provided to Anypoint CLI to execute commands against the Anypoint Platform APIs?
- A. An OAuth 2.0 token generated using the credentials provided by the IdP for identity management
- B. The credentials provided by the IdP for identity management
- C. The credentials provided by the IdP for client management
- D. An OAuth 2.0 token generated using the credentials provided by the IdP for client management
Answer: B
Explanation:
Correct answer: The credentials provided by the IdP for identity management
*****************************************
Reference:
>> There is no support for OAuth 2.0 tokens from client/identity providers to authenticate via Anypoint CLI. Only possible tokens are "bearer tokens" that too only generated using Anypoint Organization/Environment Client Id and Secret from https://anypoint.mulesoft.com/accounts/login. Not the client credentials of client provider. So, OAuth 2.0 is not possible. More over, the token is mainly for API Manager purposes and not associated with a user. You can NOT use it to call most APIs (for example Cloudhub and etc) as per this Mulesoft Knowledge article.
>> The other option allowed by Anypoint CLI is to use client credentials. It is possible to use client credentials of a client provider but requires setting up Connected Apps in client management but such details are not given in the scenario explained in the question.
>> So only option left is to use user credentials from identify provider
NEW QUESTION 47
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?
- A. Persistent Object Store
- B. Redis distributed cache
- C. java.util.WeakHashMap
- D. File-based storage
Answer: A
NEW QUESTION 48
......
Download Free Latest Exam MCPA-Level-1 Certified Sample Questions: https://freedumps.validvce.com/MCPA-Level-1-exam-collection.html
