[Apr-2023] MCPA-Level-1 Dumps With 100% Verified Q&As - Pass Guarantee or Full Refund
Pass MuleSoft MCPA-Level-1 Exam With Practice Test Questions Dumps Bundle
NEW QUESTION # 58
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?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: B
Explanation:
Correct answer: 8082
*****************************************
>> 8091 and 8092 ports are to be used when keeping your HTTP and HTTPS app private to the LOCAL VPC respectively.
>> Above TWO ports are not for Shared AWS VPC/ Shared Worker Cloud.
>> 8081 is to be used when exposing your HTTP endpoint app to the internet through Shared LB
>> 8082 is to be used when exposing your HTTPS endpoint app to the internet through Shared LB So, API invocations should be sent to port 8082 when calling this HTTPS based app.
References:
https://docs.mulesoft.com/runtime-manager/cloudhub-networking-guide
https://help.mulesoft.com/s/article/Configure-Cloudhub-Application-to-Send-a-HTTPS-Request-Directly-to-Another-Cloudhub-Application
https://help.mulesoft.com/s/question/0D52T00004mXXULSA4/multiple-http-listerners-on-cloudhub-one-with-port-9090
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?
- A. An SLA for the upstream API CANNOT be provided
- B. The invocation of the downstream API will run to completion without timing out
- C. A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes
- D. A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes
Answer: D
NEW QUESTION # 60
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?
- A. Ensure the APIs are well documented through their Anypoint Exchange entries and API Consoles and share these pages with all API consumers
- B. Create API Notebooks and include them in the relevant Anypoint Exchange entries
- C. Enable mocking services for each of the relevant APIs and expose them via their Anypoint Exchange entry
- D. Make relevant APIs discoverable via an Anypoint Exchange entry
Answer: B
Explanation:
Correct answer: Create API Notebooks and Include them in the relevant Anypoint exchange entries
*****************************************
>> API Notebooks are the one on Anypoint Platform that enable us to provide code-centric API documentation Reference:
NEW QUESTION # 61
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. The credentials provided by the IdP for identity management
- B. The credentials provided by the IdP for client management
- C. An OAuth 2.0 token generated using the credentials provided by the IdP for identity management
- D. An OAuth 2.0 token generated using the credentials provided by the IdP for client management
Answer: A
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 # 62
What is true about automating interactions with Anypoint Platform using tools such as Anypoint Platform REST APIs, Anypoint CLI, or the Mule Maven plugin?
- A. By default, the Anypoint CLI and Mule Maven plugin are NOT included in the Mule runtime, so are NOT available to be used by deployed Mule applications.
- B. API policies can be applied to the Anypoint Platform APIs so that ONLY certain LOBs have access to specific functions.
- C. Anypoint Platform APIs can ONLY automate interactions with CloudHub, while the Mule Maven plugin is required for deployment to customer-hosted Mule runtimes
- D. Access to Anypoint Platform APIs and Anypoint CLI can be controlled separately through the roles and permissions in Anypoint Platform, so that specific users can get access to Anypoint CLI while others get access to the platform APIs.
Answer: A
NEW QUESTION # 63
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. 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
- B. 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
- C. 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
- D. Implement an anti-corruption layer in the Order API that transforms the Product API data model into internal data types of the Order API
Answer: D
NEW QUESTION # 64
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. Auth 2 token enforcement
- B. IPwhitelist
- C. Client ID enforcement
- D. SLA-based rate limiting
Answer: D
Explanation:
Explanation
https://dzone.com/articles/how-to-secure-apis
NEW QUESTION # 65
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?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: A
NEW QUESTION # 66
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. An overall tower usage of resources because each fine-grained API consumes less resources
- C. A decrease in the number of connections within the application network supporting the business process
- D. A higher number of discoverable API-related assets in the application network
Answer: D
Explanation:
Correct answer: A higher number of discoverable API-related assets in the application network.
*****************************************
>> We do NOT get faster response times in fine-grained approach when compared to coarse-grained approach.
>> In fact, we get faster response times from a network having coarse-grained APIs compared to a network having fine-grained APIs model. The reasons are below.
Fine-grained approach:
1. will have more APIs compared to coarse-grained
2. So, more orchestration needs to be done to achieve a functionality in business process.
3. Which means, lots of API calls to be made. So, more connections will needs to be established. So, obviously more hops, more network i/o, more number of integration points compared to coarse-grained approach where fewer APIs with bulk functionality embedded in them.
4. That is why, because of all these extra hops and added latencies, fine-grained approach will have bit more response times compared to coarse-grained.
5. Not only added latencies and connections, there will be more resources used up in fine-grained approach due to more number of APIs.
That's why, fine-grained APIs are good in a way to expose more number of resuable assets in your network and make them discoverable. However, needs more maintenance, taking care of integration points, connections, resources with a little compromise w.r.t network hops and response times.
NEW QUESTION # 67
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.
- A. An SLA for the upstream API CANNOT be provided
- B. Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?
- C. The invocation of the downstream API will run to completion without timing out
- D. A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes
- E. A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes
Answer: E
NEW QUESTION # 68
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
- A. Option A
- B. Option B
- C. Option D
- D. Option C
Answer: A
Explanation:
Correct answer: Ask the Marketing Department to interact with a mocking implementation of the API using the automatically generated API Console.
*****************************************
As per MuleSoft's IT Operating Model:
>> API consumers need NOT wait until the full API implementation is ready.
>> NO technical test-suites needs to be shared with end users to interact with APIs.
>> Anypoint Platform offers a mocking capability on all the published API specifications to Anypoint Exchange which also will be rich in documentation covering all details of API functionalities and working nature.
>> No needs of arranging days of workshops with end users for feedback.
API consumers can use Anypoint Exchange features on the platform and interact with the API using its mocking feature. The feedback can be shared quickly on the same to incorporate any changes.
NEW QUESTION # 69
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
- A. Option B
- B. Option A
- C. Option D
- D. Option C
Answer: D
NEW QUESTION # 70
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 the Mule runtime irrespective of the deployment model
- C. From the Mule runtime or the API implementation, depending on the deployment model
- D. From various components of Anypoint Platform, such as the Shared Load Balancer, VPC, and Mule runtimes
Answer: B
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 # 71
What is typically NOT a function of the APIs created within the framework called API-led connectivity?
- A. 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.
- B. They provide an additional layer of resilience on top of the underlying backend system, thereby insulating clients from extended failure of these systems.
- C. They reduce the dependency on the underlying backend systems by helping unlock data from backend systems In a reusable and consumable way.
- D. They can compose data from various sources and combine them with orchestration logic to create higher level value.
Answer: B
Explanation:
Explanation
https://dzone.com/articles/api-led-connectivity-with-mule
NEW QUESTION # 72
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.
- A. TRUE
- B. FALSE
Answer: A
Explanation:
Correct answer: TRUE
*****************************************
>> As per MuleSoft proposed IT Operating Model, designing APIs and making sure that they are discoverable and self-servable is VERY VERY IMPORTANT and decides the success of an API and its application network.
NEW QUESTION # 73
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 requests over HTTP/1.x
B) A Mule application that accepts JSON requests over TCP but is NOT required to provide a response
C) A Mute application that accepts JSON requests over WebSocket
D) A Mule application that accepts gRPC requests over HTTP/2
- A. Option A
- B. Option B
- C. Option D
- D. Option C
Answer: A
NEW QUESTION # 74
What is a key performance indicator (KPI) that measures the success of a typical C4E that is immediately apparent in responses from the Anypoint Platform APIs?
- A. The fraction of API implementations deployed manually relative to those deployed using a CI/CD tool
- B. The number of API implementations that have a publicly accessible HTTP endpoint and are being managed by Anypoint Platform
- C. The number of API specifications in RAML or OAS format published to Anypoint Exchange
- D. The number of production outage incidents reported in the last 24 hours
Answer: B
NEW QUESTION # 75
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?
- A. Use a spike control policy that limits the number of requests for each client application type
- B. Use a rate limiting policy and a client ID enforcement policy, each configured by the client application type
- C. Use a cross-origin resource sharing (CORS) policy to limit resource sharing between client applications, configured by the client application type
- D. Use an SLA-based rate limiting policy and assign a client application to a matching SLA tier based on its type
Answer: D
NEW QUESTION # 76
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 decrease in the number of connections within the application network supporting the business process.
- B. An overall lower 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 higher number of discoverable API-related assets in the application network.
Answer: C
NEW QUESTION # 77
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. Client ID enforcement
- B. IP whitelist
- C. OAuth 2 token enforcement
- D. SLA-based rate limiting
Answer: B
Explanation:
Explanation/Reference: https://dzone.com/articles/how-to-secure-apis
NEW QUESTION # 78
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. File-based storage
- D. java.util.WeakHashMap
Answer: A
Explanation:
Correct answer: Persistent Object Store
*****************************************
>> Redis distributed cache is performant but NOT out-of-the-box solution in Anypoint Platform
>> File-storage is neither performant nor out-of-the-box solution in Anypoint Platform
>> java.util.WeakHashMap needs a completely custom implementation of cache from scratch using Java code and is limited to the JVM where it is running. Which means the state in the cache is not worker aware when running on multiple workers. This type of cache is local to the worker. So, this is neither out-of-the-box nor worker-aware among multiple workers on cloudhub. https://www.baeldung.com/java-weakhashmap
>> Persistent Object Store is an out-of-the-box solution provided by Anypoint Platform which is performant as well as worker aware among multiple workers running on CloudHub. https://docs.mulesoft.com/object-store/ So, Persistent Object Store is the right answer.
NEW QUESTION # 79
......
2023 Valid MCPA-Level-1 test answers & MuleSoft Exam PDF: https://www.fast2test.com/MCPA-Level-1-premium-file.html