MCPA-LEVEL-1 practice question 6 of 15

An organization is deploying their new implementation of the OrderStatus System API to multiple workers in CloudHub. This API fronts the organization's on-premises Order Management System, which is accessed by the API implementation over an IPsec tunnel. What type of error typically does NOT result in a service outage of the OrderStatus System API?

Full set: 95 questions
Answer options
A: A CloudHub worker fails with an out-of-memory exception Correct answer
B: API Manager has an extended outage during the initial deployment of the API implementation
C: The AWS region goes offline with a major network failure to the relevant AWS data centers
D: The Order Management System is Inaccessible due to a network outage in the organization's on- premises data center
Correct Answer:
A. A CloudHub worker fails with an out-of-memory exception
Explanation

The question specifies that the API is deployed to multiple workers in CloudHub. This configuration is designed for high availability (HA). If a single worker fails due to an issue like an out-of-memory exception, the CloudHub load balancer automatically detects the failure and stops routing traffic to it. Requests are seamlessly redirected to the remaining healthy workers. While the application's overall processing capacity is temporarily reduced, the API service remains operational and available to consumers, thus avoiding a complete service outage.

Why Incorrect

B. API Manager has an extended outage during the initial deployment of the API implementation: The API implementation must register with API Manager upon initial startup (autodiscovery). An outage would prevent this, causing the deployment to fail and the service to be unavailable.
C. The AWS region goes offline with a major network failure to the relevant AWS data centers: CloudHub is hosted on AWS. A regional failure would take all deployed workers offline simultaneously, resulting in a complete and unavoidable service outage.
D. The Order Management System is Inaccessible due to a network outage in the organization's on-premises data center: The API's core function is to front the on-premises system. If this backend system is unavailable, the API cannot process requests successfully, leading to a functional service outage.

References

1. MuleSoft Documentation, "CloudHub Architecture", Section: High Availability: "You can make your application highly available by deploying it to two or more workers. If one worker goes down, the other workers continue processing the requests, resulting in zero downtime." This directly supports the correctness of answer A.

2. MuleSoft Documentation, "CloudHub Networking Guide", Section: Load Balancing: "The CloudHub load balancer distributes traffic among the workers that run your application... If a worker becomes unresponsive, the load balancer stops routing requests to it." This explains the mechanism that prevents a single worker failure from causing an outage.

3. MuleSoft Documentation, "API Autodiscovery": "When a Mule application that is configured for autodiscovery starts, it registers itself with API Manager..." This highlights the critical dependency on API Manager during the startup/deployment phase, explaining why option B would cause an outage.

4. MuleSoft Documentation, "Error Handling in Mule 4": This documentation details strategies for handling backend failures. The existence of extensive error handling for backend connectivity issues (like in option D) underscores that such failures are critical events that can cause a functional service outage if not managed.

Scroll to Top