Exam AZ-204 topic 2 question 58 discussion

Zero downtime deployment using single mode https://learn.microsoft.com/en-us/azure/container-apps/revisions#zero-downtime-deployment

https://learn.microsoft.com/en-us/answers/questions/2276430/zero-downtime-deployment-in-azure-container-apps

it should be Ënable Multiple Revision Mode

Got this in the exam today! May 15, 2025. Went most voted. 940/1000. 50 of 51 from examtopics. Cases Munson’s Pickles and Preserves Farm (7) and Fourth Coffee (3)

E. Enable multiple revision mode.

E is the correct one imho

Enable multiple revision mode.

E is the correct one.

My guess is E? The docs are very clear that both Single- and Multi-Revision are zero-downtime: https://learn.microsoft.com/en-us/azure/container-apps/revisions#zero-downtime-deployment ...so there's no clear answer just from that. My thinking is: Even if the container ready-checks pass, the deployed code itself could still be flawed and result in a broken application. Being able to validate the new version using multi-revision mode is a safer option than just sending it. Is a broken app technically 'downtime'? Debatable. Should a broken app be caught before the prod deploy? Certainly. But I don't see any other way to favour one option over the other. Of course, is that what Mr. Microsoft wants...? I have no idea.

Multiple Revision Mode: - In multiple revision mode, Azure Container Apps creates a new revision each time a deployment is updated. - Traffic can be split between the current and new revisions during the update process, ensuring zero downtime. - Once the new revision is stable, traffic can be shifted fully to the new revision, completing the update.

Single Revision Mode has zero downtime.

A Source: https://learn.microsoft.com/en-us/azure/container-apps/revisions#zero-downtime-deployment

E Single Revision Mode: In single revision mode, only one revision of the application is active at any given time. When you deploy a new revision, it replaces the current active revision. This means that during the deployment process, the old revision is taken offline while the new one is brought up. This can cause a brief period where the application might be unavailable or not fully functional, resulting in potential downtime. Multiple Revision Mode: This mode allows multiple revisions to run concurrently. When deploying a new revision, it can coexist with the old revision. Traffic can be routed gradually from the old revision to the new one, ensuring a smooth transition without downtime.

E. Enable multiple revision mode: Multiple revision mode allows for more than one version of the container app to be active at the same time. This is essential for zero-downtime deployments because you can deploy a new revision without taking down the old one, then gradually shift traffic to the new revision using traffic splitting.

single revision mode

In single revision mode, Container Apps ensures your app doesn't experience downtime when creating a new revision. The existing active revision isn't deactivated until the new revision is ready. If ingress is enabled, the existing revision continues to receive 100% of the traffic until the new revision is ready. https://learn.microsoft.com/en-us/azure/container-apps/revisions

E. Enable multiple revision mode. Explanation: Azure Container Apps supports multiple revision mode, allowing you to deploy updates without causing downtime. With multiple revision mode, you can deploy new revisions of your microservice while keeping the previous revision running. This approach enables a smooth transition without interruption to your application. So, choose option E to enable multiple revision mode when deploying updates to your microservice on Azure Container Apps.