Microsoft DevOps Engineer Expert AZ-400 — Study Guide
Practice as you learn. Every concept maps to real exam questions with verified answers in the Microsoft exam hub, or drill the full exam with timed practice on ExamRoll.io.
This guide covers each AZ-400 domain in depth. Pick a domain to go deep, or work through them in order.
The domains
- Source Control and Repository Management — Choose a branching strategy deliberately: - Trunk-based development favors a single long-lived main branch with very short-lived feature branches and
- CI/CD Pipelines with Azure Pipelines — Templates enable composition and reuse at different granularities: - Step templates: encapsulate a sequence of tasks (e.g., tool setup, restore,
- Infrastructure as Code and Configuration Management — To break large deployments into maintainable units you can use nested or linked templates. A nested template inlines JSON in a
- Containerization and Kubernetes — Azure Container Registry (ACR) is the backbone for image storage and distribution. Leverage ACR Tasks to offload builds to Azure: quick tasks for
- Release Management and Deployment Strategies — Canary deploys to a small slice of users first, then progressively increases traffic as health holds. On Azure, implement canary with: - Azure Front
- Security, Compliance and DevSecOps — DAST validates running builds in a staging environment. Automate OWASP ZAP or equivalent as a pipeline job post-deploy to non-production, using
- Testing Strategy and Quality Engineering — Shift-left testing practices reduce defects earlier: - Test-Driven Development (TDD) enforces red–green–refactor cycles, informs design, and
- Monitoring, Observability and Feedback — Telemetry types include requests, dependencies (HTTP, SQL, Azure SDKs), traces, exceptions, page views, page load performance, availability test
- Package Management and Artifact Management — Views implement a gated promotion model within a single feed: - local: all newly published packages appear here - prerelease: used to expose
- Agile Planning and Work Management — Azure DevOps process templates define states, fields, and WIT naming: - Agile: Requirement-level item is User Story; fast-moving teams often choose
Ready to practice?
- Browse every question with verified answers → — free, with explanations.
- Start timed practice tests on ExamRoll.io → — the full question bank, in 20+ languages.
Pass the whole exam — not just this question
You found this answer. Get every verified question and explanation in one place, and save hours of prep. Free to start.
Pass your exam →