A company deploys a microservices application to AKS. They want to deploy a new version of one service with a canary strategy, but they also need to ensure that if the canary fails, the system automatically reverts to the previous version. They use Flagger or a similar progressive delivery tool. What should they configure?

Configure a canary analysis with a metric that checks error rate and a threshold that triggers a rollback

Use a blue-green deployment with a manual switch

Use a rolling update with a readiness probe

Use a manual canary deployment and rely on Azure Monitor alerts to roll back

A company is deploying an application that requires a database schema migration. They want the migration to run automatically as part of the release pipeline, but they also want to ensure that if the migration fails, the application deployment does not proceed. What should they do?

Run the database migration in parallel with the application deployment

Run the database migration after the application deployment

Use a manual step to run the migration outside the pipeline

Add a database migration task as a separate stage before the application deployment stage, and fail the pipeline if the task fails

A company deploys a critical API to Azure Kubernetes Service (AKS). They want to ensure that a failed deployment does not affect all users at once and that the system can automatically recover if a new pod is unhealthy. Which deployment strategy and Kubernetes feature should they use?

Blue-green deployment with a manual switch and no probes

Recreate deployment strategy with a single replica

Canary deployment with a fixed 50% traffic split and no health checks

Rolling update with readiness probes and pod disruption budgets

A release pipeline deploys a database schema change and then a new version of an application. The database change is backward-compatible with the old application version, but the new application version requires the new schema. The team wants to minimize downtime and be able to roll back the application independently of the database. What should they do?

Use a blue-green deployment for the database and application together.

Deploy both the database and application together and roll back both if there is a failure.

Deploy the new application first, then the database change, and if the database fails, roll back the application.

Deploy the database change first, then deploy the new application, and if the application fails, roll back the application to the previous version.

Microsoft Certified:DevOps Engineer Expert

Domain 3Objective 4

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

Part of the Design and implement build and release pipelines domain, which makes up ~41% of our current practice bank. Microsoft does not publish an official question count, but from its 140-minute exam (~55–95 total, ~23–39 in this domain), expect 4–7 from this objective — we provide 19 practice questions to prepare you well beyond it. (estimate)

19questions here

4free pages

8concepts

Questions 1–5

1expert · hard
A company deploys a microservices application to AKS. They want to deploy a new version of one service with a canary strategy, but they also need to ensure that if the canary fails, the system automatically reverts to the previous version. They use Flagger or a similar progressive delivery tool. What should they configure?
Select an answer first
2foundation · easy
A DevOps team wants to deploy a new version of a web application with zero downtime and the ability to instantly roll back if a critical issue is detected. Which deployment strategy should they use?
Select an answer first
3application · medium
A company is deploying an application that requires a database schema migration. They want the migration to run automatically as part of the release pipeline, but they also want to ensure that if the migration fails, the application deployment does not proceed. What should they do?
Select an answer first
4application · medium
A company deploys a critical API to Azure Kubernetes Service (AKS). They want to ensure that a failed deployment does not affect all users at once and that the system can automatically recover if a new pod is unhealthy. Which deployment strategy and Kubernetes feature should they use?
Select an answer first
5expert · hard
A release pipeline deploys a database schema change and then a new version of an application. The database change is backward-compatible with the old application version, but the new application version requires the new schema. The team wants to minimize downtime and be able to roll back the application independently of the database. What should they do?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to AZ-400

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Microsoft. “AZ-400” is a trademark of its owner, used for identification only.

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

Questions 1–5

A DevOps team wants to deploy a new version of a web application with zero downtime and the ability to instantly roll back if a critical issue is detected. Which deployment strategy should they use?

A company is deploying an application that requires a database schema migration. They want the migration to run automatically as part of the release pipeline, but they also want to ensure that if the migration fails, the application deployment does not proceed. What should they do?

A company deploys a critical API to Azure Kubernetes Service (AKS). They want to ensure that a failed deployment does not affect all users at once and that the system can automatically recover if a new pod is unhealthy. Which deployment strategy and Kubernetes feature should they use?

Keep studying — Design and implement build and release pipelines