Practice Exam

Explanations for each answer:

• Enable single revision mode is incorrect. Single revision mode automatically deactivates the previous revision once the new one is ready, which creates a significant risk: if the new deployment contains bugs in new features or patches, the entire application would go down immediately with no ability to quickly rollback. Without the ability to maintain multiple active revisions and split traffic between them, you cannot perform gradual rollouts, A/B testing, or instant rollbacks when issues are discovered in production.
• Use a single environment for all containers is incorrect. Using a single environment doesn't address the requirement for zero-downtime deployments. Container Apps environments provide the infrastructure for containers, but the revision mode setting determines how updates are deployed. A single environment can host multiple revisions when properly configured.
• Use multiple environments for each container is incorrect. Creating separate environments for each container adds unnecessary complexity and management overhead. Azure Container Apps is designed to handle multiple revisions within a single environment, making multiple environments redundant for zero-downtime updates.
• Use a private container registry and single image for all containers is incorrect. While using a private registry is a security best practice, it doesn't affect how updates are deployed. Using a single image for all containers would actually prevent zero-downtime deployments because you couldn't gradually transition from the old version to the new version.
• Enable multiple revision mode is correct. Multiple revision mode allows you to run several revisions simultaneously and control traffic distribution between them. When you deploy an update, the new revision starts alongside the existing one, and traffic can be switched after the new revision passes health checks. This enables zero-downtime deployments, gradual traffic shifting, and easy rollbacks.