Pass Microsoft DevOps AZ-400 Exam in First Attempt Easily
Real Microsoft DevOps AZ-400 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts
3 products

You save $69.98

AZ-400 Premium Bundle

  • Premium File 398 Questions & Answers
  • Last Update: Nov 11, 2026
  • Training Course 27 Lectures
  • Study Guide 784 Pages
$79.99 $149.97

Purchase Individually

  • Premium File

    398 Questions & Answers
    Last Update: Nov 11, 2026

    $76.99
    $69.99
  • Training Course

    27 Lectures

    $43.99
    $39.99
  • Study Guide

    784 Pages

    $43.99
    $39.99

Designing and Implementing Microsoft DevOps Solutions AZ-400 Practice Test 9

Question 80

A regulated platform wants pipelines to reject unapproved task types even when repository contributors edit their YAML definitions.

Which explanation best supports the needed implementation decision?

  1. Pipelines may execute independent jobs in parallel, so dependent stages must be linked to upstream successful work.
  2. Correct cache keys improve speed while preventing incompatible or stale cached outputs from silently changing builds.
  3. Environment checks are managed on the resource rather than inside the pipeline YAML, resisting bypass by repository edits.
  4. An extends template can constrain allowed pipeline steps, while checks on protected resources prevent easy removal of the requirement.

Explanation

Correct Answer

D:

An extends template can constrain allowed pipeline steps, while checks on protected resources prevent easy removal of the requirement. The appropriate response is to use a governed YAML extends template and required-template checks for enforceable pipeline structure. The expected evidence is that a pipeline attempting to omit the approved template or run a prohibited task is rejected before a protected release.

Incorrect Answers

A:

That explanation is about YAML multi-stage dependency: Pipelines may execute independent jobs in parallel, so dependent stages must be linked to upstream successful work.

B:

This describes the mechanism for Build cache with correctness: Correct cache keys improve speed while preventing incompatible or stale cached outputs from silently changing builds.

C:

This reasoning pertains to YAML environments approvals: Environment checks are managed on the resource rather than inside the pipeline YAML, resisting bypass by repository edits.

Question 81

A repository accepts accidentally pasted personal access tokens and the team discovers them only after public release.

Which explanation best supports the needed implementation decision?

  1. Secret scanning detects known credential patterns before promotion and alerts owners to rotate any exposed credential.
  2. Integrated DevOps security posture helps central teams connect source risk with affected development assets and cloud governance.
  3. Dependency scanning connects known advisories to manifest and lockfile versions and can propose reviewed updates.
  4. Azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments.

Explanation

Correct Answer

A:

Secret scanning detects known credential patterns before promotion and alerts owners to rotate any exposed credential. The appropriate response is to enable automated secret scanning and push or pull-request protection with clear remediation for exposed values. The expected evidence is that the leak blocks or flags the proposed change and the exposed credential is revoked before a safe replacement merges.

Incorrect Answers

B:

This reasoning pertains to GitHub Advanced Security and Defender: Integrated DevOps security posture helps central teams connect source risk with affected development assets and cloud governance.

C:

That explanation is about Dependabot dependency alerts: Dependency scanning connects known advisories to manifest and lockfile versions and can propose reviewed updates.

D:

This describes the mechanism for Managed identity versus service principal: Azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments.

Question 82

A government project keeps process diagrams in private slide files that fall out of sync with its Git repository.

Which risk most directly follows if the team leaves this problem unresolved?

  1. Critical failures remain invisible, or noisy unrestricted messages cause sensitive information disclosure.
  2. Outdated instructions can cause an operator to promote components in the wrong order.
  3. An apparent improvement in support productivity can conceal longer and more damaging outages.
  4. Users may adopt incompatible clients or support teams may misdiagnose expected release behavior.

Explanation

Correct Answer

B:

Outdated instructions can cause an operator to promote components in the wrong order. The failure follows from the described gap because version-controlled documentation can evolve through ordinary review and makes dependencies inspectable by engineers and operators. Mitigate it by choosing to maintain reviewed Markdown documentation and Mermaid diagrams alongside the service delivery workflow.

Incorrect Answers

A:

That is a credible failure of Teams pipeline notifications: Purposeful notifications give stakeholders timely actionable status while original pipeline permissions continue to protect detail. The present scenario instead leaves the wiki and process diagrams requirement unresolved, which creates this more direct risk: outdated instructions can cause an operator to promote components in the wrong order.

C:

That consequence is characteristic of Mean time to restore: Recovery duration captures actual service impact better than activity counts and can guide investment in incident response. The present scenario instead leaves the wiki and process diagrams requirement unresolved, which creates this more direct risk: outdated instructions can cause an operator to promote components in the wrong order.

D:

That is a credible failure of Versioned release notes: Releasing documented change history helps consumers and support understand compatible features, fixes and known constraints. The present scenario instead leaves the wiki and process diagrams requirement unresolved, which creates this more direct risk: outdated instructions can cause an operator to promote components in the wrong order.

Question 83

An enterprise monorepo causes everyday Git status operations to scan many irrelevant directories for each developer.

Which observation most directly confirms the required DevOps control is effective?

  1. Developers can clone code efficiently and retrieve versioned large binaries through an authorized LFS endpoint.
  2. A modification to an owned security path requests and obtains the designated team's approval before merge.
  3. Representative developers complete status, fetch and build workflows with acceptable latency while retaining needed source access.
  4. The exposed token no longer authenticates and approved history-remediation checks find no accessible sensitive object.

Explanation

Correct Answer

C:

Representative developers complete status, fetch and build workflows with acceptable latency while retaining needed source access. This shows that the control was implemented as intended: evaluate Scalar and sparse or partial checkout strategies for large-repository development. It matters because optimized Git enlistments and reduced working-tree scope can make monorepo operations practical without splitting required source history.

Incorrect Answers

A:

This observation would support Git LFS for binaries, where the relevant control is use Git LFS for large binaries with explicit patterns while leaving source code in ordinary Git storage.

B:

Such evidence would establish Code owner review, where the relevant control is define CODEOWNERS and require appropriate code-owner approval for protected paths.

D:

This observation would support Remove leaked credential from Git, where the relevant control is revoke and rotate the exposed credential immediately, remove sensitive history using an approved rewrite and coordinate downstream cleanup.

Question 84

A team wants repeatable builds but agents have accumulated different compiler versions and undocumented fixes.

Which risk most directly follows if the team leaves this problem unresolved?

  1. An overly broad cache key can introduce wrong dependencies or stale build results.
  2. The pipeline reports success while customers experience degraded application behavior.
  3. Blind reruns can compound partial changes and damage application data or environment state.
  4. Unpatched or inconsistent agents cause both supply-chain risk and irreproducible pipeline outcomes.

Explanation

Correct Answer

D:

Unpatched or inconsistent agents cause both supply-chain risk and irreproducible pipeline outcomes. The failure follows from the described gap because controlled immutable agent baselines reduce drift and known vulnerabilities while retaining build reproducibility. Mitigate it by choosing to manage versioned hardened runner images with patch schedules and automated smoke validation.

Incorrect Answers

A:

That consequence is characteristic of Build cache with correctness: Correct cache keys improve speed while preventing incompatible or stale cached outputs from silently changing builds. The present scenario instead leaves the agent image maintenance requirement unresolved, which creates this more direct risk: unpatched or inconsistent agents cause both supply-chain risk and irreproducible pipeline outcomes.

B:

That is a credible failure of Rollback health criteria: Successful command execution is not proof of healthy user traffic; objective health checks guide safe progression. The present scenario instead leaves the agent image maintenance requirement unresolved, which creates this more direct risk: unpatched or inconsistent agents cause both supply-chain risk and irreproducible pipeline outcomes.

C:

This risk is associated with Pipeline retry boundaries: Retries are reliable only when repeated execution has a defined effect and partial failures are detectable. The present scenario instead leaves the agent image maintenance requirement unresolved, which creates this more direct risk: unpatched or inconsistent agents cause both supply-chain risk and irreproducible pipeline outcomes.

Question 85

A developer commits a cloud access key and branch policies permit merging because unit tests pass.

What is the most appropriate action for this DevOps team?

  1. Enable automated secret scanning and push or pull-request protection with clear remediation for exposed values.
  2. Scan container images and dependencies before promotion, enforce risk-based gates and retain image provenance.
  3. Use a scoped workload identity federation service connection or GitHub OIDC trust instead of storing long-lived cloud secrets.
  4. Enable Dependabot alerts and security updates, then validate proposed fixes in CI with clear ownership.

Explanation

Correct Answer

A:

Enable automated secret scanning and push or pull-request protection with clear remediation for exposed values. Secret scanning detects known credential patterns before promotion and alerts owners to rotate any exposed credential. A useful check is that the leak blocks or flags the proposed change and the exposed credential is revoked before a safe replacement merges.

Incorrect Answers

B:

That intervention fits Container image scanning: Container scanning examines packaged runtime components that may not appear in application source analysis.

C:

This is designed for Workload identity federation: OIDC-based federation exchanges trusted workflow identity assertions for short-lived cloud access, reducing static credential exposure.

D:

This would instead address Dependabot dependency alerts: Dependency scanning connects known advisories to manifest and lockfile versions and can propose reviewed updates.

Question 86

An application running on an Azure VM needs to read a secret but the team plans to embed a service-principal password in code.

Which explanation best supports the needed implementation decision?

  1. Dependency scanning connects known advisories to manifest and lockfile versions and can propose reviewed updates.
  2. Azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments.
  3. Service connections are privileged deployment identities, so resource RBAC and use restrictions should match actual blast radius.
  4. OIDC-based federation exchanges trusted workflow identity assertions for short-lived cloud access, reducing static credential exposure.

Explanation

Correct Answer

B:

Azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments. The appropriate response is to use a managed identity for the Azure-hosted workload and assign minimal target-resource RBAC roles. The expected evidence is that the workload obtains a token and reaches only the authorized resource without a credential in source or logs.

Incorrect Answers

A:

That explanation is about Dependabot dependency alerts: Dependency scanning connects known advisories to manifest and lockfile versions and can propose reviewed updates.

C:

This reasoning pertains to Service connection scope: Service connections are privileged deployment identities, so resource RBAC and use restrictions should match actual blast radius.

D:

That explanation is about Workload identity federation: OIDC-based federation exchanges trusted workflow identity assertions for short-lived cloud access, reducing static credential exposure.

Question 87

An Azure Pipeline deploys to Azure using a service-principal client secret that operators must renew manually each quarter.

Which explanation best supports the needed implementation decision?

  1. GitHub Apps separate automation identity from a human account and can grant repository-scoped, revocable access.
  2. Secret scanning detects known credential patterns before promotion and alerts owners to rotate any exposed credential.
  3. OIDC-based federation exchanges trusted workflow identity assertions for short-lived cloud access, reducing static credential exposure.
  4. Access levels govern available features while permissions and security groups govern allowed actions; both matter for least privilege.

Explanation

Correct Answer

C:

OIDC-based federation exchanges trusted workflow identity assertions for short-lived cloud access, reducing static credential exposure. The appropriate response is to use a scoped workload identity federation service connection or GitHub OIDC trust instead of storing long-lived cloud secrets. The expected evidence is that the approved job obtains only scoped Azure access without any stored client secret and untrusted branches cannot impersonate it.

Incorrect Answers

A:

This describes the mechanism for GitHub App scope: GitHub Apps separate automation identity from a human account and can grant repository-scoped, revocable access.

B:

This reasoning pertains to Secret scanning in pull requests: Secret scanning detects known credential patterns before promotion and alerts owners to rotate any exposed credential.

D:

This describes the mechanism for Azure DevOps least privilege: Access levels govern available features while permissions and security groups govern allowed actions; both matter for least privilege.

Question 88

A build pipeline deploys to one resource group but its Azure service connection has contributor rights across the entire subscription.

Which observation most directly confirms the required DevOps control is effective?

  1. The workload obtains a token and reaches only the authorized resource without a credential in source or logs.
  2. A seeded high-severity injection pattern creates a finding and a protected release cannot proceed until disposition.
  3. The bot updates only installed repositories with the approved permissions and cannot read unrelated projects.
  4. An authorized test pipeline can deploy to its resource group but cannot alter other environments.

Explanation

Correct Answer

D:

An authorized test pipeline can deploy to its resource group but cannot alter other environments. This shows that the control was implemented as intended: scope service connection roles and approvals to the smallest necessary Azure resources and pipeline consumers. It matters because service connections are privileged deployment identities, so resource RBAC and use restrictions should match actual blast radius.

Incorrect Answers

A:

That result would verify Managed identity versus service principal, where the relevant control is use a managed identity for the Azure-hosted workload and assign minimal target-resource RBAC roles.

B:

This observation would support CodeQL static analysis, where the relevant control is run CodeQL analysis appropriate to the code language and act on high-severity findings before release.

C:

Such evidence would establish GitHub App scope, where the relevant control is use a GitHub App installation with narrowly requested repository permissions and short-lived installation tokens.

Question 89

A developer group wants actionable deployment completion summaries in Microsoft Teams without disclosing build secrets.

Which observation most directly confirms the required DevOps control is effective?

  1. The correct Teams channel receives failure and deployment notifications with working links and no exposed credentials.
  2. Incident records contain onset and verified recovery times and the restoration trend is shown across comparable events.
  3. Each deployed version has accurate notes listing the associated changes, breaking behaviors and support actions.
  4. A changed workflow updates its checked-in documentation and readers can follow the current deployment and rollback path.

Explanation

Correct Answer

A:

The correct Teams channel receives failure and deployment notifications with working links and no exposed credentials. This shows that the control was implemented as intended: integrate filtered pipeline status notifications with Microsoft Teams and link back to the secured run records. It matters because purposeful notifications give stakeholders timely actionable status while original pipeline permissions continue to protect detail.

Incorrect Answers

B:

Such evidence would establish Mean time to restore, where the relevant control is measure time to restore service from incident impact to verified recovery and trend it alongside incident frequency.

C:

That result would verify Versioned release notes, where the relevant control is generate versioned release notes from linked work items, pull requests and approved change records.

D:

This observation would support Wiki and process diagrams, where the relevant control is maintain reviewed Markdown documentation and Mermaid diagrams alongside the service delivery workflow.

Question 90

A critical production defect needs a patch today, but the normal release train includes unrelated unverified features.

What is the most appropriate action for this DevOps team?

  1. Use backward-compatible expand-and-contract schema changes before removing old fields.
  2. Create a controlled hotfix path from the production release, validate the targeted change and reconcile it into main.
  3. Use a documented CalVer scheme for chronological releases while separately tracking backward-compatibility obligations.
  4. Gate deployment completion on service-health metrics and invoke rollback when agreed thresholds fail.

Explanation

Correct Answer

B:

Create a controlled hotfix path from the production release, validate the targeted change and reconcile it into main. A distinct expedited path preserves essential test and approval controls while avoiding unrelated functionality. A useful check is that only the reviewed fix reaches the supported deployment and its commit is incorporated into ongoing development.

Incorrect Answers

A:

This is designed for Database expand-contract migration: The expand phase adds compatible schema, data migration occurs safely, and contraction follows after consumers have transitioned.

C:

That intervention fits Date-based versioning: Calendar-based versions express release timing, but do not automatically convey semantic API compatibility.

D:

This is designed for Rollback health criteria: Successful command execution is not proof of healthy user traffic; objective health checks guide safe progression.

Designing and Implementing Microsoft DevOps Solutions (AZ-400) Practice Tests

Purchase Individually

  • Premium File

    398 Questions & Answers
    Last Update: Nov 11, 2026

    $76.99
    $69.99
  • Training Course

    27 Lectures

    $43.99
    $39.99
  • Study Guide

    784 Pages

    $43.99
    $39.99

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports