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 22

Question 210

During an operational security assessment at a public-sector technology agency, the team documents this issue: A release rollback retrieves different source because the tag target was rewritten. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Choose TWO statements that provide both the appropriate correction and a meaningful test of its success. (Select TWO.)

  1. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.
  2. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.
  3. A change to a protected deployment file requests the listed code owner and cannot merge until that review passes.
  4. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.
  5. The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected.

Explanation

Correct Answers

D:

Correct corrective action. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The action targets the recorded failure (A release rollback retrieves different source because the tag target was rewritten), and is intended to reduce the corresponding risk: Moving a release tag after deployment breaks auditability, rollback and artifact-to-source correspondence.

E:

Correct verification. The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected. The measurement or controlled test provides evidence for the issue (A release rollback retrieves different source because the tag target was rewritten) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. It is not the complementary risk control for git tags and immutable releases.

B:

Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. This does not supply the required git tags and immutable releases action-and-control pair.

C:

A change to a protected deployment file requests the listed code owner and cannot merge until that review passes. The paired controls concern git tags and immutable releases, not that measure.

Question 211

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A production defect is addressed with a force-push that removes public commits. 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 partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos.
  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. Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures.

Explanation

Correct Answer

B:

Correct. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. The specific observed issue is: A production defect is addressed with a force-push that removes public commits. The intervention addresses the git revert versus reset incident recovery exposure, where resetting shared history disrupts collaborators and can erase the audit trail of a production correction. After the change, acceptance should establish: A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.

Incorrect Answers

A:

Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos. That change would not implement git revert versus reset incident recovery.

C:

Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review. The git revert versus reset incident recovery prerequisite remains unaddressed.

D:

Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures. It changes a different feature than git revert versus reset incident recovery.

Question 212

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A production defect is addressed with a force-push that removes public commits. 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. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.
  2. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.
  3. The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected.
  4. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.

Explanation

Correct Answer

D:

Correct. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history. This observable result is specific to the reported issue: A production defect is addressed with a force-push that removes public commits. It checks the effectiveness of the proposed correction (Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants. Acceptance here depends on observing git revert versus reset incident recovery, not only that test.

B:

A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value. It does not establish the requested git revert versus reset incident recovery outcome.

C:

The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected. The relevant success criterion is git revert versus reset incident recovery; this measures a different function.

Question 213

During a regulated production readiness review at a financial technology company, the team documents this issue: An engineer uses reset --hard on a shared branch after other teams based work on it. 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. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.
  2. Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures.
  3. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.
  4. Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos.

Explanation

Correct Answer

C:

Correct. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. The specific observed issue is: An engineer uses reset --hard on a shared branch after other teams based work on it. The intervention addresses the git revert versus reset incident recovery exposure, where resetting shared history disrupts collaborators and can erase the audit trail of a production correction. After the change, acceptance should establish: A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.

Incorrect Answers

A:

Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. The git revert versus reset incident recovery prerequisite remains unaddressed.

B:

Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures. It changes a different feature than git revert versus reset incident recovery.

D:

Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos. The configuration must instead establish git revert versus reset incident recovery.

Question 214

During a regulated production readiness review at a financial technology company, the team documents this issue: An engineer uses reset --hard on a shared branch after other teams based work on it. 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 release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change.
  2. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.
  3. The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected.
  4. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.

Explanation

Correct Answer

B:

Correct. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history. This observable result is specific to the reported issue: An engineer uses reset --hard on a shared branch after other teams based work on it. It checks the effectiveness of the proposed correction (Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change. The relevant success criterion is git revert versus reset incident recovery; this measures a different function.

C:

The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected. Acceptance here depends on observing git revert versus reset incident recovery, not only that test.

D:

An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants. It does not establish the requested git revert versus reset incident recovery outcome.

Question 215

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A release manager needs to undo one isolated merged PR without discarding newer changes. 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. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.
  2. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.
  3. Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure.
  4. Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos.

Explanation

Correct Answer

B:

Correct. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. The specific observed issue is: A release manager needs to undo one isolated merged PR without discarding newer changes. The intervention addresses the git revert versus reset incident recovery exposure, where resetting shared history disrupts collaborators and can erase the audit trail of a production correction. After the change, acceptance should establish: A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.

Incorrect Answers

A:

Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. That result could pass without demonstrating git revert versus reset incident recovery.

C:

Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure. It does not establish the requested git revert versus reset incident recovery outcome.

D:

Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos. The relevant success criterion is git revert versus reset incident recovery; this measures a different function.

Question 216

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A release manager needs to undo one isolated merged PR without discarding newer changes. 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. A new developer checks out a targeted component with required history while repository transfer and disk use are reduced.
  3. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.
  4. A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change.

Explanation

Correct Answer

A:

Correct. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history. This observable result is specific to the reported issue: A release manager needs to undo one isolated merged PR without discarding newer changes. It checks the effectiveness of the proposed correction (Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

A new developer checks out a targeted component with required history while repository transfer and disk use are reduced. It does not establish the requested git revert versus reset incident recovery outcome.

C:

An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants. The relevant success criterion is git revert versus reset incident recovery; this measures a different function.

D:

A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change. That result could pass without demonstrating git revert versus reset incident recovery.

Question 217

During a high-volume service modernization at a multinational retail group, the team documents this issue: A production fix is applied by deleting commits from the repository's visible history. 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. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.
  2. Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure.
  3. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.
  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

D:

Correct. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. The specific observed issue is: A production fix is applied by deleting commits from the repository's visible history. The intervention addresses the git revert versus reset incident recovery exposure, where resetting shared history disrupts collaborators and can erase the audit trail of a production correction. After the change, acceptance should establish: A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.

Incorrect Answers

A:

Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. The git revert versus reset incident recovery prerequisite remains unaddressed.

B:

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 git revert versus reset incident recovery.

C:

Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. That change would not implement git revert versus reset incident recovery.

Question 218

During a high-volume service modernization at a multinational retail group, the team documents this issue: A production fix is applied by deleting commits from the repository's visible history. 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. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.
  2. A new developer checks out a targeted component with required history while repository transfer and disk use are reduced.
  3. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.
  4. A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change.

Explanation

Correct Answer

A:

Correct. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history. This observable result is specific to the reported issue: A production fix is applied by deleting commits from the repository's visible history. It checks the effectiveness of the proposed correction (Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

A new developer checks out a targeted component with required history while repository transfer and disk use are reduced. That result could pass without demonstrating git revert versus reset incident recovery.

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 git revert versus reset incident recovery, not only that test.

D:

A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change. It does not establish the requested git revert versus reset incident recovery outcome.

Question 219

During an operational security assessment at a public-sector technology agency, the team documents this issue: An audit requires a clear record of who reversed a problematic change. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Which consequence is MOST directly supported by these facts?

  1. Large binary blobs inflate every clone and make source-control operations slow and expensive.
  2. Deleting a leaked credential in a new commit does not remove the secret from previous history or revoke its validity.
  3. Resetting shared history disrupts collaborators and can erase the audit trail of a production correction.
  4. Changes to critical infrastructure or security code can pass generic peer review without an accountable specialist.

Explanation

Correct Answer

C:

Correct. Resetting shared history disrupts collaborators and can erase the audit trail of a production correction. This risk follows from the recorded condition: An audit requires a clear record of who reversed a problematic change. The most relevant correction is use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Large binary blobs inflate every clone and make source-control operations slow and expensive. That change would not implement git revert versus reset incident recovery.

B:

Deleting a leaked credential in a new commit does not remove the secret from previous history or revoke its validity. The configuration must instead establish git revert versus reset incident recovery.

D:

Changes to critical infrastructure or security code can pass generic peer review without an accountable specialist. It changes a different feature than git revert versus reset incident recovery.

Question 220

During an operational security assessment at a public-sector technology agency, the team documents this issue: An audit requires a clear record of who reversed a problematic change. 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. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.
  2. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.
  3. Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures.
  4. A new developer checks out a targeted component with required history while repository transfer and disk use are reduced.
  5. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.

Explanation

Correct Answers

A:

Correct corrective action. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. The action targets the recorded failure (An audit requires a clear record of who reversed a problematic change), and is intended to reduce the corresponding risk: Resetting shared history disrupts collaborators and can erase the audit trail of a production correction.

E:

Correct verification. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history. The measurement or controlled test provides evidence for the issue (An audit requires a clear record of who reversed a problematic change) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

B:

Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. The git revert versus reset incident recovery implementation and safeguard are still missing.

C:

Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures. It is not the complementary risk control for git revert versus reset incident recovery.

D:

A new developer checks out a targeted component with required history while repository transfer and disk use are reduced. This does not supply the required git revert versus reset incident recovery action-and-control pair.