AZ-400 Quick Reference: Every Number You Need to Memorise

AZ-400 Exam Overview: The Numbers That Matter

Before diving into study material, get the essential exam facts straight. The AZ-400 exam, titled 'Designing and Implementing Microsoft DevOps Solutions,' is a challenging certification that validates your ability to combine people, processes, and technologies to deliver continuous value. Here are the hard numbers you must know:

• Number of questions: 40-60 (typically around 50)
• Time limit: 120 minutes (plus 15 minutes for the non-scored demo and survey)
• Passing score: 700 out of 1000 (scaled score)
• Question types: Multiple choice, multiple select, drag-and-drop, build list, hot area, and case studies (case studies are not in this exam, but be prepared for scenario-based questions)
• Cost: $165 USD (varies by region)
• Validity: 1 year from the date of passing

Remember: there is no negative marking for incorrect answers, so always attempt every question.

Domain Weightings: Where to Focus Your Study

The AZ-400 exam is divided into six domains, each with a specific percentage of questions. Use this breakdown to allocate your study time effectively.

A free AZ-400 study plan turns that breakdown into a week-by-week schedule that fits your available time and includes full mock tests.

Notice that the first two domains together account for nearly half the exam. Prioritize these in your studies.

Must-Know Concepts for Each Major Domain

1. Design a DevOps Strategy (20-25%)

• DevOps transformation: Know the three ways of DevOps (flow, feedback, and continual learning) and how to apply them.
• Azure Boards: Understand work item types (epics, features, user stories, tasks, bugs) and how to configure area and iteration paths.
• Agile vs. Scrum vs. Kanban: Be able to recommend a process for a team based on their needs.
• Quality and release strategies: Know the difference between release gates, approval gates, and quality metrics.
• Security and compliance: Familiarize yourself with Azure Policy, RBAC, and secrets management (Azure Key Vault).

2. Implement DevOps Development Processes (20-25%)

• Version control: Know Git branching strategies (GitHub Flow, Git Flow, trunk-based) and when to use each.
• Azure Repos: Understand branch policies, pull requests, and protected branches.
• Code quality: Use SonarCloud, ESLint, or other tools to enforce code quality.
• Automated testing: Implement unit, integration, and acceptance tests in pipelines.
• Bicep and ARM templates: Know how to define infrastructure as code (IaC) for repeatable deployments.

3. Implement Continuous Integration (10-15%)

• Azure Pipelines: Configure CI pipelines using YAML or classic editor.
• Build agents: Understand Microsoft-hosted vs. self-hosted agents and when to use each.
• Pipeline triggers: Know the difference between CI triggers, PR triggers, and scheduled triggers.
• Artifacts: Use Azure Artifacts to store build outputs.
• Pipeline caching: Reduce build time by caching dependencies (e.g., npm, NuGet).

4. Implement Continuous Delivery (10-15%)

• Release pipelines: Design multi-stage deployment pipelines (dev, test, prod).
• Deployment strategies: Know blue-green, canary, and rolling deployments, and when to use each.
• Release gates: Implement health, security, and business approval gates.
• Azure App Service slots: Use deployment slots for zero-downtime deployments.
• Feature flags: Use LaunchDarkly or Azure App Configuration to toggle features.

5. Implement Dependency Management (5-10%)

• Azure Artifacts: Create and consume feeds for NuGet, npm, Maven, and Python packages.
• Package versioning: Follow SemVer (Semantic Versioning) and understand prerelease versions.
• Upstream sources: Configure upstream sources to cache packages from public repositories.
• Pipeline integration: Publish and consume packages from build pipelines.

6. Implement Application Infrastructure (10-15%)

• Infrastructure as Code (IaC): Use ARM templates, Bicep, or Terraform to provision Azure resources.
• Azure Kubernetes Service (AKS): Understand how to deploy and scale containerized applications.
• Azure Container Instances (ACI): Know when to use ACI instead of AKS.
• Configuration management: Use Azure Automation State Configuration (DSC) or Ansible.
• Secrets and certificates: Store and retrieve secrets using Azure Key Vault.

Common Exam Traps and How to Avoid Them

Even well-prepared candidates fall for these traps. Watch out for:

• Confusing Azure DevOps Services with Azure DevOps Server: Remember that 'Services' is cloud-based (SaaS), while 'Server' is on-premises.
• Mixing up YAML and classic pipelines: The exam often asks which approach is better for a scenario. YAML is preferred for source-control-driven pipelines, while classic is for simple, non-developer scenarios.
• Ignoring the 'most' and 'least' keywords: Questions often include 'most appropriate' or 'least likely.' Read carefully.
• Not understanding the difference between a release gate and an approval: Gates are automated checks (e.g., Azure Monitor alerts), approvals are manual sign-offs.
• Overlooking the cost factor: Sometimes the best answer is the one that minimizes cost, even if it's less feature-rich.

Final Study Tips

To pass the AZ-400, you need hands-on experience, not just theory. Spend time in the Azure portal and Azure DevOps. Create sample projects and practice building pipelines. The official Microsoft Learn path for AZ-400 is a great resource, but supplement it with practice exams to get used to the question style.

A free AZ-400 readiness check gives you a short set of practice questions with explanations and points you to the topic that needs more review.

Identify your weak spots early — work through Designing and Implementing Microsoft DevOps Solutions (AZ-400) mock test questions while you still have time to review.