AZ-400 study scenarios: three profiles
How you should study for AZ-400 depends on one number and one requirement: build and release pipelines are 50 to 55% of the exam, and Microsoft’s audience profile expects experience with both GitHub and Azure DevOps. A candidate who is strong on one product and thin on pipelines, or strong on pipelines in one product only, fails for different reasons, so the plan differs.
Example profiles, not real people. The profiles below are illustrative planning examples built from the official exam outline. They are not reviews or reports of anyone’s result.
The study plan assumes four weeks at 8 to 10 hours a week for someone who already builds CI/CD, with two of the four weeks on pipelines. The scenarios below adjust that baseline. Every hour figure is a planning assumption, not a promise.
The Azure Pipelines author who has never opened GitHub Actions
Starting point. Writes multi-stage YAML, templates and environments in Azure DevOps most weeks. Branch policies and variable groups are routine.
Where the time goes. The pipelines domain (50 to 55%) is already strong, but many questions give one side of a pair and expect the other: branch policy and branch protection rule, environment approval and GitHub environment reviewer, template and reusable workflow, service connection and federated credential. The security domain (10 to 15%) adds GitHub Advanced Security, CodeQL, Dependabot and workload identity federation. Instrumentation (5 to 10%) is small but predictable.
The trap. Assuming concept parity means syntax parity. A question about a reusable workflow or composite action is not answered by a template.
Order. GitHub equivalents first, then security and secretless authentication, then a light revision of pipeline strategy.
Time budget. A reasonable planning assumption is 24 to 30 hours: the plan’s weeks 1 and 4 in full and weeks 2 and 3 compressed, as the plan suggests for people who already run pipelines.
The AZ-104 administrator with no pipeline experience
Starting point. Holds or is working toward Azure Administrator Associate, so identities, networking and App Service are comfortable. Has not written a pipeline, and uses Git lightly.
Where the time goes. Almost entirely in the pipelines domain: YAML triggers, stages and conditions, testing strategy, package feeds, deployment strategies and infrastructure as code from a pipeline. The source control domain (10 to 15%) is next, because Git beyond commit and push is assumed.
The trap. Reading about pipelines instead of writing them. More than half the marks are on a skill that only comes from running broken pipelines.
Order. Git and branching, then a single small app with a build pipeline, then deployments and IaC, then security and monitoring.
Time budget. A reasonable planning assumption is 64 to 80 hours over eight weeks, which is the plan’s “double the timeline” advice at the same weekly pace. If half the time goes to the pipelines domain, that is roughly 32 to 40 hours of hands-on building.
The GitHub-only developer who has not used Azure DevOps or Azure operations
Starting point. Comfortable with Actions, pull requests, branch protection and Dependabot. Has little exposure to Azure Boards, Azure Repos, Azure Artifacts, service connections or the Azure resources the pipelines deploy to.
Where the time goes. Processes and communications (10 to 15%) hides Azure Boards, work item linking and dashboards. In the pipelines domain, the Azure Pipelines equivalents, deployment slots, Bicep and Azure App Configuration feature flags need attention. Security (10 to 15%) and instrumentation (5 to 10%) need Key Vault, managed identities and basic KQL.
The trap. Over-trusting the GitHub strengths. The exam audience also expects Azure administration or development skills, and Microsoft’s retired Azure Developer Associate route means the practical prerequisite is AZ-104.
Order. Azure Boards and Azure Repos, then Azure Pipelines, then Azure resources and IaC, then monitoring.
Time budget. A reasonable planning assumption is 28 to 36 hours: the four-week plan with the GitHub-flow material in week 1 cut and the Azure-side material in weeks 2 to 4 expanded.
The three AZ-400 profiles compared
| Profile | Front-load | Main risk |
|---|---|---|
| Azure Pipelines author | GitHub Actions equivalents, security | Syntax that differs from the familiar product |
| AZ-104 administrator | Pipelines and Git (60 to 70% together) | Studying instead of building |
| GitHub-only developer | Azure Boards, Azure Pipelines, Azure resources | Missing the Azure-side halves of paired questions |
How to check which AZ-400 profile fits before booking
Take the sample questions and sort each miss into pipelines, source control, security, process or monitoring. The exam format page lists the 700 scaled score and the possible labs, which affect the 100 or 120 minutes. Then work through the study plan, finish with the timed practice test, and read prerequisites and exam tips to confirm the associate credential requirement.
If your gap turns out to be Azure administration rather than pipelines, the AZ-104 hub is the better first exam.