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 23

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.

Question 221

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A production token remains usable after developers delete it from the latest YAML file. 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. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review.
  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

D:

Correct. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. The specific observed issue is: A production token remains usable after developers delete it from the latest YAML file. The intervention addresses the credential removal from git history exposure, where deleting a leaked credential in a new commit does not remove the secret from previous history or revoke its validity. After the change, acceptance should establish: A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.

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. The credential removal from git history prerequisite remains unaddressed.

B:

Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review. It changes a different feature than credential removal from git history.

C:

Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. That change would not implement credential removal from git history.

Question 222

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A production token remains usable after developers delete it from the latest YAML file. 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 change to a protected deployment file requests the listed code owner and cannot merge until that review passes.
  2. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.
  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

D:

Correct. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value. This observable result is specific to the reported issue: A production token remains usable after developers delete it from the latest YAML file. It checks the effectiveness of the proposed correction (Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A change to a protected deployment file requests the listed code owner and cannot merge until that review passes. The relevant success criterion is credential removal from git history; this measures a different function.

B:

A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history. That result could pass without demonstrating credential removal from git history.

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 credential removal from git history, not only that test.

Question 223

During a regulated production readiness review at a financial technology company, the team documents this issue: A private key is accidentally included in a GitHub pull-request diff and merged. 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. Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures.
  2. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.
  3. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.
  4. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review.

Explanation

Correct Answer

B:

Correct. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. The specific observed issue is: A private key is accidentally included in a GitHub pull-request diff and merged. The intervention addresses the credential removal from git history exposure, where deleting a leaked credential in a new commit does not remove the secret from previous history or revoke its validity. After the change, acceptance should establish: A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.

Incorrect Answers

A:

Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures. That change would not implement credential removal from git history.

C:

Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The credential removal from git history prerequisite remains unaddressed.

D:

Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review. It changes a different feature than credential removal from git history.

Question 224

During a regulated production readiness review at a financial technology company, the team documents this issue: A private key is accidentally included in a GitHub pull-request diff and merged. 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. The production artifact identifies an approved immutable tag and an unauthorized attempt to retarget it is rejected.
  2. A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.
  3. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.
  4. A change to a protected deployment file requests the listed code owner and cannot merge until that review passes.

Explanation

Correct Answer

C:

Correct. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value. This observable result is specific to the reported issue: A private key is accidentally included in a GitHub pull-request diff and merged. It checks the effectiveness of the proposed correction (Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.) 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. Acceptance here depends on observing credential removal from git history, not only that test.

B:

A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history. It does not establish the requested credential removal from git history outcome.

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 credential removal from git history.

Question 225

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A repository history rewrite is completed but fork owners retain the leaked secret. 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 partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos.
  2. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review.
  3. Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures.
  4. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.

Explanation

Correct Answer

D:

Correct. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. The specific observed issue is: A repository history rewrite is completed but fork owners retain the leaked secret. The intervention addresses the credential removal from git history exposure, where deleting a leaked credential in a new commit does not remove the secret from previous history or revoke its validity. After the change, acceptance should establish: A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.

Incorrect Answers

A:

Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos. It does not establish the requested credential removal from git history outcome.

B:

Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review. The relevant success criterion is credential removal from git history; this measures a different function.

C:

Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures. That result could pass without demonstrating credential removal from git history.

Question 226

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A repository history rewrite is completed but fork owners retain the leaked secret. 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. 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

B:

Correct. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value. This observable result is specific to the reported issue: A repository history rewrite is completed but fork owners retain the leaked secret. It checks the effectiveness of the proposed correction (Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.) 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. The relevant success criterion is credential removal from git history; 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 credential removal from git history, not only that test.

D:

A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history. It does not establish the requested credential removal from git history outcome.

Question 227

During a high-volume service modernization at a multinational retail group, the team documents this issue: A CI access key is removed from source without changing the cloud permission credential. 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. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.
  3. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.
  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. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. The specific observed issue is: A CI access key is removed from source without changing the cloud permission credential. The intervention addresses the credential removal from git history exposure, where deleting a leaked credential in a new commit does not remove the secret from previous history or revoke its validity. After the change, acceptance should establish: A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.

Incorrect Answers

A:

Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures. That change would not implement credential removal from git history.

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 configuration must instead establish credential removal from git history.

D:

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 credential removal from git history.

Question 228

During a high-volume service modernization at a multinational retail group, the team documents this issue: A CI access key is removed from source without changing the cloud permission credential. 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. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.
  3. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.
  4. A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change.

Explanation

Correct Answer

C:

Correct. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value. This observable result is specific to the reported issue: A CI access key is removed from source without changing the cloud permission credential. It checks the effectiveness of the proposed correction (Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.) 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. Acceptance here depends on observing credential removal from git history, not only that test.

B:

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 credential removal from git history outcome.

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 credential removal from git history.

Question 229

During an operational security assessment at a public-sector technology agency, the team documents this issue: A team assumes deleting a tag eliminates every historical copy of a committed password. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Why is the current implementation not a reliable control?

  1. Unnecessary object downloads and checkout of unrelated trees prevent productive contribution at enterprise scale.
  2. Large binary blobs inflate every clone and make source-control operations slow and expensive.
  3. Floating shared code references create nonreproducible builds and unexpected behavioral changes across consuming services.
  4. Deleting a leaked credential in a new commit does not remove the secret from previous history or revoke its validity.

Explanation

Correct Answer

D:

Correct. Deleting a leaked credential in a new commit does not remove the secret from previous history or revoke its validity. This risk follows from the recorded condition: A team assumes deleting a tag eliminates every historical copy of a committed password. The most relevant correction is revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. 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. The credential removal from git history prerequisite remains unaddressed.

B:

Large binary blobs inflate every clone and make source-control operations slow and expensive. It changes a different feature than credential removal from git history.

C:

Floating shared code references create nonreproducible builds and unexpected behavioral changes across consuming services. That change would not implement credential removal from git history.

Question 230

During an operational security assessment at a public-sector technology agency, the team documents this issue: A team assumes deleting a tag eliminates every historical copy of a committed password. 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. An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.
  2. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.
  3. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.
  4. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.
  5. Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures.

Explanation

Correct Answers

B:

Correct corrective action. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. The action targets the recorded failure (A team assumes deleting a tag eliminates every historical copy of a committed password), and is intended to reduce the corresponding risk: Deleting a leaked credential in a new commit does not remove the secret from previous history or revoke its validity.

C:

Correct verification. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value. The measurement or controlled test provides evidence for the issue (A team assumes deleting a tag eliminates every historical copy of a committed password) 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 credential removal from git history.

D:

Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. The credential removal from git history implementation and safeguard are still missing.

E:

Use a controlled repository dependency strategy with pinned submodule revisions or versioned packages and documented update procedures. The two-part credential removal from git history control remains unsatisfied.