AZ-400 course and practice exam: Microsoft Azure DevOps Engineer Expert
This AZ-400 course has 33 video lessons and 49 graded labs, and its AZ-400 practice exam follows the official exam objectives: a 20-question sampler free with an account, the full question bank and timed mock exams with Pro.
Processes, source control, pipelines, security and instrumentation
Prepares you for AZ-400: designing DevOps processes, source control strategy, build and release pipelines, security and compliance, and instrumentation on Azure.
Advanced · 3 hours · 33 lessons · 72 labs
AZ-400 exam guide
The AZ-400 exam (Microsoft Certified: DevOps Engineer Expert, by Microsoft): 100 minutes; pass mark: 700 (on a scale of 1–1,000); cost: price based on the country or region in which the exam is proctored.
- Format: Proctored; multiple choice and interactive components
- Duration: 100 minutes
- Pass mark: 700 (on a scale of 1–1,000)
- Cost: Price based on the country or region in which the exam is proctored
- Valid for: Expires annually; free renewal by passing online assessment on Microsoft Learn
- Delivery: Online proctored or at Pearson VUE testing center
- Prerequisites: The DevOps Engineer Expert certification also requires Microsoft Certified: Azure Administrator Associate (AZ-104) or Azure Developer Associate (AZ-204). AZ-204 was reported retired on 31 July 2026; check the certification page for how the AZ-204 route applies.
Exam domains and weights
- Design and implement processes and communications: 10–15%
- Design and implement a source control strategy: 10–15%
- Design and implement build and release pipelines: 50–55%
- Develop a security and compliance plan: 10–15%
- Implement an instrumentation strategy: 5–10%
A 20-question practice sampler is free with an account; Pro adds the full question bank and timed mock exams.
10 AZ-400 sample questions with answers: free to read, no account needed.
Common questions
How long is the AZ-400 exam?
The AZ-400 exam lasts 100 minutes.
What is the AZ-400 passing score?
The pass mark is 700 (on a scale of 1–1,000).
How much does the AZ-400 exam cost?
Price based on the country or region in which the exam is proctored.
Is there a free AZ-400 practice test?
Yes. A 20-question practice sampler is free with an account; Pro adds the full question bank and timed mock exams.
Source: Study guide for Exam AZ-400: Designing and Implementing Microsoft DevOps Solutions (Microsoft), checked 2026-10-01.
Who it is for
Advanced level.
For developers and platform engineers who build release pipelines on Azure DevOps and GitHub, and want the DevOps Engineer Expert certificate.
What you don't need yet:
- No Azure subscription: every lab runs in your browser
- You don't need to know every Azure service already
- You don't need production Terraform experience
What helps:
- Azure administration or development experience, at AZ-104 level
- Comfort with Git, the command line and YAML pipeline files
No formal prerequisites. The courses under "Take first" cover what helps.
Take first:
- Microsoft Azure Administrator (AZ-104) Exam Prep — Intermediate
- Advanced Git Internals & Distributed Workflows — Beginner
- Continuous Integration & Continuous Delivery Pipelines — Intermediate
Learning paths:
Nobody needs to know everything before they start. Each course builds on the one before, so a learning path takes you there step by step.
What this exam proves, and what it doesn't
AZ-400 is a proctored exam of multiple-choice and interactive questions: passing shows you can design release pipelines on Azure. It doesn't replace running them in production; our graded labs run in your browser, not a live subscription.
Exam objectives this course teaches
Microsoft Certified: DevOps Engineer Expert
- Design and implement processes and communications (10–15% of the exam): Design and implement traceability and flow of work; Design and implement appropriate metrics and queries for DevOps; Configure collaboration and communication
- Design and implement a source control strategy (10–15% of the exam): Design and implement branching strategies for the source code; Configure and manage repositories
- Design and implement build and release pipelines (50–55% of the exam): Design and implement a package management strategy; Design and implement a testing strategy for pipelines; Design and implement pipelines; Design and implement deployments; Design and implement infrastructure as code (IaC); Maintain pipelines
- Develop a security and compliance plan (10–15% of the exam): Design and implement authentication and authorization methods; Design and implement a strategy for managing sensitive information in automation; Automate security and compliance scanning
- Implement an instrumentation strategy (5–10% of the exam): Configure monitoring for a DevOps environment; Analyze metrics from instrumentation
Labs
72 labs, 49 of them graded: you write the code, it runs, and graded labs check the result. The outline lists each lesson's labs.
What is free
Start free: First module free with an account. Pro: Every course, lab, handbook, practice exam and certificate.
- Pro monthly — $29 a month. Every course, lab, handbook, practice exam and certificate
- Pro yearly — $249 a year. Every course, lab, handbook, practice exam and certificate
Course outline
Start Here
- Release Day At Kestrel Bank: You can follow one change at Kestrel Bank from a work item to production and its first alert, and name the AZ-400 domain that governs each step.
- An Expert Exam With The Book Open (1 lab): You can plan a 100-minute AZ-400 sitting, decide which questions are worth a Microsoft Learn lookup, work a case study requirement by requirement, and know the scoring and retake rules.
Processes And Communications
- Traceability And The Flow Of Work (2 labs): You can structure the flow of work in Azure Boards or GitHub Projects, link commits and pull requests to work items with the documented AB# rules, and follow a bug back to the code, build and review that fixed it.
- Metrics, Queries And Dashboards (3 labs): You can compute lead time and cycle time as Azure Boards defines them, use a cumulative flow diagram and Little's law to explain a queue, write a work item query, and choose the right metric for planning, development, testing, security, delivery and operations.
- Wikis, Release Notes And Integrations (3 labs): You can document a project in an Azure DevOps or GitHub wiki with Markdown and Mermaid diagrams, generate release notes from git history, and connect Azure DevOps and GitHub to each other and to Microsoft Teams with apps, service hooks and webhooks.
- DORA Metrics: Measuring Your Pipeline (3 labs): You can name the five DORA metrics as the research publishes them, say which data each one is computed from, and compute change lead time and deployment frequency yourself from a commit list and a deployment log your pipeline appends to.
Source Control Strategy
- Choosing A Branching Strategy (1 lab): You can choose between trunk-based development, feature branches and release branches for a described team, explain how feature flags shorten branches, and port a fix from main to a release branch with cherry-pick.
- Branch Policies And Protection Rules (1 lab): You can design a pull request workflow with Azure Repos branch policies and GitHub branch protection rules or rulesets, restrict merges and bypasses, and predict whether a given push or pull request will be allowed.
- Large Files, Scale, Permissions And Tags (4 labs): You can find large files in a repository's history, keep new ones out with Git LFS or git-fat, choose Scalar, sparse checkout or a shared package to scale, set repository permissions in Azure Repos and GitHub, and organise releases with annotated tags.
- Recovering And Removing Data With Git (2 labs): You can recover a deleted branch or file with the reflog and git restore, choose between revert and reset, and remove a committed secret from every branch in the right order: rotate, rewrite, force push, clean up.
Build And Release Pipelines
- Package Feeds, Views And Upstream Sources (3 labs): You can choose between Azure Artifacts and GitHub Packages, design a feed with upstream sources and views, predict which version a consumer resolves, and protect internal package names from public look-alikes.
- Versioning Packages And Pipeline Artifacts (4 labs): You can choose SemVer or CalVer for a package, decide the bump a change requires, order prerelease versions correctly, pick a dependency versioning strategy, and number pipeline runs and artifacts with run numbers and counters.
- A Testing Strategy In The Pipeline (3 labs): You can place local, unit, integration, load and UI tests in the right pipeline stage, publish test results and code coverage so they survive a failing run, set quality gates, and handle flaky tests.
- Azure Pipelines YAML: Stages, Triggers And Conditions (2 labs): You can write a multi-stage Azure Pipelines YAML file, set CI, pull request, scheduled and pipeline triggers with branch and path filters, control execution order and parallelism, use the three variable syntaxes, and predict which stages run for an event.
- Agents, Pools And Runners (1 lab): You can choose Microsoft-hosted agents, self-hosted agents, Managed DevOps Pools or GitHub runners for a workload by cost, tools, licences, connectivity and maintenance, and predict which agent a job's demands select.
- Templates, Extends And Reuse (4 labs): You can write step, job, stage and variable templates with typed parameters, expand them to see what will run, enforce an approved pipeline shape with extends and the required template check, and choose between templates, task groups and variable groups.
- Workflows, Jobs, Steps, and Actions (5 labs): You can name the four levels of a workflow file, read a needs key as an edge in a graph of jobs, tell a run step from a uses step, choose between a version tag and a pinned commit, and move a value from one step to another through the outputs file.
- GitHub Actions And Azure Pipelines Side By Side (2 labs): You can translate between Azure Pipelines and GitHub Actions concepts, choose between them for a scenario, connect GitHub repositories to Azure Pipelines with the GitHub App, and catch translation mistakes with actionlint.
- Blue-Green, Canary, Rings And Feature Flags (2 labs): You can choose blue-green, canary, ring, progressive exposure, feature flag or A/B strategies for a scenario, gate a ring rollout on health, and predict who sees a feature behind an Azure App Configuration targeting filter.
- Environments, Approvals And Checks (2 labs): You can target an environment from a deployment job, protect it with branch control, approvals, business hours, Azure Monitor alert and exclusive lock checks, predict which check holds or fails a stage, and map the same controls onto GitHub environments.
- Deploying With Less Downtime (1 lab): You can replace running code with rolling updates or App Service slot swaps, predict what a swap does to each app setting, change a database schema so two versions can share it, order dependent deployments, and plan a hotfix path and a recovery.
- Infrastructure As Code In The Pipeline (2 labs): You can define an IaC strategy with source control, validation and approval, preview Bicep and ARM deployments with what-if, apply exactly the Terraform plan that was approved, and offer self-service infrastructure with Azure Deployment Environments.
- Desired State And Configuration Management (1 lab): You can separate provisioning from configuration management, choose Azure Machine Configuration's audit, apply and monitor, or apply and autocorrect mode, predict what each reports after drift, and recommend a home for application settings and secrets references.
- Pipeline Health, Cost And Retention (2 labs): You can read pipeline pass rate, duration and test failure reports, find flaky tests and top failing tasks in run history, predict whether parallel jobs or caching cut queue time more, and design run, artifact and package retention.
- From Classic Pipelines To YAML (2 labs): You can migrate a classic build with Export to YAML, rebuild a classic release as YAML stages with deployment jobs, templates and environment checks, find the mistakes a conversion typically makes, and cut over without losing secrets, schedules or control.
Security And Compliance
- Service Connections, Identities And Tokens (2 labs): You can choose between service principals and system- or user-assigned managed identities, set up workload identity federation from Azure Pipelines and GitHub Actions, predict which OIDC tokens a federated credential accepts, scope service connections, and pick between GITHUB_TOKEN, GitHub Apps and personal access tokens.
- Permissions, Groups And Access Levels (1 lab): You can organise Azure DevOps into an organisation, projects and teams, choose Stakeholder, Basic or Basic plus Test Plans access, predict effective permissions from Allow, Deny and inheritance, and apply GitHub organisation roles, repository roles and outside collaborators.
- Secrets, Keys And Certificates In Pipelines (2 labs): You can keep secrets, keys and certificates in Azure Key Vault, bring them into Azure Pipelines through Key Vault-linked variable groups and secure files, predict what log masking hides and what it misses, and design pipelines and GitHub workflows that do not leak.
- Scanning Code, Dependencies And Containers (3 labs): You can design a scanning strategy that pairs dependencies, code, secrets, containers and licences with the right scanner, configure Dependabot, CodeQL (including in a container) and GitHub Advanced Security on GitHub and Azure DevOps, connect them to Microsoft Defender for Cloud, and route findings to an owner and a merge verdict.
Instrumentation
- Monitoring A DevOps Environment (2 labs): You can choose what Application Insights, VM insights, Container insights and the storage and network insights collect, design Azure Monitor alert rules whose window, frequency and state behave as intended, route alerts into work items, alert on GitHub Actions and Azure Pipelines events, and build GitHub project insight charts.
- Asking Telemetry Why, With KQL (3 labs): You can query Application Insights requests, dependencies and traces with basic KQL, spot and fix common query mistakes, follow one operation through distributed tracing, and read infrastructure, usage and performance indicators.
Mock And Review
- Case Study: Larkspur Freight (1 lab): You can work an AZ-400 case study the way the exam sets it: read a company's environment and numbered requirements, map each question to the one requirement it tests, eliminate options that break a requirement or add what nobody asked for, and check a whole design against every requirement.
- The Full Mock And Your Review Plan (2 labs): You can sit a mock that behaves like AZ-400, read its result by domain and by objective priced by exam weight, classify every miss, turn the result into a study plan of lessons, and decide when to book, with the retake and renewal rules in mind.