Five DevOps domains, with weights set by Microsoft's April 2026 update. The build/release pipelines domain alone is weighted at 50–55% — more than the other four combined. Every domain summary below is paraphrased from the official skills outline.
Design and implement processes and communications10–15%
Traceability and flow of work — GitHub Flow, feedback cycles, GitHub Issues, GitHub Projects integration with Azure Boards. Metrics and queries for the full DevOps lifecycle (cycle time, time to recovery, lead time) plus project planning, development, testing, security, delivery, and operations. Configure collaboration: wikis with Markdown and Mermaid syntax, release notes, automated docs from Git history, webhook integrations, Microsoft Teams integration. Around 4–9 questions.
Design and implement a source control strategy10–15%
Branching strategies — trunk-based, feature branch, release branch — plus pull request workflows, branch policies and protection rules. Repository management at scale — Git Large File Storage (LFS), Scalar, cross-repository sharing, permissions, tags. Recovering specific data via Git commands and removing data from history. Around 4–9 questions.
Design and implement build and release pipelines50–55%
The largest domain by far. Package management (GitHub Packages, Azure Artifacts, SemVer, CalVer); testing strategy (unit, integration, load, code coverage, quality gates); pipeline implementation (YAML in Azure Pipelines AND GitHub Actions, agent/runner infrastructure, triggers, multi-stage pipelines, reusable templates, environment checks/approvals); deployment strategies (blue-green, canary, ring, progressive exposure, feature flags via Azure App Configuration, A/B testing, hotfix paths, deployment slots); IaC (Bicep, ARM, Azure Automation State Configuration, Azure Machine Configuration, Azure Deployment Environments); pipeline maintenance (health, optimisation, classic-to-YAML migration). Around 20–33 questions per sitting.
Develop a security and compliance plan10–15%
Authentication and authorisation — service principals vs Managed Identities (system-assigned vs user-assigned), GitHub Apps, GITHUB_TOKEN, personal access tokens, Azure DevOps service connections, GitHub permissions and roles, Azure DevOps permissions and security groups. Sensitive information management — Azure Key Vault, GitHub Secrets, OpenID Connect / workload identity federation. Security and compliance scanning — Microsoft Defender for Cloud DevOps Security, GitHub Advanced Security, container scanning, CodeQL, Dependabot. Around 4–9 questions.
Implement an instrumentation strategy5–10%
The smallest domain. Configure Azure Monitor and Azure Monitor Logs to integrate with DevOps tools; collect telemetry via Application Insights, VM Insights, Container Insights, and storage/network monitoring. Configure GitHub monitoring (insights, charts, alerts on Actions and Pipelines events). Analyse metrics — infrastructure indicators (CPU, memory, disk, network), application performance, distributed tracing, and basic Kusto Query Language (KQL) queries. Around 2–6 questions.