Download MCPA-Level-1 Exam Dumps Questions to get 100% Success in MuleSoft [Q49-Q70]

Download MCPA-Level-1 Exam Dumps Questions to get 100% Success in MuleSoft

100% Accurate Answers! MCPA-Level-1 Actual Real Exam Questions

NEW QUESTION 49
An API implementation returns three X-RateLimit-* HTTP response headers to a requesting API client. What type of information do these response headers indicate to the API client?

A. A correlation ID that should be sent in the next request
B. The HTTP response size
C. The error codes that result from throttling
D. The remaining capacity allowed by the API implementation

Answer: D

Explanation:
Correct answer: The remaining capacity allowed by the API implementation.
*****************************************
>> Reference: https://docs.mulesoft.com/api-manager/2.x/rate-limiting-and-throttling-sla-based-policies#response-headers

NEW QUESTION 50
A system API has a guaranteed SLA of 100 ms per request. The system API is deployed to a primary environment as well as to a disaster recovery (DR) environment, with different DNS names in each environment. An upstream process API invokes the system API and the main goal of this process API is to respond to client requests in the least possible time. In what order should the system APIs be invoked, and what changes should be made in order to speed up the response time for requests from the process API?

A. Invoke ONLY the system API deployed to the primary environment, and add timeout and retry logic to avoid intermittent failures
B. In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment, and ONLY use the first response
C. In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment using a scatter-gather configured with a timeout, and then merge the responses
D. Invoke the system API deployed to the primary environment, and if it fails, invoke the system API deployed to the DR environment

Answer: B

Explanation:
Correct answer: In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment, and ONLY use the first response.
*****************************************
>> The API requirement in the given scenario is to respond in least possible time.
>> The option that is suggesting to first try the API in primary environment and then fallback to API in DR environment would result in successful response but NOT in least possible time. So, this is NOT a right choice of implementation for given requirement.
>> Another option that is suggesting to ONLY invoke API in primary environment and to add timeout and retries may also result in successful response upon retries but NOT in least possible time. So, this is also NOT a right choice of implementation for given requirement.
>> One more option that is suggesting to invoke API in primary environment and API in DR environment in parallel using Scatter-Gather would result in wrong API response as it would return merged results and moreover, Scatter-Gather does things in parallel which is true but still completes its scope only on finishing all routes inside it. So again, NOT a right choice of implementation for given requirement The Correct choice is to invoke the API in primary environment and the API in DR environment parallelly, and using ONLY the first response received from one of them.

NEW QUESTION 51
Refer to the exhibit.

A developer is building a client application to invoke an API deployed to the STAGING environment that is governed by a client ID enforcement policy.
What is required to successfully invoke the API?

A. The client ID and secret for the Anypoint Platform account owning the API in the STAGING environment
B. The client ID and secret for the Anypoint Platform account's STAGING environment
C. The client ID and secret obtained from Anypoint Exchange for the API instance in the STAGING environment
D. A valid OAuth token obtained from Anypoint Platform and its associated client ID and secret

Answer: D

Explanation:
Explanation
https://docs.mulesoft.com/api-manager/2.x/policy-mule3-client-id-based-policies

NEW QUESTION 52
The implementation of a Process API must change.
What is a valid approach that minimizes the impact of this change on API clients?

A. Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition
B. Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged
C. Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version
D. 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

Answer: A

NEW QUESTION 53
An API client calls one method from an existing API implementation. The API implementation is later updated. What change to the API implementation would require the API client's invocation logic to also be updated?

A. When a child method is added to the method called by the API client
B. When a new required field is added to the method called by the API client
C. When a new method is added to the resource used by the API client
D. When the data type of the response is changed for the method called by the API client

Answer: B

Explanation:
Correct answer: When a new required field is added to the method called by the API client
*****************************************
>> Generally, the logic on API clients need to be updated when the API contract breaks.
>> When a new method or a child method is added to an API , the API client does not break as it can still continue to use its existing method. So these two options are out.
>> We are left for two more where "datatype of the response if changed" and "a new required field is added".
>> Changing the datatype of the response does break the API contract. However, the question is insisting on the "invocation" logic and not about the response handling logic. The API client can still invoke the API successfully and receive the response but the response will have a different datatype for some field.
>> Adding a new required field will break the API's invocation contract. When adding a new required field, the API contract breaks the RAML or API spec agreement that the API client/API consumer and API provider has between them. So this requires the API client invocation logic to also be updated.

NEW QUESTION 54
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 number of API specifications in RAML or OAS format published to Anypoint Exchange
B. The fraction of API implementations deployed manually relative to those deployed using a CI/CD tool
C. The number of API implementations that have a publicly accessible HTTP endpoint and are being managed by Anypoint Platform
D. The number of production outage incidents reported in the last 24 hours

Answer: A

Explanation:
Correct answer: The number of API specifications in RAML or OAS format published to Anypoint Exchange
*****************************************
>> The success of C4E always depends on their contribution to the number of reusable assets that they have helped to build and publish to Anypoint Exchange.
>> It is NOT due to any factors w.r.t # of outages, Manual vs CI/CD deployments or Publicly accessible HTTP endpoints
>> Anypoint Platform APIs helps us to quickly run and get the number of published RAML/OAS assets to Anypoint Exchange. This clearly depicts how successful a C4E team is based on number of returned assets in the response.

NEW QUESTION 55
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 C
B. Option D
C. Option B
D. Option A

Answer: C

NEW QUESTION 56
How can the application of a rate limiting API policy be accurately reflected in the RAML definition of an API?

A. By refining the response definitions by adding the out-of-the-box Anypoint Platform rate-limit-enforcement securityScheme with description, type, and example
B. By refining the resource definitions by adding a description of the rate limiting policy behavior
C. By refining the response definitions by adding the x-ratelimit-* response headers with description, type, and example
D. By refining the request definitions by adding a remaining Requests query parameter with description, type, and example

Answer: C

NEW QUESTION 57
What condition requires using a CloudHub Dedicated Load Balancer?

A. When API invocations across multiple CloudHub workers must be load balanced
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 cross-region load balancing is required between separate deployments of the same Mule application

Answer: C

Explanation:
Correct answer: When server-side load-balanced TLS mutual authentication is required between API implementations and API clients
*****************************************
Fact/ Memory Tip: Although there are many benefits of CloudHub Dedicated Load balancer, TWO important things that should come to ones mind for considering it are:
>> Having URL endpoints with Custom DNS names on CloudHub deployed apps
>> Configuring custom certificates for both HTTPS and Two-way (Mutual) authentication.
Coming to the options provided for this
>> We
CANNOT use DLB to perform cross-region load balancing between separate deployments of the same Mule application.
>> We can have mapping rules to have more than one DLB URL pointing to same Mule app. But vicevera (More than one Mule app having same DLB URL) is NOT POSSIBLE
>> It is true that DLB helps to setup custom DNS names for Cloudhub deployed Mule apps but NOT true for apps deployed to Customer-hosted Mule Runtimes.
>> It is true to that we can load balance API invocations across multiple CloudHub workers using DLB but it is NOT A MUST. We can achieve the same (load balancing) using SLB (Shared Load Balancer) too. We DO NOT necessarily require DLB for achieve it.
So the only right option that fits the scenario and requires us to use DLB is when TLS mutual authentication is required between API implementations and API clients.

NEW QUESTION 58
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 lower 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: A

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

NEW QUESTION 60
What are the major benefits of MuleSoft proposed IT Operating Model?

A. 1. Decrease the IT delivery gap
2. Meet various business demands without increasing the IT capacity
3. Make consumption of assets at the rate of production
B. 1. Decrease the IT delivery gap
2. Meet various business demands by increasing the IT capacity and forming various IT departments
3. Make consumption of assets at the rate of production
C. 1. Decrease the IT delivery gap
2. Meet various business demands without increasing the IT capacity
3. Focus on creation of reusable assets first. Upon finishing creation of all the possible assets then inform the LOBs in the organization to start using them

Answer: A

Explanation:
Correct answer:
1. Decrease the IT delivery gap
2. Meet various business demands without increasing the IT capacity
3. Make consumption of assets at the rate of production.
*****************************************
Reference:

NEW QUESTION 61
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. Configure a "worker not responding" alert in Anypoint Runtime Manager
C. Create an alert for when the API receives no requests within a specified time period
D. Handle API invocation exceptions within the calling API client and raise an alert from that API client when the API Is unavailable

Answer: A

NEW QUESTION 62
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 D
C. Option C
D. Option A

Answer: C

NEW QUESTION 63
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 irrespective of the deployment model
B. From the Mule runtime or the API implementation, depending on the deployment model
C. From the Mule runtime or the API Manager, depending on the type of data
D. From various components of Anypoint Platform, such as the Shared Load Balancer, VPC, and Mule runtimes

Answer: D

NEW QUESTION 64
What correctly characterizes unit tests of Mule applications?

A. They test the validity of input and output of source and target systems
B. They must be run in a unit testing environment with dedicated Mule runtimes for the environment
C. They must be triggered by an external client tool or event source
D. They are typically written using MUnit to run in an embedded Mule runtime that does not require external connectivity

Answer: D

Explanation:
Correct answer: They are typically written using MUnit to run in an embedded Mule runtime that does not require external connectivity.
*****************************************
Below TWO are characteristics of Integration Tests but NOT unit tests:
>> They test the validity of input and output of source and target systems.
>> They must be triggered by an external client tool or event source.
It is NOT TRUE that Unit Tests must be run in a unit testing environment with dedicated Mule runtimes for the environment.
MuleSoft offers MUnit for writing Unit Tests and they run in an embedded Mule Runtime without needing any separate/ dedicated Runtimes to execute them. They also do NOT need any external connectivity as MUnit supports mocking via stubs.
https://dzone.com/articles/munit-framework

NEW QUESTION 65
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 gRPC requests over HTTP/2
B. A Mule application that accepts requests over HTTP/1x.
C. A Mule application that accepts JSON requests over TCP but is NOT required to provide a response.
D. A Mule application that accepts JSON requests over WebSocket.

Answer: A

Explanation:
Explanation/Reference:

NEW QUESTION 66
What correctly characterizes unit tests of Mule applications?

A. They test the validity of input and output of source and target systems
B. They must be run in a unit testing environment with dedicated Mule runtimes for the environment
C. They are typically written using MUnit to run in an embedded Mule runtime that does not require external connectivity
D. They must be triggered by an external client tool or event source

Answer: B

Explanation:
Explanation
https://dzone.com/articles/munit-framework

NEW QUESTION 67
What API policy would LEAST likely be applied to a Process API?

A. Custom circuit breaker
B. Rate limiting
C. JSON threat protection
D. Client ID enforcement

Answer: A

NEW QUESTION 68
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. A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes
B. Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?
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. An SLA for the upstream API CANNOT be provided
E. The invocation of the downstream API will run to completion without timing out

Answer: E

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