I Failed the AZ-400. Here's What Worked the Second Time

Score: 680. Twenty points short. That was my first AZ-400 attempt.

The worst part? I actually felt good walking out of the testing center. Like, genuinely confident. Then the results email came and I just stared at the screen for a solid minute. Twenty points. That's maybe 2-3 questions I could've gotten right.

Six weeks later, I passed with 780. Here's what changed between attempt one and attempt two — because it wasn't just "study more." It was study differently.

Why I Failed the First Time

Let me be specific about what went wrong, because these mistakes are common.

Mistake 1: I Studied Azure DevOps, Not DevOps on Azure

There's a subtle but critical difference. I focused almost entirely on Azure DevOps (the product — boards, repos, pipelines). The exam tests DevOps practices implemented on Azure, which includes GitHub Actions, Bicep/ARM templates, Azure Monitor, security scanning tools, and way more than just the Azure DevOps product.

Mistake 2: I Skipped Infrastructure as Code

ARM templates and Bicep? I thought I'd get by knowing they existed. Nope. The exam asked me to read template snippets and identify issues. I couldn't.

Mistake 3: No Practice Tests

I went in cold. No timed practice exams. The time pressure caught me off guard on case studies, and I rushed through the last 10 questions.

The AZ-400 Exam: What You're Actually Tested On

The AZ-400 is the exam for the Azure DevOps Engineer Expert certification. But here's the catch — you can't just take AZ-400. You need a prerequisite: either AZ-104 (Administrator) or AZ-204 (Developer). Then AZ-400 stacks on top to get the Expert title.

My 8-Week Study Plan (The One That Worked)

After failing, I rebuilt my study plan from scratch. Here's exactly what I did over 8 weeks, spending about 12-15 hours per week.

Week 1: YAML Pipelines Deep Dive

This is the most important week. I'm not exaggerating — if you understand YAML pipelines cold, you've covered 30%+ of the exam.

• Pipeline structure: stages, jobs, steps, tasks. Know how they nest and when to use each level
• Variables and parameters: runtime vs compile-time, variable groups, Key Vault integration
• Triggers: CI triggers, PR triggers, scheduled triggers, pipeline triggers (chaining)
• Templates: Step templates, job templates, stage templates. Extends templates for security

I wrote at least 15 different pipeline YAML files during this week. Not copied from tutorials — written from memory, then compared against docs. That active recall is what made the difference.

Week 2: GitHub Actions & Multi-Platform CI/CD

The 2026 version of AZ-400 tests GitHub Actions almost as much as Azure Pipelines. Don't skip this.

• GitHub Actions workflows: triggers, jobs, steps, environments, secrets
• GitHub Advanced Security: CodeQL, secret scanning, Dependabot
• Azure DevOps vs GitHub: When to use which. Feature comparison. Migration patterns
• Self-hosted runners vs Microsoft-hosted agents: Pros, cons, security implications

Weeks 3-4: Infrastructure as Code

This is where I failed last time. Not this time.

• Bicep: Microsoft's preferred IaC language now. Modules, parameters, outputs, conditions
• ARM templates: Still tested. JSON structure, linked templates, deployment modes (incremental vs complete)
• Terraform on Azure: Basic provider config, state management with Azure Storage backend
• Azure Resource Manager: Template specs, deployment stacks, what-if operations

My approach: I deployed the same infrastructure (App Service + SQL Database + Key Vault) using Bicep, ARM, and Terraform. Seeing the same thing in three different formats cemented the concepts.

Week 5: Source Control and Branching

• Git branching strategies: GitFlow, trunk-based development, release branches. Know when each is appropriate
• Pull request workflows: Branch policies, required reviewers, build validation, status checks
• Monorepo vs polyrepo: Trade-offs and when to use each
• Git hooks and pre-commit checks: Client-side and server-side hooks

The branching strategy questions are trickier than they look. It's not "which is best" — it's "given this team size and release cadence, which strategy fits." Context matters.

Week 6: Security and Compliance

• Azure Key Vault: Secrets, certificates, keys. Integration with pipelines and apps
• Managed identities for pipelines: Service connections, workload identity federation
• SAST/DAST tools: SonarQube, OWASP ZAP, Microsoft Security DevOps extension
• Container security: Image scanning, Defender for Containers, admission controllers
• Compliance: Azure Policy, Azure Blueprints, governance patterns in CI/CD

Week 7: Monitoring and Feedback

• Azure Monitor: Metrics, logs, alerts, action groups, workbooks
• Application Insights: Availability tests, live metrics, custom events, distributed tracing
• Release gates: Pre-deployment and post-deployment gates using Azure Monitor queries
• Feature flags: Azure App Configuration feature management, progressive rollout

Week 8: Practice Tests and Targeted Review

This was the game-changer. I took 4 full-length practice tests on ExamCert's AZ-400 practice exam.

• Test 1: Identified weak areas (IaC and GitHub Actions)
• Test 2: Focused review on weak areas, then retested
• Test 3: Full simulation with timer — practiced time management
• Test 4: Final confidence check two days before the exam

The 7 Things I Wish Someone Told Me

1. YAML pipeline questions are NOT open book. You need to know the syntax from memory. Indentation, property names, task inputs. Practice writing them without the docs open.

2. GitHub Actions is equally important. The exam doesn't favor Azure DevOps over GitHub anymore. Study both equally.

3. Bicep is the future. ARM templates still appear, but Bicep questions are increasing. If you're short on time, prioritize Bicep over ARM.

4. "Shift left" is always the answer. When in doubt on security questions, the answer that moves testing/scanning earlier in the pipeline is usually correct.

5. Know your deployment strategies cold. Blue-green, canary, rolling, A/B testing. Not just what they are, but how to implement them in Azure Pipelines and GitHub Actions.

6. Release gates are testable. Understand how to configure pre-deployment gates that query Azure Monitor metrics. The YAML syntax for these is a favorite exam topic.

7. Don't ignore Azure Boards. The "configure processes and communications" section is only 10-15%, but those are free points if you know work item types, process customization, and dashboard widgets.

AZ-400 Career Impact and Salary

The DevOps Engineer Expert certification is one of Microsoft's most respected certs because it requires a prerequisite — you can't just cram for one exam and get it.

Salary ranges for Azure DevOps Engineers in 2026:

• US: $130K-$170K USD
• Australia: $140K-$180K AUD
• UK: £75K-£110K
• Remote roles: Often at the higher end due to demand exceeding supply

The combination of AZ-204 + AZ-400 (Developer + DevOps Expert) is particularly powerful for senior developer roles. It signals that you can both build and ship software on Azure — which is exactly what companies want.

Should You Take AZ-104 or AZ-204 as Your Prerequisite?

This depends entirely on your background:

• Take AZ-104 first if: you're an infrastructure person, sysadmin, or platform engineer. AZ-104 → AZ-400 gives you the "infrastructure DevOps" angle
• Take AZ-204 first if: you're a developer. AZ-204 → AZ-400 gives you the "developer DevOps" angle

Both paths lead to the same Azure DevOps Engineer Expert certification. But the AZ-204 path gives you more relevant overlap with AZ-400 content (CI/CD, containers, app deployment).

Frequently Asked Questions