MCPA-Level-1-Maintenance MuleSoft Certified Platform Architect - Level 1 MAINTENANCE exact Exam Questions

MuleSoft Certified Platform Architect - Level 1 MAINTENANCE

Last Update 21 hours ago Total Questions : 80

The MuleSoft Certified Platform Architect - Level 1 MAINTENANCE content is now fully updated, with all current exam questions added 21 hours ago. Deciding to include MCPA-Level-1-Maintenance practice exam questions in your study plan goes far beyond basic test preparation.

You'll find that our MCPA-Level-1-Maintenance exam questions frequently feature detailed scenarios and practical problem-solving exercises that directly mirror industry challenges. Engaging with these MCPA-Level-1-Maintenance sample sets allows you to effectively manage your time and pace yourself, giving you the ability to finish any MuleSoft Certified Platform Architect - Level 1 MAINTENANCE practice test comfortably within the allotted time.

Question # 21

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

Answer:

Explanation:

Explanation

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.

Question # 22

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?

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

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

Invoke the system API deployed to the primary environment, and if it fails, invoke the system API deployed to the DR environment

Invoke ONLY the system API deployed to the primary environment, and add timeout and retry logic to avoid intermittent failures

Question # 23

An organization has several APIs that accept JSON data over HTTP POST. The APIs are all publicly available and are associated with several mobile applications and web applications.

The organization does NOT want to use any authentication or compliance policies for these APIs, but at the same time, is worried that some bad actor could send payloads that could somehow compromise the applications or servers running the API implementations.

What out-of-the-box Anypoint Platform policy can address exposure to this threat?

Shut out bad actors by using HTTPS mutual authentication for all API invocations

Apply an IP blacklist policy to all APIs; the blacklist will Include all bad actors

Apply a Header injection and removal policy that detects the malicious data before it is used

Apply a JSON threat protection policy to all APIs to detect potential threat vectors

Question # 24

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