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 89

Question 880

During an operational security assessment at a public-sector technology agency, the team documents this issue: An automated dependency update merges directly without the project's required test checks. 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. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.
  2. Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.
  3. A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph.
  4. A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process.
  5. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.

Explanation

Correct Answers

B:

Correct corrective action. Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. The action targets the recorded failure (An automated dependency update merges directly without the project's required test checks), and is intended to reduce the corresponding risk: Transitive vulnerable dependencies remain unnoticed when projects only scan their own application source.

C:

Correct verification. A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph. The measurement or controlled test provides evidence for the issue (An automated dependency update merges directly without the project's required test checks) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. The paired controls concern GitHub dependabot vulnerability and version alerts, not that measure.

D:

A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process. This does not supply the required GitHub dependabot vulnerability and version alerts action-and-control pair.

E:

Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. The two-part GitHub dependabot vulnerability and version alerts control remains unsatisfied.

Question 881

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A live cloud token is committed and the next pipeline run merely deletes it from the latest 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. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.
  2. Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.
  3. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.
  4. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.

Explanation

Correct Answer

D:

Correct. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. The specific observed issue is: A live cloud token is committed and the next pipeline run merely deletes it from the latest file. The intervention addresses the github secret scanning and push protection exposure, where detecting a secret after publication is insufficient while the credential remains usable in history or forks. After the change, acceptance should establish: An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access.

Incorrect Answers

A:

Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. The GitHub secret scanning and push protection prerequisite remains unaddressed.

B:

Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. It changes a different feature than GitHub secret scanning and push protection.

C:

Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. That change would not implement GitHub secret scanning and push protection.

Question 882

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A live cloud token is committed and the next pipeline run merely deletes it from the latest 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. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access.
  2. A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph.
  3. A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process.
  4. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.

Explanation

Correct Answer

A:

Correct. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access. This observable result is specific to the reported issue: A live cloud token is committed and the next pipeline run merely deletes it from the latest file. It checks the effectiveness of the proposed correction (Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph. That result could pass without demonstrating GitHub secret scanning and push protection.

C:

A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process. Acceptance here depends on observing GitHub secret scanning and push protection, not only that test.

D:

A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. It does not establish the requested GitHub secret scanning and push protection outcome.

Question 883

During a regulated production readiness review at a financial technology company, the team documents this issue: A repository disables secret push protection because developers find warnings inconvenient. 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. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.
  2. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.
  3. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.
  4. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.

Explanation

Correct Answer

D:

Correct. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. The specific observed issue is: A repository disables secret push protection because developers find warnings inconvenient. The intervention addresses the github secret scanning and push protection exposure, where detecting a secret after publication is insufficient while the credential remains usable in history or forks. After the change, acceptance should establish: An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access.

Incorrect Answers

A:

Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. That change would not implement GitHub secret scanning and push protection.

B:

Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The configuration must instead establish GitHub secret scanning and push protection.

C:

Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. The GitHub secret scanning and push protection prerequisite remains unaddressed.

Question 884

During a regulated production readiness review at a financial technology company, the team documents this issue: A repository disables secret push protection because developers find warnings inconvenient. 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 deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.
  2. A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process.
  3. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access.
  4. A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph.

Explanation

Correct Answer

C:

Correct. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access. This observable result is specific to the reported issue: A repository disables secret push protection because developers find warnings inconvenient. It checks the effectiveness of the proposed correction (Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity. Acceptance here depends on observing GitHub secret scanning and push protection, not only that test.

B:

A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process. It does not establish the requested GitHub secret scanning and push protection outcome.

D:

A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph. That result could pass without demonstrating GitHub secret scanning and push protection.

Question 885

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A PR includes a private key but no reviewers are notified before merge. 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. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.
  2. Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.
  3. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.
  4. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.

Explanation

Correct Answer

C:

Correct. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. The specific observed issue is: A PR includes a private key but no reviewers are notified before merge. The intervention addresses the github secret scanning and push protection exposure, where detecting a secret after publication is insufficient while the credential remains usable in history or forks. After the change, acceptance should establish: An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access.

Incorrect Answers

A:

Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. It does not establish the requested GitHub secret scanning and push protection outcome.

B:

Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. The relevant success criterion is GitHub secret scanning and push protection; this measures a different function.

D:

Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. Acceptance here depends on observing GitHub secret scanning and push protection, not only that test.

Question 886

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A PR includes a private key but no reviewers are notified before merge. 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 known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph.
  2. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access.
  3. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.
  4. A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.

Explanation

Correct Answer

B:

Correct. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access. This observable result is specific to the reported issue: A PR includes a private key but no reviewers are notified before merge. It checks the effectiveness of the proposed correction (Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph. The relevant success criterion is GitHub secret scanning and push protection; this measures a different function.

C:

A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. Acceptance here depends on observing GitHub secret scanning and push protection, not only that test.

D:

A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity. It does not establish the requested GitHub secret scanning and push protection outcome.

Question 887

During a high-volume service modernization at a multinational retail group, the team documents this issue: An emergency bypass for a known secret exposure remains undocumented and unreviewed. 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. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.
  2. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.
  3. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.
  4. Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.

Explanation

Correct Answer

B:

Correct. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. The specific observed issue is: An emergency bypass for a known secret exposure remains undocumented and unreviewed. The intervention addresses the github secret scanning and push protection exposure, where detecting a secret after publication is insufficient while the credential remains usable in history or forks. After the change, acceptance should establish: An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access.

Incorrect Answers

A:

Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. That change would not implement GitHub secret scanning and push protection.

C:

Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The GitHub secret scanning and push protection prerequisite remains unaddressed.

D:

Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. It changes a different feature than GitHub secret scanning and push protection.

Question 888

During a high-volume service modernization at a multinational retail group, the team documents this issue: An emergency bypass for a known secret exposure remains undocumented and unreviewed. 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. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access.
  2. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.
  3. A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.
  4. A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process.

Explanation

Correct Answer

A:

Correct. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access. This observable result is specific to the reported issue: An emergency bypass for a known secret exposure remains undocumented and unreviewed. It checks the effectiveness of the proposed correction (Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. It does not establish the requested GitHub secret scanning and push protection outcome.

C:

A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity. The relevant success criterion is GitHub secret scanning and push protection; this measures a different function.

D:

A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process. That result could pass without demonstrating GitHub secret scanning and push protection.

Question 889

During an operational security assessment at a public-sector technology agency, the team documents this issue: A credential rotation is declared complete while the leaked old token can still authenticate. 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. Security-sensitive code paths may contain vulnerabilities not found by functional tests when scanning is absent or incomplete.
  2. Disconnected or partial code-to-cloud coverage can hide high-risk vulnerabilities and mislead central governance.
  3. A container image may ship known vulnerable packages even when the application itself passes all functional tests.
  4. Detecting a secret after publication is insufficient while the credential remains usable in history or forks.

Explanation

Correct Answer

D:

Correct. Detecting a secret after publication is insufficient while the credential remains usable in history or forks. This risk follows from the recorded condition: A credential rotation is declared complete while the leaked old token can still authenticate. The most relevant correction is use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Security-sensitive code paths may contain vulnerabilities not found by functional tests when scanning is absent or incomplete. That protection can exist while GitHub secret scanning and push protection is still missing.

B:

Disconnected or partial code-to-cloud coverage can hide high-risk vulnerabilities and mislead central governance. It protects a different risk than the GitHub secret scanning and push protection requirement.

C:

A container image may ship known vulnerable packages even when the application itself passes all functional tests. It does not retain the GitHub secret scanning and push protection control over time.

Question 890

During an operational security assessment at a public-sector technology agency, the team documents this issue: A credential rotation is declared complete while the leaked old token can still authenticate. 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. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.
  2. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.
  3. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access.
  4. A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph.
  5. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.

Explanation

Correct Answers

B:

Correct corrective action. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. The action targets the recorded failure (A credential rotation is declared complete while the leaked old token can still authenticate), and is intended to reduce the corresponding risk: Detecting a secret after publication is insufficient while the credential remains usable in history or forks.

C:

Correct verification. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access. The measurement or controlled test provides evidence for the issue (A credential rotation is declared complete while the leaked old token can still authenticate) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. It is not the complementary risk control for GitHub secret scanning and push protection.

D:

A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph. The GitHub secret scanning and push protection implementation and safeguard are still missing.

E:

Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The two-part GitHub secret scanning and push protection control remains unsatisfied.