Exampractice
Microsoft & Azure

Azure DevOps Engineer Exam Preparation Guide

How to prepare for AZ-400 end to end — the AZ-104 prerequisite, exam domains, a prioritised study sequence, resources and readiness checks.

Daniel Carter · 11 min read
Metro-map style diagram of a CI/CD pipeline representing the AZ-400 preparation journey starting from AZ-104

Before you plan a single study session for AZ-400, check one thing: do you hold an active Azure Administrator Associate (AZ-104) or Azure Developer Associate (AZ-204) certification? Microsoft's DevOps Engineer Expert credential is one of only two Microsoft certifications with a mandatory certification prerequisite, and passing AZ-400 without one of those two associates earns you an exam pass but no certification. With AZ-204 retired as of mid-2026, AZ-104 is now the practical entry route for new candidates — which reshapes how most people should sequence their preparation.

This guide covers the whole journey: confirming your prerequisite, understanding what AZ-400 "Designing and Implementing Microsoft DevOps Solutions" actually measures, a prioritised study sequence, the resources worth your time, and how to know you are ready to book. For the credential's formal details — booking mechanics, format and pricing — the Azure DevOps Engineer certification guide is the companion piece; this article is about the preparation itself.

Step zero: sort the prerequisite before anything else

To earn Microsoft Certified: DevOps Engineer Expert you must hold either Azure Administrator Associate (AZ-104) or Azure Developer Associate (AZ-204). Three situations cover almost everyone:

You already hold AZ-104 or a still-valid AZ-204. You are clear to prepare for AZ-400 directly. Keep an eye on your associate's renewal date — role-based Microsoft certifications expire after one year, renewed free through an unproctored online assessment on Microsoft Learn — because the Expert credential depends on the prerequisite being in place.

You hold neither. Plan for AZ-104 first. Since Microsoft retired the Azure Developer Associate certification in 2026, AZ-104 is the route that remains open to new candidates. That is not a detour to resent: AZ-400 assumes you can already operate Azure — identities, networking, compute, storage — and AZ-104 builds exactly that base. The Azure Administrator certification guide covers that exam in full.

You held AZ-204 but it has lapsed or is lapsing. Retired certifications remain on your transcript but can no longer be renewed. Microsoft had not published detailed transition guidance at the time of writing, so verify your own standing on the official DevOps Engineer certification page before assuming your prerequisite still qualifies — and if in doubt, the AZ-104 route removes the ambiguity.

If you are unsure whether the DevOps track is even the right one versus a development-focused path, that comparison lives in Azure Developer vs Azure DevOps Engineer — one sentence of guidance here: AZ-400 is about how software is built, shipped and observed, not about writing the application code itself.

What AZ-400 actually measures

The exam's official title — Designing and Implementing Microsoft DevOps Solutions — is precise. This is a design-and-implementation exam about the delivery system around code, spanning both GitHub and Azure DevOps. Its skills areas cover:

  • Processes and communications — how work flows, how teams collaborate, how feedback loops are wired into delivery.
  • Source control strategy — designing and implementing how code is branched, reviewed, merged and governed.
  • Build and release pipelines — the core of the exam's practical weight: continuous integration and continuous delivery across GitHub Actions and Azure Pipelines.
  • Security and compliance plan — securing the pipeline itself: secrets, dependencies, permissions, and compliance built into delivery rather than bolted on.
  • Instrumentation strategy — monitoring, telemetry and the feedback data that closes the DevOps loop.

Notice what that list is not. It is not an Azure services catalogue exam, and it is not a coding exam. Nearly every question lives at the level of "given this team, this codebase and this constraint, which delivery design is right?" — which is why candidates who have only ever followed a pipeline someone else built find it harder than the topic list suggests.

Two things Microsoft deliberately does not publish: the number of questions, and (on the certification page we verified) the exam duration. Ignore folklore question counts, and confirm the current duration on the official exam page when you book. What is published: the pass mark is 700 on a 1,000-point scale — a scaled score, not 70 per cent — and pricing varies by country or region.

The dual-platform reality: GitHub and Azure DevOps

The single most underestimated aspect of modern AZ-400 preparation is that it covers both GitHub and Azure DevOps. Many candidates arrive fluent in one and hazy on the other — a GitHub Actions native who has never configured Azure Boards, or an Azure DevOps veteran who has never written a reusable GitHub workflow. Audit yourself honestly at the start: for every delivery concept in your stronger platform, can you name and configure its counterpart in the other? If not, that gap goes at the top of your study plan.

A prioritised study sequence

Study time should follow leverage, not the order topics appear in the outline. This sequence front-loads the areas that carry the most questions and the most transfer value.

1. Pipelines first, and hands-on only

Build and release pipelines are the spine of the exam. Reading about YAML pipelines teaches you almost nothing the exam can use; building them does. Work in a real repository:

  1. Create a small application repo (any language you know).
  2. Build a CI workflow in GitHub Actions — triggers, jobs, matrix builds, caching, artifacts.
  3. Rebuild the same CI in Azure Pipelines, noting where concepts map and where they diverge.
  4. Extend both into CD: environments, approvals, deployment strategies, rollback thinking.
  5. Break things deliberately — a failing test gate, a missing secret, a bad trigger filter — and fix them. Troubleshooting questions reward people who have seen the failure modes.

2. Source control strategy second

Branching models, pull-request policies, code review gates, repository permissions and monorepo-versus-multirepo trade-offs. This domain is conceptual as much as practical, and it interlocks with pipelines: a branching strategy is only as real as the automation that enforces it. Practise articulating why a team with a given release cadence would pick a given model — that judgement is what the questions probe.

3. Pipeline security and compliance third

Secrets management, service connections and workload identities, dependency and container scanning, and permission boundaries between the people, the pipeline and the cloud. Your AZ-104 background helps here — this is where identity knowledge from the prerequisite pays direct dividends. Treat "how would this leak?" as your study question for every pipeline you built in step one.

4. Instrumentation and process last — but not never

Telemetry, monitoring strategy and feedback loops, plus the processes-and-communications material. Candidates skip these because they feel soft; that is precisely why they lose marks here. These topics are quick to cover relative to pipelines, so leaving them until later costs little — leaving them out entirely costs real points.

Resources that earn their place

Microsoft Learn's official AZ-400 learning paths. Free, aligned to the current skills outline, and the authoritative statement of scope. Use the official study guide as your syllabus checklist — when Microsoft updates the exam, this is where the change appears first.

A live sandbox: your own repos and a personal Azure DevOps organisation. Both GitHub and Azure DevOps offer free tiers generous enough for exam preparation. There is no substitute; the exam's scenario style presumes you have felt these tools push back at you.

Microsoft's free practice assessment. Microsoft provides free practice assessments on Microsoft Learn — use one early as a diagnostic, not late as a lottery ticket.

Timed third-party practice. Once the domains are covered, timed practice under exam-like conditions exposes pacing problems and weak domains that untimed study hides. A set of AZ-400 practice questions works best used diagnostically: sit a timed block, sort the misses by domain, and let the pattern — not your mood — choose next week's focus. Practice questions test your understanding of the exam objectives; if you find yourself memorising answers rather than reasoning to them, you have stopped preparing and started rehearsing.

Your own work history. Unusually for a certification, professional experience is a first-class study resource here. Every incident retro, every flaky pipeline, every branching argument your team ever had is exam-relevant. Write down how your organisation does source control, CI, CD, secrets and monitoring — then ask, domain by domain, whether you could defend or improve that design. AZ-400 questions are that exercise, formalised.

How long will preparation take?

Microsoft publishes no official study-hours figure, and any guide quoting one as a guarantee is guessing. The honest answer is that duration tracks your starting point on two axes: depth of hands-on delivery experience, and coverage across both platforms. An engineer who runs GitHub Actions and Azure Pipelines professionally is polishing gaps; an AZ-104 holder who has never owned a pipeline is building a skill, and building skills takes weeks of regular practice, not a revision blitz. Calibrate with evidence: an early diagnostic practice assessment tells you more about your timeline than any generic estimate.

Readiness checks: how to know you can book

Book the exam when the following are true, not when the calendar says so:

  • [ ] Prerequisite confirmed — AZ-104 (or valid AZ-204) showing on your Microsoft transcript.
  • [ ] You have built CI and CD in both platforms — from an empty repo to a gated deployment, without following a tutorial line by line.
  • [ ] You can argue trade-offs aloud — branching models, deployment strategies, secret-handling options — in terms of team size, cadence and risk.
  • [ ] Security questions do not scare you — you can trace how code, credentials and permissions flow through a pipeline and name the controls at each hop.
  • [ ] Timed practice is consistently comfortable — across domains, under time pressure, with your misses clustering in topics you can name and fix rather than scattering randomly.
  • [ ] The official study guide reads as a checklist, not a syllabus — every line item maps to something you have done, not just read.

When one box stays stubbornly unticked, that is your last study sprint defined for you.

Common preparation mistakes

Treating it as AZ-104 part two. The prerequisite exam rewards knowing Azure services; AZ-400 rewards designing delivery systems. Candidates who study by memorising service facts prepare for the wrong exam.

Single-platform preparation. Covering Azure Pipelines and hoping GitHub Actions questions will be guessable — or the reverse. The exam covers both by design.

All reading, no repos. Watching pipeline videos produces recognition, not recall. Scenario questions punish recognition-level knowledge precisely.

Ignoring process and instrumentation domains. Smaller domains are cheap marks for prepared candidates and a silent leak for everyone else.

Booking on hope. With retakes available only after a 24-hour wait — and longer waits after that — a readiness benchmark beats optimism. One timed, full-coverage practice run in the final week converts "probably ready" into evidence either way.

A worked example: eight weeks from AZ-104 holder to booking

Abstract sequences are easier to trust when you can see one applied. Consider a realistic candidate: a systems engineer, two years into an Azure operations role, AZ-104 earned last year and still active, comfortable in Azure Pipelines because her team uses them daily, but with GitHub experience limited to occasional pull requests.

Her audit (step zero) shows the classic single-platform profile, so her plan inverts the usual order of comfort: weeks one and two go to GitHub — recreating her team's real build in GitHub Actions, wiring branch protection and review rules on a personal repository, and mapping every Azure DevOps concept she uses at work to its GitHub counterpart. Weeks three and four extend both platforms into CD with environments, approvals and a deliberately broken deployment to practise rollback reasoning. Week five is pipeline security: rotating a leaked secret, replacing stored credentials with workload identities, and adding dependency scanning to both pipelines. Week six covers instrumentation and process material through Microsoft Learn's paths — her weakest reading-heavy week, kept short deliberately. Week seven is diagnostic: a timed practice block, misses sorted by domain, which reveals source-control strategy questions failing not on mechanics but on justifying model choices — so the final week is spent articulating trade-offs, not building more pipelines. She books for the end of week eight while the diagnostic evidence is fresh.

The details will differ for you; the shape should not. Audit first, spend time where the audit says, verify with timed evidence, then book.

Frequently asked questions

Is AZ-400 harder than AZ-104?

They are hard in different directions. AZ-104 tests whether you can operate Azure's services; AZ-400 tests whether you can design and implement the delivery system around software, and it assumes the operational knowledge rather than testing it. Candidates with real pipeline ownership often find AZ-400 more natural than AZ-104; candidates without it find the scenario judgement harder than any service-fact exam.

How many questions does AZ-400 have, and how long is it?

Microsoft does not publish question counts for its exams, and the certification page we verified does not state the AZ-400 duration — check the official exam page when you book rather than trusting third-party figures.

How much does the exam cost?

Microsoft prices exams by the country or region in which they are proctored, so there is no single official figure — confirm the fee for your country on the official AZ-400 exam page at booking time.

Does the DevOps Engineer Expert certification expire?

Yes — like all Microsoft role-based certifications it is valid for 12 months, renewed free through an unproctored, open-book online assessment on Microsoft Learn, available in the six months before expiry and retakeable if needed.

Can I sit AZ-400 before earning AZ-104?

You can sit the exam, but the Expert certification is only awarded once you hold Azure Administrator Associate (or a valid Azure Developer Associate). Passing the exam first leaves the credential pending, so most candidates sensibly sequence the prerequisite first — it is also the knowledge base AZ-400 quietly assumes.

Where AZ-400 fits, and your next move

AZ-400 sits at the expert tier of a certification family that runs fundamentals → associate → expert, and like all Microsoft role-based certifications it expires after one year with free online renewal — so the credential you are working towards is a practice, not a trophy. If your prerequisite is sorted and the readiness list above is mostly ticked, book a date three or four weeks out and let the deadline organise your final sprint. If the prerequisite is not sorted, your next exam is AZ-104, and the wider sequencing question — what comes after AZ-400, and what sits alongside it — is mapped in the Azure certifications roadmap.

Exam facts in this guide were checked against official certification-provider pages on . Fees, exam codes and policies change — confirm on the provider’s own site before you book.

Put it into practice

Test what you have just read

Reading about an exam only takes you so far. Work through practice questions for your certification and find the gaps before exam day does.

You may also like