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 90

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.

Question 891

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A security operations team assumes all GitHub repositories are covered though only one organization was connected. 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. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.
  3. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.
  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

B:

Correct. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. The specific observed issue is: A security operations team assumes all GitHub repositories are covered though only one organization was connected. The intervention addresses the microsoft defender for cloud devops posture exposure, where disconnected or partial code-to-cloud coverage can hide high-risk vulnerabilities and mislead central governance. After the change, acceptance should establish: A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.

Incorrect Answers

A:

Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. That change would not implement microsoft defender for cloud devops posture.

C:

Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The microsoft defender for cloud devops posture prerequisite remains unaddressed.

D:

Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. It changes a different feature than microsoft defender for cloud devops posture.

Question 892

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A security operations team assumes all GitHub repositories are covered though only one organization was connected. 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 seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process.
  2. A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph.
  3. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access.
  4. A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.

Explanation

Correct Answer

D:

Correct. A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity. This observable result is specific to the reported issue: A security operations team assumes all GitHub repositories are covered though only one organization was connected. It checks the effectiveness of the proposed correction (Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

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 microsoft defender for cloud devops posture, not only that test.

B:

A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph. It does not establish the requested microsoft defender for cloud devops posture outcome.

C:

An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access. The relevant success criterion is microsoft defender for cloud devops posture; this measures a different function.

Question 893

During a regulated production readiness review at a financial technology company, the team documents this issue: A newly created Azure DevOps project has no Defender integration despite the enterprise policy. 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. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.
  2. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.
  3. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.
  4. Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.

Explanation

Correct Answer

C:

Correct. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. The specific observed issue is: A newly created Azure DevOps project has no Defender integration despite the enterprise policy. The intervention addresses the microsoft defender for cloud devops posture exposure, where disconnected or partial code-to-cloud coverage can hide high-risk vulnerabilities and mislead central governance. After the change, acceptance should establish: A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.

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 microsoft defender for cloud devops posture prerequisite remains unaddressed.

B:

Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. It changes a different feature than microsoft defender for cloud devops posture.

D:

Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. The configuration must instead establish microsoft defender for cloud devops posture.

Question 894

During a regulated production readiness review at a financial technology company, the team documents this issue: A newly created Azure DevOps project has no Defender integration despite the enterprise policy. 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. 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 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

D:

Correct. A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity. This observable result is specific to the reported issue: A newly created Azure DevOps project has no Defender integration despite the enterprise policy. It checks the effectiveness of the proposed correction (Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access. The relevant success criterion is microsoft defender for cloud devops posture; this measures a different function.

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 microsoft defender for cloud devops posture.

C:

A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. Acceptance here depends on observing microsoft defender for cloud devops posture, not only that test.

Question 895

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: Findings are visible centrally but cannot be associated with owning application teams. 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. 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 Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.
  4. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.

Explanation

Correct Answer

A:

Correct. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. The specific observed issue is: Findings are visible centrally but cannot be associated with owning application teams. The intervention addresses the microsoft defender for cloud devops posture exposure, where disconnected or partial code-to-cloud coverage can hide high-risk vulnerabilities and mislead central governance. After the change, acceptance should establish: A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.

Incorrect Answers

B:

Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. Acceptance here depends on observing microsoft defender for cloud devops posture, not only that test.

C:

Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. It does not establish the requested microsoft defender for cloud devops posture outcome.

D:

Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The relevant success criterion is microsoft defender for cloud devops posture; this measures a different function.

Question 896

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: Findings are visible centrally but cannot be associated with owning application teams. 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 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. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.
  4. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access.

Explanation

Correct Answer

A:

Correct. A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity. This observable result is specific to the reported issue: Findings are visible centrally but cannot be associated with owning application teams. It checks the effectiveness of the proposed correction (Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

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 microsoft defender for cloud devops posture outcome.

C:

A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. The relevant success criterion is microsoft defender for cloud devops posture; this measures a different function.

D:

An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access. That result could pass without demonstrating microsoft defender for cloud devops posture.

Question 897

During a high-volume service modernization at a multinational retail group, the team documents this issue: A production repo's code security posture is reported as healthy although ingestion stopped. 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. Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.
  2. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.
  3. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.
  4. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.

Explanation

Correct Answer

D:

Correct. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. The specific observed issue is: A production repo's code security posture is reported as healthy although ingestion stopped. The intervention addresses the microsoft defender for cloud devops posture exposure, where disconnected or partial code-to-cloud coverage can hide high-risk vulnerabilities and mislead central governance. After the change, acceptance should establish: A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.

Incorrect Answers

A:

Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. The microsoft defender for cloud devops posture prerequisite remains unaddressed.

B:

Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. It changes a different feature than microsoft defender for cloud devops posture.

C:

Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. That change would not implement microsoft defender for cloud devops posture.

Question 898

During a high-volume service modernization at a multinational retail group, the team documents this issue: A production repo's code security posture is reported as healthy although ingestion stopped. 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 test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.
  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 deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.

Explanation

Correct Answer

D:

Correct. A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity. This observable result is specific to the reported issue: A production repo's code security posture is reported as healthy although ingestion stopped. It checks the effectiveness of the proposed correction (Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. The relevant success criterion is microsoft defender for cloud devops posture; this measures a different function.

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 microsoft defender for cloud devops posture.

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 microsoft defender for cloud devops posture, not only that test.

Question 899

During an operational security assessment at a public-sector technology agency, the team documents this issue: A high-risk pull-request finding appears but is never routed to an accountable remediation owner. 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. A container image may ship known vulnerable packages even when the application itself passes all functional tests.
  2. Transitive vulnerable dependencies remain unnoticed when projects only scan their own application source.
  3. Disconnected or partial code-to-cloud coverage can hide high-risk vulnerabilities and mislead central governance.
  4. Security-sensitive code paths may contain vulnerabilities not found by functional tests when scanning is absent or incomplete.

Explanation

Correct Answer

C:

Correct. Disconnected or partial code-to-cloud coverage can hide high-risk vulnerabilities and mislead central governance. This risk follows from the recorded condition: A high-risk pull-request finding appears but is never routed to an accountable remediation owner. The most relevant correction is connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

A container image may ship known vulnerable packages even when the application itself passes all functional tests. It does not retain the microsoft defender for cloud devops posture control over time.

B:

Transitive vulnerable dependencies remain unnoticed when projects only scan their own application source. Recurrence here depends on microsoft defender for cloud devops posture, not this safeguard.

D:

Security-sensitive code paths may contain vulnerabilities not found by functional tests when scanning is absent or incomplete. It protects a different risk than the microsoft defender for cloud devops posture requirement.

Question 900

During an operational security assessment at a public-sector technology agency, the team documents this issue: A high-risk pull-request finding appears but is never routed to an accountable remediation owner. 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. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.
  2. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access.
  3. Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.
  4. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.
  5. A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.

Explanation

Correct Answers

D:

Correct corrective action. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. The action targets the recorded failure (A high-risk pull-request finding appears but is never routed to an accountable remediation owner), and is intended to reduce the corresponding risk: Disconnected or partial code-to-cloud coverage can hide high-risk vulnerabilities and mislead central governance.

E:

Correct verification. A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity. The measurement or controlled test provides evidence for the issue (A high-risk pull-request finding appears but is never routed to an accountable remediation owner) 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 microsoft defender for cloud devops posture, not that measure.

B:

An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access. The microsoft defender for cloud devops posture implementation and safeguard are still missing.

C:

Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. It is not the complementary risk control for microsoft defender for cloud devops posture.