IT Certifications · AZ-400

Exam AZ-400: Designing and Implementing Microsoft DevOps Solutions Practice Test

Exam AZ-400: Designing and Implementing Microsoft DevOps Solutions focuses on integrating development and operations practices across software delivery. Its subject matter includes source control workflows, build and release automation, deployment safety, artifact handling, and managing credentials and configuration. The practice bank uses scenario-based questions about decisions teams make when building and deploying applications with Azure DevOps and related tools.

Exam overview

Exam providerMicrosoft
Exam codeAZ-400
CategoryIT Certifications

About the Exam AZ-400: Designing and Implementing Microsoft DevOps Solutions Exam

DevOps practitioners connect code changes to repeatable builds, tests, and deployments. Relevant skills include choosing Git workflows for isolated changes and review, configuring agents to run pipeline jobs, and keeping build environments consistent through controlled toolchains. Pipeline decisions involve preserving outputs as artifacts, promoting the same tested package across environments, and expressing dependencies when services must be deployed in sequence. Deployment scenarios may require techniques that validate an application before directing normal traffic to it. Secure delivery also depends on managing credentials to reduce exposure and separating secrets from reusable non-secret settings such as deployment regions. These tasks call for matching a delivery objective to an appropriate pipeline feature, then considering how the choice affects repeatability, isolation, deployment order, and operational risk.

Sample Practice Questions

Review a selection from this exam's published US Practice Tests practice bank.

Question 1

A team uses a self-hosted Azure Pipelines agent and wants it to build a repository hosted on GitHub. Which setup is needed for the agent to communicate with Azure DevOps and receive jobs?

  1. AInstall the agent and register it with an agent pool using the required authentication
  2. BAdd the agent's executable to the repository and invoke it from a build script
  3. CCreate a deployment environment and assign the agent as an approval
  4. DPublish the agent as a package in Azure Artifacts
Show answerCorrect answer: A

A self-hosted agent must be installed and configured to register with an Azure DevOps agent pool. Once available in the pool, pipelines can select it to run jobs; publishing it as a package or assigning it as an approval does not make it an agent.

Question 2

A team wants to make a production change safer by verifying that a new application version can start and serve requests before sending normal user traffic to it. Which deployment technique fits this goal?

  1. AUse a blue-green deployment and validate the new environment before switching traffic
  2. BReplace the running application files in place without a health check
  3. CDeploy directly to every instance simultaneously and skip validation
  4. DWait for users to report problems before checking the deployment
Show answerCorrect answer: A

Blue-green deployment runs the new version in a separate environment. The team can validate it before switching traffic, limiting exposure if the version is unhealthy.

Question 3

A team has many independent test cases and wants them to run concurrently, with each test process isolated from the others. Which pipeline strategy can provide this?

  1. ARun the tests as a matrix of jobs with separate configurations
  2. BPut all test cases in one sequential task
  3. CAdd a manual approval before the test stage
  4. DUse a pipeline resource trigger
Show answerCorrect answer: A

A matrix can expand a job into multiple jobs with different configurations, allowing work to run concurrently when sufficient agents are available. A single sequential task does not provide that parallel job structure.

Question 4

A team wants its build to use the same toolchain versions on developer machines and in CI, despite changes to the hosted agent image. Which approach most directly improves that consistency?

  1. AUse a container image that declares the required build tools and versions
  2. BRely on whichever tool versions happen to be preinstalled
  3. CRun the build only on a developer workstation
  4. DIncrease the pipeline's job timeout
Show answerCorrect answer: A

A versioned container image can define the operating environment and toolchain used by the build, reducing variation between runs. The image itself should be maintained and updated deliberately.

Question 5

A build produces a package that must be retained for later use by a deployment pipeline. Which pipeline output is intended to preserve files produced by a run?

  1. AA pipeline artifact
  2. BA pull request comment
  3. CA branch policy
  4. DA service hook subscription
Show answerCorrect answer: A

Pipeline artifacts are files or directories published by a pipeline run so they can be downloaded or consumed by later stages or pipelines. The other options serve collaboration, branch governance, or event-notification purposes.

Question 6

A team wants to limit how long a compromised credential remains usable by a deployment process. Which credential-management practice best addresses this concern?

  1. AUse short-lived credentials that are renewed or issued when needed
  2. BStore a permanent credential in a shared text file
  3. CCopy the credential into every repository
  4. DReuse one credential for all teams and environments
Show answerCorrect answer: A

Short-lived credentials reduce the time window in which an exposed credential can be abused. Where possible, use identity-based authentication and automatic token issuance rather than long-lived shared secrets.

Question 7

A team needs to coordinate deployment of a distributed application so that several independently managed services are updated in a controlled sequence. Which pipeline design feature is most useful for expressing this dependency order?

  1. AExplicit stage dependencies
  2. BA larger agent pool
  3. CA repository fork
  4. DA longer artifact retention period
Show answerCorrect answer: A

Pipeline stages can declare dependencies so that downstream deployment stages run only after prerequisite stages complete successfully. This makes ordering and gating visible in the delivery workflow.

How to use this practice test

The free US Practice Tests practice session draws up to 20 random questions from the available AZ-400 bank. Use the scenarios to check your reasoning about pipelines, Git, artifacts, deployment patterns, and configuration management. Results appear after the session, helping you identify which decisions to revisit.

Preparation tips

  • Trace how a code change moves from a Git branch through review, CI build, artifact publication, and deployment; note where each pipeline stage adds value.
  • Compare pipeline artifacts with variables and variable groups, distinguishing deployable build outputs from reusable configuration and secrets.
  • Work through deployment scenarios by identifying whether the goal is traffic validation, environment promotion, or sequencing updates across dependent services.
  • Review agent connectivity and build reproducibility, including how self-hosted agents receive Azure Pipelines jobs and how controlled toolchain versions reduce image-related variation.
  • For credential scenarios, focus on limiting credential lifetime and exposure, and distinguish secret values from ordinary settings such as a deployment region.
Official sourceOfficial exam page ↗