Design & Implement a Release Strategy — MOC

MS Learn path: Design and implement a release strategy · The CD half — delivering every change safely to production.

Planned concepts

Continuous delivery · release-strategy · deployment-ring · blue-green-deployment · canary-deployment · feature-flags · deployment-environment · release-definition · deployment-gate · rollback-strategy · Sneak/verified environments · workload-identity-federation · secretless-pipeline-authentication · deployment-automation · release-notes-templates

Canvas

Release Strategy canvas

Modules in this path

  1. Introduction to Continuous Delivery
  2. Design a release strategy
  3. Deployment patterns
  4. Deployment gates and rollback
  5. Release management models
  6. Deploy automation
  7. Pipeline reliability
  8. Deploying to cloud infrastructure
  9. Service connections for deployments

Skills

Release pipeline, deployment patterns, rollback, deploy automation, pipeline resilience, service-connection security, release notes.

Evidence route

Complete the database-safe release and feature rollout first. Then complete ordered, resilient release paths to connect immutable artifacts, dependency order, slots or revisions, bounded retry, measured rollback, and the protected hotfix path.

Route check: Choose the first recovery action when an additive schema migration succeeds but the training smoke test fails: hold traffic, disable a flag, restore an artifact, or reverse data. Justify it from the recorded evidence.

Practice questions

Conceptual checkpoint

Explain the sequence in this path using one workload scenario: identify the boundary being changed, the identity or tool acting on it, the expected evidence, and the failure that would change your decision.

Sources and re-audit

Re-audit when the AZ-400 course path, study-guide effective date, or the services and permissions taught here change.