In a CloudHub deployment with a single worker/replica located in a specific Availability Zone (AZ), if an AZ experiences an outage, here's what happens:
* Worker Availability: Since the application is deployed in a single AZ, CloudHub does not automatically redeploy the application in a different zone or region during an outage. Thus, if the current AZ is unavailable, the application will be offline.
* Auto-Restart upon AZ Recovery: Once the affected AZ is back online, CloudHub will auto-restart the worker in the same AZ without manual intervention. This ensures that as soon as the AZ is functional, the application resumes automatically.
* Explanation of Correct Answer (B):
* Option B accurately describes the situation, as the API will remain unavailable until the original AZ is restored.
* CloudHub does not currently support automatic failover across regions or other availability zones within the same region for single-worker deployments on the shared cloud.
* Explanation of Incorrect Options:
* Option A (auto-redeployment in the U.S. East region) is incorrect, as CloudHub does not migrate across regions automatically.
* Option C (redeployment in another AZ within the U.S. West) is not a feature for single-worker deployments.
* Option D (manual redeployment triggered by an admin) is unnecessary as CloudHub handles restarts automatically when the AZ is back online.
ReferencesRefer to MuleSoft CloudHub's availability and disaster recovery documentation for more information on how CloudHub manages availability in shared environments.