Exam Prep
Microsoft Azure · AZ-400

Designing and Implementing Microsoft DevOps Solutions

Validates the skills to design and implement DevOps practices on Azure — covers source control strategy, build and release pipelines, security and compliance, and monitoring instrumentation.

Start Preparing

Free study references: Pages from Microsoft Azure for every objective

Should I Take the AZ-400?

You should work towards AZ-400 if you’re aiming for one of these careers:

  • DevOps engineer — designs and runs the CI/CD pipelines, branching strategy and release gates that take code from commit to production.
  • Site reliability engineer — builds the monitoring, alerting and instrumentation that keep deployed systems observable and keeps deployments resilient under load.
  • Release engineer or build and release engineer — owns package management, artifact versioning and the pipeline infrastructure that turns builds into repeatable, auditable releases.
  • Cloud infrastructure or automation engineer — implements infrastructure as code, configuration management and deployment automation across Azure environments.

AZ-400 is Microsoft's expert-level credential in the Azure track, and it only becomes a full certification once paired with an associate prerequisite — either the Azure Administrator Associate (AZ-104) or the Azure Developer Associate (AZ-204). For someone who already holds one of those, AZ-400 is the step that turns an associate credential into the Microsoft Certified: DevOps Engineer Expert title.

Is the AZ-400 Worthwhile?

Here’s what we’d tell a friend:

  • It sits at the top of Microsoft's Azure certification ladder, and the market treats it that way. A certification tracker that monitors job postings and pay by credential puts AZ-400 and the Solutions Architect Expert certification (AZ-305) above the associate-level Azure certifications in average pay, and that comparison shows up repeatedly across sites that track multiple Azure credentials side by side. Source: AZ-400 vs AZ-104: DevOps Engineer Expert vs Azure Administrator 2026
  • Pay figures for AZ-400 and for "DevOps engineer" generally vary by a wide margin — treat any single number with caution. ZipRecruiter's listing specifically for AZ-400 certification jobs showed an average of roughly $88.94 an hour as of June 2026, while general DevOps engineer salary surveys from the same period range from about $103,000 to over $144,000 a year in base pay depending on the source and seniority measured. Those differences come from different job titles, different seniority mixes and different data sources, not from one number being wrong — the certification alone won't set your salary; your role, your employer and your experience will. Source: $82-$98/hr Az 400 Certification Jobs Hiring Now Jun 26, DevOps Engineer Salary 2026: Pay by Level, Cert, and Location
  • The exam demands breadth, not just one skill. More than half the exam weight sits in build and release pipelines alone, and the remaining skill areas span source control strategy, security and compliance, and monitoring — so passing it signals exposure across the whole DevOps lifecycle rather than depth in a single tool.
  • It is named explicitly in a meaningful slice of DevOps-adjacent postings. Job boards that track certification mentions in active postings list AZ-400 by name alongside AZ-104, AZ-204 and AZ-305 as a credential employers call out directly when hiring for Azure-based engineering roles. Source: $82-$98/hr Az 400 Certification Jobs Hiring Now Jun 26

How Long Will I Have to Spend Studying for the AZ-400?

The honest answer is that it depends on how much you already know. Microsoft's own description of the candidate says that as a DevOps engineer, you are a developer or infrastructure administrator who also has subject matter expertise in working with people, processes, and products to enable continuous delivery of value in organizations, and that you must have experience both administering and developing in Azure, with strong skills in at least one of these areas, as well as experience implementing both GitHub and Azure DevOps solutions. If that’s your background, you’ve got a good start.

In our plan, you pick the areas of AZ-400 that matter to you — for the exam and for your job — and build a study plan from our domain reviews. Then you take an initial exam, backed by Microsoft Azure’s own documentation, to see where you need to focus to meet your study plan’s goals (our exam review will show you that).

In our store, you can buy a single exam or, if you intend to stick with us, our standard package — which includes, for example, custom drills for the areas our review showed that you need to strengthen (both domain knowledge and exam-taking skills). Repeat with fresh exams, step up to a challenge exam, take advantage of Mentor, and walk into the real exam with your own two-page cheat sheet. See how it works.

How Hard Is the AZ-400 Exam?

Another honest answer: since Microsoft Azure doesn’t publish pass rates, no one knows (including us). What Microsoft Azure does publish: you need a score of 700 or greater to pass. That's a scaled score, not 70% of the questions. The skills it measures, and how much each area weighs, are listed below.

We can tell you that we update our exams monthly, so they always reflect the current state of both the certification and the documentation that supports it. That means our exams follow the certification’s current topic weights, and our domain reviews and explanations are always up to date.

Start Preparing

We can’t tell you how well you know the content — you need to take one of our real exams for that. But our full exams also tell you how you miss: what question answering habits are tripping you up (and we do it across six kinds of ‘bad habits’). We have over 100 answers written that not only test your knowledge but catch those specific bad habits.

These 10 questions, for example, find which kind of ‘almost right’ answers catch you:

Sample exam coming soon.

Skills at a glance

Design and implement processes and communications10–15%
  • Design and implement a structure for the flow of work, including GitHub Flow
  • Design and implement a strategy for feedback cycles, including notifications and GitHub Issues
  • Design and implement integration for tracking work, including GitHub projects, Azure Boards, and repositories
  • Design and implement source, bug, and quality traceability
  • Design and implement a dashboard, including flow of work, such as cycle times, time to recovery, and lead time
  • Design and implement appropriate metrics and queries for project planning
  • Design and implement appropriate metrics and queries for development
  • Design and implement appropriate metrics and queries for testing
  • Design and implement appropriate metrics and queries for security
  • Design and implement appropriate metrics and queries for delivery
  • Design and implement appropriate metrics and queries for operations
  • Document a project by configuring wikis and process diagrams, including Markdown and Mermaid syntax
  • Configure release documentation, including release notes and API documentation
  • Automate creation of documentation from Git history
  • Configure integration by using webhooks
  • Configure integration between Azure Boards and GitHub repositories
  • Configure integration between GitHub or Azure DevOps and Microsoft Teams
Design and implement a source control strategy10–15%
  • Design a branch strategy, including trunk-based, feature branch, and release branch
  • Design and implement a pull request workflow by using branch policies and branch protection rules
  • Implement branch merging restrictions by using branch policies and branch protection rules
  • Design and implement a strategy for managing large files, including Git Large File Storage (LFS) and git-fat
  • Design a strategy for scaling and optimizing a Git repository, including Scalar and cross-repository sharing
  • Configure permissions in the source control repository
  • Configure tags to organize the source control repository
  • Recover specific data by using Git commands
  • Remove specific data from source control
Design and implement build and release pipelines50–55%
  • Recommend package management tools including GitHub Packages and Azure Artifacts
  • Design and implement package feeds and views for local and upstream packages
  • Design and implement a dependency versioning strategy for code assets and packages, including semantic versioning (SemVer) and date-based (CalVer)
  • Design and implement a versioning strategy for pipeline artifacts
  • Design and implement quality and release gates, including security and governance
  • Design a comprehensive testing strategy, including local tests, unit tests, integration tests, and load tests
  • Implement tests in a pipeline, including configuring test tasks, configuring test agents, and integration of test results
  • Implement code coverage analysis
  • Select a deployment automation solution, including GitHub Actions and Azure Pipelines
  • Design and implement a GitHub runner or Azure DevOps agent infrastructure, including cost, tool selection, licenses, connectivity, and maintainability
  • Design and implement integration between GitHub repositories and Azure Pipelines
  • Develop and implement pipeline trigger rules
  • Develop pipelines by using YAML
  • Design and implement a strategy for job execution order, including parallelism and multi-stage pipelines
  • Develop and implement complex pipeline scenarios, such as hybrid pipelines, VM templates, and self-hosted runners or agents
  • Create reusable pipeline elements, including YAML templates, task groups, variables, and variable groups
  • Design and implement checks and approvals by using YAML-based environments
  • Design a deployment strategy, including blue-green, canary, ring, progressive exposure, feature flags, and A/B testing
  • Design a pipeline to ensure that dependency deployments are reliably ordered
  • Plan for minimizing downtime during deployments by using load balancing, rolling deployments, and deployment slot usage and swap
  • Design a hotfix path plan for responding to high-priority code fixes
  • Design and implement a resiliency strategy for deployment
  • Implement feature flags by using Azure App Configuration Feature Manager
  • Implement application deployment by using containers, binaries, and scripts
  • Implement a deployment that includes database tasks
  • Recommend a configuration management technology for application infrastructure
  • Implement a configuration management strategy for application infrastructure
  • Define an IaC strategy, including source control and automation of testing and deployment
  • Design and implement desired state configuration for environments, including Azure Automation State Configuration, Azure Resource Manager, Bicep, and Azure Machine Configuration
  • Design and implement Azure Deployment Environments for on-demand self-deployment
  • Monitor pipeline health, including failure rate, duration, and flaky tests
  • Optimize a pipeline for cost, time, performance, and reliability
  • Optimize pipeline concurrency for performance and cost
  • Design and implement a retention strategy for pipeline artifacts and dependencies
  • Migrate a pipeline from classic to YAML in Azure Pipelines
Develop a security and compliance plan10–15%
  • Choose between Microsoft Entra service principals and managed identities for Azure resources (system-assigned and user-assigned)
  • Implement and manage GitHub authentication, including GitHub Apps, GITHUB_TOKEN, and personal access tokens
  • Implement and manage Azure DevOps service connections and personal access tokens
  • Design and implement permissions and roles in GitHub
  • Design and implement permissions and security groups in Azure DevOps
  • Recommend appropriate access levels, including stakeholder access in Azure DevOps and outside collaborator access in GitHub
  • Configure projects and teams in Azure DevOps
  • Implement and manage secrets, keys, and certificates by using Azure Key Vault
  • Implement and manage secrets and secretless authentication (for example, workload identity federation/OpenID Connect) in GitHub Actions and Azure Pipelines
  • Design and implement a strategy for managing sensitive files during deployment, including Azure Pipelines secure files
  • Design pipelines to prevent leakage of sensitive information
  • Design a strategy for security and compliance scanning, including dependency, code, secret, and licensing scanning
  • Configure Microsoft Defender for Cloud DevOps Security
  • Configure GitHub Advanced Security for GitHub and GitHub Advanced Security for Azure DevOps
  • Integrate GitHub Advanced Security with Microsoft Defender for Cloud
  • Automate container scanning, including scanning container images and configuring an action to run CodeQL analysis in a container
  • Automate analysis of vulnerabilities of open-source components by using Dependabot alerts
Implement an instrumentation strategy5–10%
  • Configure Azure Monitor and Azure Monitor Logs to integrate with DevOps tools
  • Configure collection of telemetry by using Azure Monitor Application Insights, Azure VM Insights, Azure Container Insights, Azure Monitor for Storage, and Azure Monitor for Networks
  • Configure monitoring in GitHub, including enabling insights and creating and configuring charts
  • Configure alerts for events in GitHub Actions and Azure Pipelines
  • Inspect infrastructure performance indicators, including CPU, memory, disk, and network
  • Analyze metrics by using collected telemetry, including usage and application performance
  • Inspect distributed tracing by using Azure Monitor Application Insights
  • Interrogate logs using basic Kusto Query Language (KQL) queries

Domains

Design and implement processes and communications10–15%
Design and implement traceability and flow of work
  • Design and implement a structure for the flow of work, including GitHub Flow
  • Design and implement a strategy for feedback cycles, including notifications and GitHub Issues
  • Design and implement integration for tracking work, including GitHub projects, Azure Boards, and repositories
  • Design and implement source, bug, and quality traceability
Design and implement appropriate metrics and queries for DevOps
  • Design and implement a dashboard, including flow of work, such as cycle times, time to recovery, and lead time
  • Design and implement appropriate metrics and queries for project planning
  • Design and implement appropriate metrics and queries for development
  • Design and implement appropriate metrics and queries for testing
  • Design and implement appropriate metrics and queries for security
  • Design and implement appropriate metrics and queries for delivery
  • Design and implement appropriate metrics and queries for operations
Configure collaboration and communication
  • Document a project by configuring wikis and process diagrams, including Markdown and Mermaid syntax
  • Configure release documentation, including release notes and API documentation
  • Automate creation of documentation from Git history
  • Configure integration by using webhooks
  • Configure integration between Azure Boards and GitHub repositories
  • Configure integration between GitHub or Azure DevOps and Microsoft Teams
Design and implement a source control strategy10–15%
Design and implement branching strategies for the source code
  • Design a branch strategy, including trunk-based, feature branch, and release branch
  • Design and implement a pull request workflow by using branch policies and branch protection rules
  • Implement branch merging restrictions by using branch policies and branch protection rules
Configure and manage repositories
  • Design and implement a strategy for managing large files, including Git Large File Storage (LFS) and git-fat
  • Design a strategy for scaling and optimizing a Git repository, including Scalar and cross-repository sharing
  • Configure permissions in the source control repository
  • Configure tags to organize the source control repository
  • Recover specific data by using Git commands
  • Remove specific data from source control
Design and implement build and release pipelines50–55%
Design and implement a package management strategy
  • Recommend package management tools including GitHub Packages and Azure Artifacts
  • Design and implement package feeds and views for local and upstream packages
  • Design and implement a dependency versioning strategy for code assets and packages, including semantic versioning (SemVer) and date-based (CalVer)
  • Design and implement a versioning strategy for pipeline artifacts
Design and implement a testing strategy for pipelines
  • Design and implement quality and release gates, including security and governance
  • Design a comprehensive testing strategy, including local tests, unit tests, integration tests, and load tests
  • Implement tests in a pipeline, including configuring test tasks, configuring test agents, and integration of test results
  • Implement code coverage analysis
Design and implement pipelines
  • Select a deployment automation solution, including GitHub Actions and Azure Pipelines
  • Design and implement a GitHub runner or Azure DevOps agent infrastructure, including cost, tool selection, licenses, connectivity, and maintainability
  • Design and implement integration between GitHub repositories and Azure Pipelines
  • Develop and implement pipeline trigger rules
  • Develop pipelines by using YAML
  • Design and implement a strategy for job execution order, including parallelism and multi-stage pipelines
  • Develop and implement complex pipeline scenarios, such as hybrid pipelines, VM templates, and self-hosted runners or agents
  • Create reusable pipeline elements, including YAML templates, task groups, variables, and variable groups
  • Design and implement checks and approvals by using YAML-based environments
Design and implement deployments
  • Design a deployment strategy, including blue-green, canary, ring, progressive exposure, feature flags, and A/B testing
  • Design a pipeline to ensure that dependency deployments are reliably ordered
  • Plan for minimizing downtime during deployments by using load balancing, rolling deployments, and deployment slot usage and swap
  • Design a hotfix path plan for responding to high-priority code fixes
  • Design and implement a resiliency strategy for deployment
  • Implement feature flags by using Azure App Configuration Feature Manager
  • Implement application deployment by using containers, binaries, and scripts
  • Implement a deployment that includes database tasks
Design and implement infrastructure as code (IaC)
  • Recommend a configuration management technology for application infrastructure
  • Implement a configuration management strategy for application infrastructure
  • Define an IaC strategy, including source control and automation of testing and deployment
  • Design and implement desired state configuration for environments, including Azure Automation State Configuration, Azure Resource Manager, Bicep, and Azure Machine Configuration
  • Design and implement Azure Deployment Environments for on-demand self-deployment
Maintain pipelines
  • Monitor pipeline health, including failure rate, duration, and flaky tests
  • Optimize a pipeline for cost, time, performance, and reliability
  • Optimize pipeline concurrency for performance and cost
  • Design and implement a retention strategy for pipeline artifacts and dependencies
  • Migrate a pipeline from classic to YAML in Azure Pipelines
Develop a security and compliance plan10–15%
Design and implement authentication and authorization methods
  • Choose between Microsoft Entra service principals and managed identities for Azure resources (system-assigned and user-assigned)
  • Implement and manage GitHub authentication, including GitHub Apps, GITHUB_TOKEN, and personal access tokens
  • Implement and manage Azure DevOps service connections and personal access tokens
  • Design and implement permissions and roles in GitHub
  • Design and implement permissions and security groups in Azure DevOps
  • Recommend appropriate access levels, including stakeholder access in Azure DevOps and outside collaborator access in GitHub
  • Configure projects and teams in Azure DevOps
Design and implement a strategy for managing sensitive information in automation
  • Implement and manage secrets, keys, and certificates by using Azure Key Vault
  • Implement and manage secrets and secretless authentication (for example, workload identity federation/OpenID Connect) in GitHub Actions and Azure Pipelines
  • Design and implement a strategy for managing sensitive files during deployment, including Azure Pipelines secure files
  • Design pipelines to prevent leakage of sensitive information
Automate security and compliance scanning
  • Design a strategy for security and compliance scanning, including dependency, code, secret, and licensing scanning
  • Configure Microsoft Defender for Cloud DevOps Security
  • Configure GitHub Advanced Security for GitHub and GitHub Advanced Security for Azure DevOps
  • Integrate GitHub Advanced Security with Microsoft Defender for Cloud
  • Automate container scanning, including scanning container images and configuring an action to run CodeQL analysis in a container
  • Automate analysis of vulnerabilities of open-source components by using Dependabot alerts
Implement an instrumentation strategy5–10%
Configure monitoring for a DevOps environment
  • Configure Azure Monitor and Azure Monitor Logs to integrate with DevOps tools
  • Configure collection of telemetry by using Azure Monitor Application Insights, Azure VM Insights, Azure Container Insights, Azure Monitor for Storage, and Azure Monitor for Networks
  • Configure monitoring in GitHub, including enabling insights and creating and configuring charts
  • Configure alerts for events in GitHub Actions and Azure Pipelines
Analyze metrics from instrumentation
  • Inspect infrastructure performance indicators, including CPU, memory, disk, and network
  • Analyze metrics by using collected telemetry, including usage and application performance
  • Inspect distributed tracing by using Azure Monitor Application Insights
  • Interrogate logs using basic Kusto Query Language (KQL) queries