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 21

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.

Question 201

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A release tag is force-moved to a newer commit after customers have deployed it. 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. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.
  3. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.
  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. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The specific observed issue is: A release tag is force-moved to a newer commit after customers have deployed it. The intervention addresses the git tags and immutable releases exposure, where moving a release tag after deployment breaks auditability, rollback and artifact-to-source correspondence. After the change, acceptance should establish: The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected.

Incorrect Answers

A:

Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos. The git tags and immutable releases prerequisite remains unaddressed.

B:

Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. It changes a different feature than git tags and immutable releases.

D:

Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure. The configuration must instead establish git tags and immutable releases.

Question 202

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A release tag is force-moved to a newer commit after customers have deployed it. 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. A new developer checks out a targeted component with required history while repository transfer and disk use are reduced.
  2. A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change.
  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

C:

Correct. The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected. This observable result is specific to the reported issue: A release tag is force-moved to a newer commit after customers have deployed it. It checks the effectiveness of the proposed correction (Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

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

B:

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 tags and immutable releases.

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 tags and immutable releases outcome.

Question 203

During a regulated production readiness review at a financial technology company, the team documents this issue: A pipeline always builds from a mutable latest tag when asked to restore an old version. 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. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.
  2. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.
  3. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.
  4. Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure.

Explanation

Correct Answer

A:

Correct. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The specific observed issue is: A pipeline always builds from a mutable latest tag when asked to restore an old version. The intervention addresses the git tags and immutable releases exposure, where moving a release tag after deployment breaks auditability, rollback and artifact-to-source correspondence. After the change, acceptance should establish: The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected.

Incorrect Answers

B:

Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. The configuration must instead establish git tags and immutable releases.

C:

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 tags and immutable releases prerequisite remains unaddressed.

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 git tags and immutable releases.

Question 204

During a regulated production readiness review at a financial technology company, the team documents this issue: A pipeline always builds from a mutable latest tag when asked to restore an old version. 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. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.
  2. A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change.
  3. A new developer checks out a targeted component with required history while repository transfer and disk use are reduced.
  4. The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected.

Explanation

Correct Answer

D:

Correct. The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected. This observable result is specific to the reported issue: A pipeline always builds from a mutable latest tag when asked to restore an old version. It checks the effectiveness of the proposed correction (Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.) 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 git tags and immutable releases, not only that test.

B:

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 tags and immutable releases outcome.

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 git tags and immutable releases; this measures a different function.

Question 205

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: Operations cannot correlate a deployed package to the commit that produced it. 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. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.
  2. Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure.
  3. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.
  4. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.

Explanation

Correct Answer

C:

Correct. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The specific observed issue is: Operations cannot correlate a deployed package to the commit that produced it. The intervention addresses the git tags and immutable releases exposure, where moving a release tag after deployment breaks auditability, rollback and artifact-to-source correspondence. After the change, acceptance should establish: The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected.

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. It does not establish the requested git tags and immutable releases outcome.

B:

Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure. The relevant success criterion is git tags and immutable releases; this measures a different function.

D:

Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. Acceptance here depends on observing git tags and immutable releases, not only that test.

Question 206

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: Operations cannot correlate a deployed package to the commit that produced it. 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. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.
  2. A change to a protected deployment file requests the listed code owner and cannot merge until that review passes.
  3. The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected.
  4. A new developer checks out a targeted component with required history while repository transfer and disk use are reduced.

Explanation

Correct Answer

C:

Correct. The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected. This observable result is specific to the reported issue: Operations cannot correlate a deployed package to the commit that produced it. It checks the effectiveness of the proposed correction (Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.) 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. The relevant success criterion is git tags and immutable releases; 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 git tags and immutable releases.

D:

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 tags and immutable releases outcome.

Question 207

During a high-volume service modernization at a multinational retail group, the team documents this issue: A developer publishes an unreviewed tag that triggers a production deployment. 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. 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. 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

B:

Correct. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The specific observed issue is: A developer publishes an unreviewed tag that triggers a production deployment. The intervention addresses the git tags and immutable releases exposure, where moving a release tag after deployment breaks auditability, rollback and artifact-to-source correspondence. After the change, acceptance should establish: The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected.

Incorrect Answers

A:

Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review. That change would not implement git tags and immutable releases.

C:

Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. The git tags and immutable releases prerequisite remains unaddressed.

D:

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 git tags and immutable releases.

Question 208

During a high-volume service modernization at a multinational retail group, the team documents this issue: A developer publishes an unreviewed tag that triggers a production deployment. 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 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. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.

Explanation

Correct Answer

A:

Correct. The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected. This observable result is specific to the reported issue: A developer publishes an unreviewed tag that triggers a production deployment. It checks the effectiveness of the proposed correction (Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

A change to a protected deployment file requests the listed code owner and cannot merge until that review passes. It does not establish the requested git tags and immutable releases outcome.

C:

Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version. The relevant success criterion is git tags and immutable releases; 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 git tags and immutable releases.

Question 209

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. If this issue remains unresolved, what is the PRIMARY DevOps risk?

  1. Resetting shared history disrupts collaborators and can erase the audit trail of a production correction.
  2. Moving a release tag after deployment breaks auditability, rollback and artifact-to-source correspondence.
  3. Excessive write permissions let unintended users alter protected code, policies or release workflows.
  4. Deleting a leaked credential in a new commit does not remove the secret from previous history or revoke its validity.

Explanation

Correct Answer

B:

Correct. Moving a release tag after deployment breaks auditability, rollback and artifact-to-source correspondence. This risk follows from the recorded condition: A release rollback retrieves different source because the tag target was rewritten. The most relevant correction is create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Resetting shared history disrupts collaborators and can erase the audit trail of a production correction. That protection can exist while git tags and immutable releases is still missing.

C:

Excessive write permissions let unintended users alter protected code, policies or release workflows. It does not retain the git tags and immutable releases control over time.

D:

Deleting a leaked credential in a new commit does not remove the secret from previous history or revoke its validity. Recurrence here depends on git tags and immutable releases, not this safeguard.

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.