Design and Implement Deployments AZ-400 Practice Questions (Page 4)

Questions 16–19

1. 16expert · hard

   A company deploys a stateful application to AKS. They need to deploy a new version with zero downtime, but the application cannot have more than one instance running at a time due to a legacy database lock. They also need to automatically roll back if the new version fails readiness checks. What should they do?

   • AUse a canary deployment with a 10% traffic split and a single replica
   • BUse a rolling update with maxSurge=1 and maxUnavailable=0
   • CUse a blue-green deployment with a single replica in the new version, and configure a readiness probe that fails, triggering a rollback to the old version
   • DUse a recreate strategy with a single replica and a readiness probe
   Reveal Solution Discussion Select an answer first
2. 17application · medium

   A company wants to test a new recommendation algorithm on a small percentage of users and compare the conversion rate against the old algorithm. They need to be able to turn off the new algorithm immediately if conversion drops. What should they implement?

   • ARing deployment with a hard-coded feature toggle
   • BRolling deployment with a fixed 50% traffic split
   • CBlue-green deployment with a full traffic switch
   • DA/B testing with a feature flag in Azure App Configuration
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   A company is deploying a multi-tier application that consists of a database schema update, a backend API container, and a frontend web app. The database update must complete successfully before the API container starts, and the API must be healthy before the frontend is updated. The team uses Azure Pipelines. What should they configure to ensure the correct order?

   • ACreate separate pipelines and trigger them manually in the correct sequence
   • BUse a single stage with multiple jobs that run in parallel
   • CUse a single job with multiple steps that run in parallel
   • DDefine stages in the pipeline and use the 'dependsOn' keyword to enforce the order
   Reveal Solution Discussion Select an answer first
5. 19foundation · medium

   A DevOps team maintains a production web application deployed via Azure Pipelines. A critical security vulnerability is discovered in the current release, and the team must ship a fix immediately. The team's standard deployment pipeline runs a full suite of integration tests, takes 45 minutes, and deploys to a staging environment before production. Which hotfix path approach best balances the need for speed with the need to avoid introducing new regressions?

   • AApply the fix directly to the main branch, run the full integration test suite, and deploy to production through the standard pipeline without staging to save time.
   • BCreate a dedicated hotfix branch from the production release tag, apply the minimal code change, run only targeted unit tests for the affected component, and deploy directly to production using a separate fast pipeline that skips staging.
   • CRevert the production deployment to the previous known-good release, then apply the fix to the current development branch and deploy it through the standard pipeline with full testing.
   • DCreate a hotfix branch from the latest main branch, run all tests including integration tests, and deploy to production after manual approval from the release manager.
   Reveal Solution Discussion Select an answer first