AZ-400 cheat sheet

Updated October 9, 2026

Last-minute reference for AZ-400. Build and release pipelines are more than half the exam; instrumentation is the smallest area.

Exam facts

Duration100 minutes (120 if the exam may contain labs)
Passing score700 / 1000
QuestionsNot published for this exam
PriceSet per country or region; shown at booking
Languages10
RenewalFree, annually

Skill areas

AreaWeight
Build and release pipelines50-55%
Processes and communications10-15%
Source control strategy10-15%
Security and compliance plan10-15%
Instrumentation strategy5-10%

Requirement to answer

RequirementAnswer
Link commits and PRs to Azure Boards work itemsBoards-GitHub integration, AB#id
Diagram in a wiki as textMermaid in Markdown
Call another system on an eventWebhook / service hook
Frequent deploys, strong tests, no long branchesTrunk-based + feature flags
Maintain several shipped versionsRelease branches
Enforce reviews and builds before mergeBranch policy (Azure Repos) / branch protection (GitHub)
Large binaries in GitGit LFS
Very large repository performanceScalar, partial clone, sparse checkout
Undo a pushed commit safelygit revert
Find a deleted branch’s commitsgit reflog
Secret committedRotate, then rewrite history
Same steps in many pipelinesTemplates / reusable workflows
Approval that YAML edits cannot removeEnvironment check
Private network build access, low upkeepScale set agents / self-hosted runners
Promote tested packagesAzure Artifacts views
Breaking change in SemVerIncrement MAJOR
Instant rollback, near-zero downtimeBlue-green / slot swap
Limited exposure firstCanary or ring
Switch a feature on without deployingFeature flag, App Configuration
On-demand environments from approved templatesAzure Deployment Environments
Azure deployment without stored secretWorkload identity federation (OIDC)
Code on an Azure resource calls AzureManaged identity
Per-run token inside a workflowGITHUB_TOKEN
Central secret storeAzure Key Vault
File secrets in pipelinesSecure files
Vulnerable dependenciesDependabot, dependency review
Code vulnerabilitiesCodeQL
Pipeline and code findings in cloud security viewDefender for Cloud DevOps security
Request flow across servicesApplication Insights distributed tracing
Probe site from other regionsAvailability test
AKS pod metricsContainer insights

Deployment strategies

StrategyKey idea
Blue-greenTwo environments, switch all traffic
CanarySmall share of traffic first
RingGradual rings of users
RollingBatches of instances
Feature flagDeploy off, release later
A/BCompare variants

YAML keywords

ConceptAzure PipelinesGitHub Actions
Triggertrigger, pron:
OrderingdependsOnneeds:
Conditioncondition:if:
Reusetemplatesreusable workflows, composite actions
Approvalenvironment checksenvironment required reviewers

Common traps

  • Lead time versus cycle time: lead time starts at the request.
  • Managed identities cannot be attached to GitHub-hosted runners; use federation.
  • A custom condition replaces the default success check.
  • Deleting a secret from the latest commit leaves it in history.
  • Log alerts need a Log Analytics workspace; platform metrics do not.

More detail: exam format and study plan. Check the glossary for unfamiliar terms.