MuleSoft Certified Integration Architect – Level 1 — Question 51

A Mule application is deployed to a single CloudHub worker and the public URL appears in Runtime Manager as the App url.
Requests are sent by external web clients over the public Internet to the Mule application's App url. Each of these requests is routed to the HTTPS Listener event source of the running Mule application.
Later, the DevOps team edits some properties of this running Mule application in Runtime Manager.
Immediately after the new property values are applied in Runtime Manager, how is the current Mule application deployment affected, and how will future web client requests to the Mule application be handled?

Answer options

• A. CloudHub will redeploy the Mule application to the OLD CloudHub worker New web client requests are ROUTED to the OLD CloudHub worker BOTH before and after the Mule application is redeployed
• B. CloudHub will redeploy the Mule application to the OLD CloudHub worker New web client requests will RETURN AN ERROR until the Mule application is redeployed to the OLD CloudHub worker
• C. CloudHub will redeploy the Mule application to a NEW CloudHub worker New web client requests will RETURN AN ERROR until the NEW CloudHub worker is available
• D. CloudHub will redeploy the Mule application to a NEW CloudHub worker New web client requests are ROUTED to the OLD CloudHub worker until the NEW CloudHub worker is available

Correct answer: D

Explanation

The correct answer is D because when properties are updated, CloudHub redeploys the application to a new worker while ensuring that existing requests are still routed to the old worker until the new one is ready. Options A and B incorrectly state that the redeployment occurs on the old worker, while option C misrepresents the request routing during the redeployment process.