mcAfee Secure Website
23

Microsoft AZ-400 Bundle

Exam Code: AZ-400

Exam Name Designing and Implementing Microsoft DevOps Solutions

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: DevOps Engineer Expert

AZ-400 Training Materials $44.99

Reliable & Actual Study Materials for AZ-400 Exam Success

The Latest AZ-400 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    AZ-400 Questions & Answers

    398 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    AZ-400 Video Course

    AZ-400 Training Course

    27 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    AZ-400 Study Guide

    784 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

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

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Microsoft Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    398 Questions

    $124.99
    exam =35
  • exam =37
    AZ-400 Video Course

    Training Course

    27 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    784 PDF Pages

    $29.99

Microsoft AZ-400 Practice Test 20

Question 190

During an operational security assessment at a public-sector technology agency, the team documents this issue: A shared source update breaks a consumer without any recorded dependency upgrade. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Select TWO: one corrective action and one test that confirms its effectiveness. (Select TWO.)

  1. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.
  2. Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures.
  3. A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change.
  4. Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos.
  5. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.

Explanation

Correct Answers

B:

Correct corrective action. Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures. The action targets the recorded failure (A shared source update breaks a consumer without any recorded dependency upgrade), and is intended to reduce the corresponding risk: Floating shared code references create nonreproducible builds and unexpected behavioral changes across consuming services.

C:

Correct verification. A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change. The measurement or controlled test provides evidence for the issue (A shared source update breaks a consumer without any recorded dependency upgrade) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants. It is not the complementary risk control for git submodules and shared dependency versioning.

D:

Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos. The git submodules and shared dependency versioning implementation and safeguard are still missing.

E:

Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The two-part git submodules and shared dependency versioning control remains unsatisfied.

Question 191

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A contractor granted organization administrator access only needs to submit pull requests. The affected delivery process supports customer-facing applications and shared delivery pipelines; multiple teams must coordinate changes without losing source-to-release traceability. Which change MOST DIRECTLY addresses the control failure without compromising the delivery process?

  1. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.
  2. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.
  3. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review.
  4. Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure.

Explanation

Correct Answer

C:

Correct. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review. The specific observed issue is: A contractor granted organization administrator access only needs to submit pull requests. The intervention addresses the repository permissions and least privilege exposure, where excessive write permissions let unintended users alter protected code, policies or release workflows. After the change, acceptance should establish: An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.

Incorrect Answers

A:

Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. That change would not implement repository permissions and least privilege.

B:

Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. The configuration must instead establish repository permissions and least privilege.

D:

Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure. It changes a different feature than repository permissions and least privilege.

Question 192

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A contractor granted organization administrator access only needs to submit pull requests. The affected delivery process supports customer-facing applications and shared delivery pipelines; multiple teams must coordinate changes without losing source-to-release traceability. What evidence MOST convincingly verifies the remediation?

  1. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.
  2. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.
  3. A new developer checks out a targeted component with required history while repository transfer and disk use are reduced.
  4. A change to a protected deployment file requests the listed code owner and cannot merge until that review passes.

Explanation

Correct Answer

B:

Correct. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants. This observable result is specific to the reported issue: A contractor granted organization administrator access only needs to submit pull requests. It checks the effectiveness of the proposed correction (Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version. Acceptance here depends on observing repository permissions and least privilege, not only that test.

C:

A new developer checks out a targeted component with required history while repository transfer and disk use are reduced. The relevant success criterion is repository permissions and least privilege; this measures a different function.

D:

A change to a protected deployment file requests the listed code owner and cannot merge until that review passes. That result could pass without demonstrating repository permissions and least privilege.

Question 193

During a regulated production readiness review at a financial technology company, the team documents this issue: A shared team has write access to every sensitive repository regardless of assignment. The affected delivery process supports payment APIs and the deployment process; transaction integrity and change authorization are material controls. Which configuration or workflow change BEST fixes this issue?

  1. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.
  2. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.
  3. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review.
  4. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.

Explanation

Correct Answer

C:

Correct. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review. The specific observed issue is: A shared team has write access to every sensitive repository regardless of assignment. The intervention addresses the repository permissions and least privilege exposure, where excessive write permissions let unintended users alter protected code, policies or release workflows. After the change, acceptance should establish: An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.

Incorrect Answers

A:

Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. The repository permissions and least privilege prerequisite remains unaddressed.

B:

Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. It changes a different feature than repository permissions and least privilege.

D:

Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The configuration must instead establish repository permissions and least privilege.

Question 194

During a regulated production readiness review at a financial technology company, the team documents this issue: A shared team has write access to every sensitive repository regardless of assignment. The affected delivery process supports payment APIs and the deployment process; transaction integrity and change authorization are material controls. Which test outcome should the release team require before closing the issue?

  1. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.
  2. A change to a protected deployment file requests the listed code owner and cannot merge until that review passes.
  3. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.
  4. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.

Explanation

Correct Answer

D:

Correct. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants. This observable result is specific to the reported issue: A shared team has write access to every sensitive repository regardless of assignment. It checks the effectiveness of the proposed correction (Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value. The relevant success criterion is repository permissions and least privilege; this measures a different function.

B:

A change to a protected deployment file requests the listed code owner and cannot merge until that review passes. That result could pass without demonstrating repository permissions and least privilege.

C:

Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version. Acceptance here depends on observing repository permissions and least privilege, not only that test.

Question 195

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: An archived project still permits former contributors to update code. The affected delivery process supports clinical workflow services and their delivery automation; customer impact and service recovery need defensible evidence. What should the DevOps engineer implement to correct the observed gap?

  1. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review.
  2. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.
  3. Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures.
  4. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.

Explanation

Correct Answer

A:

Correct. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review. The specific observed issue is: An archived project still permits former contributors to update code. The intervention addresses the repository permissions and least privilege exposure, where excessive write permissions let unintended users alter protected code, policies or release workflows. After the change, acceptance should establish: An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.

Incorrect Answers

B:

Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. Acceptance here depends on observing repository permissions and least privilege, not only that test.

C:

Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures. It does not establish the requested repository permissions and least privilege outcome.

D:

Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. The relevant success criterion is repository permissions and least privilege; this measures a different function.

Question 196

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: An archived project still permits former contributors to update code. The affected delivery process supports clinical workflow services and their delivery automation; customer impact and service recovery need defensible evidence. What observed result BEST demonstrates the defect has been resolved?

  1. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.
  2. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.
  3. A change to a protected deployment file requests the listed code owner and cannot merge until that review passes.
  4. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.

Explanation

Correct Answer

B:

Correct. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants. This observable result is specific to the reported issue: An archived project still permits former contributors to update code. It checks the effectiveness of the proposed correction (Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history. Acceptance here depends on observing repository permissions and least privilege, not only that test.

C:

A change to a protected deployment file requests the listed code owner and cannot merge until that review passes. The relevant success criterion is repository permissions and least privilege; this measures a different function.

D:

A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value. That result could pass without demonstrating repository permissions and least privilege.

Question 197

During a high-volume service modernization at a multinational retail group, the team documents this issue: A CI bot can change branch protection even though it only needs checkout permission. The affected delivery process supports digital storefronts and backend fulfillment workflows; peak traffic makes regressions expensive to contain. Which proposed change is the most appropriate response to the facts?

  1. Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures.
  2. Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos.
  3. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review.
  4. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.

Explanation

Correct Answer

C:

Correct. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review. The specific observed issue is: A CI bot can change branch protection even though it only needs checkout permission. The intervention addresses the repository permissions and least privilege exposure, where excessive write permissions let unintended users alter protected code, policies or release workflows. After the change, acceptance should establish: An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.

Incorrect Answers

A:

Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures. The repository permissions and least privilege prerequisite remains unaddressed.

B:

Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos. It changes a different feature than repository permissions and least privilege.

D:

Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The configuration must instead establish repository permissions and least privilege.

Question 198

During a high-volume service modernization at a multinational retail group, the team documents this issue: A CI bot can change branch protection even though it only needs checkout permission. The affected delivery process supports digital storefronts and backend fulfillment workflows; peak traffic makes regressions expensive to contain. Which validation would MOST directly prove the intended control operates?

  1. The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected.
  2. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.
  3. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.
  4. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.

Explanation

Correct Answer

D:

Correct. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants. This observable result is specific to the reported issue: A CI bot can change branch protection even though it only needs checkout permission. It checks the effectiveness of the proposed correction (Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected. The relevant success criterion is repository permissions and least privilege; this measures a different function.

B:

A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value. That result could pass without demonstrating repository permissions and least privilege.

C:

A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history. Acceptance here depends on observing repository permissions and least privilege, not only that test.

Question 199

During an operational security assessment at a public-sector technology agency, the team documents this issue: External collaborators can inspect confidential repositories unrelated to their project. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Which risk statement BEST explains the problem described?

  1. Unnecessary object downloads and checkout of unrelated trees prevent productive contribution at enterprise scale.
  2. Floating shared code references create nonreproducible builds and unexpected behavioral changes across consuming services.
  3. Moving a release tag after deployment breaks auditability, rollback and artifact-to-source correspondence.
  4. Excessive write permissions let unintended users alter protected code, policies or release workflows.

Explanation

Correct Answer

D:

Correct. Excessive write permissions let unintended users alter protected code, policies or release workflows. This risk follows from the recorded condition: External collaborators can inspect confidential repositories unrelated to their project. The most relevant correction is assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Unnecessary object downloads and checkout of unrelated trees prevent productive contribution at enterprise scale. That evidence would not isolate repository permissions and least privilege.

B:

Floating shared code references create nonreproducible builds and unexpected behavioral changes across consuming services. The decisive diagnostic evidence must instead cover repository permissions and least privilege.

C:

Moving a release tag after deployment breaks auditability, rollback and artifact-to-source correspondence. It could look normal while repository permissions and least privilege remains unexplained.

Question 200

During an operational security assessment at a public-sector technology agency, the team documents this issue: External collaborators can inspect confidential repositories unrelated to their project. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Which TWO responses form a sound implementation-and-verification pair for this issue? (Select TWO.)

  1. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.
  2. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.
  3. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review.
  4. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.
  5. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.

Explanation

Correct Answers

C:

Correct corrective action. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review. The action targets the recorded failure (External collaborators can inspect confidential repositories unrelated to their project), and is intended to reduce the corresponding risk: Excessive write permissions let unintended users alter protected code, policies or release workflows.

E:

Correct verification. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants. The measurement or controlled test provides evidence for the issue (External collaborators can inspect confidential repositories unrelated to their project) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The paired controls concern repository permissions and least privilege, not that measure.

B:

A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history. The repository permissions and least privilege implementation and safeguard are still missing.

D:

Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. This does not supply the required repository permissions and least privilege action-and-control pair.