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 91

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.

Question 901

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An AKS deployment pipeline builds an image but never checks its operating-system packages. 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. Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.
  2. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.
  3. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.
  4. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.

Explanation

Correct Answer

C:

Correct. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. The specific observed issue is: An AKS deployment pipeline builds an image but never checks its operating-system packages. The intervention addresses the container image vulnerability scanning exposure, where a container image may ship known vulnerable packages even when the application itself passes all functional tests. After the change, acceptance should establish: A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.

Incorrect Answers

A:

Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. The container image vulnerability scanning prerequisite remains unaddressed.

B:

Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. It changes a different feature than container image vulnerability scanning.

D:

Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The configuration must instead establish container image vulnerability scanning.

Question 902

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An AKS deployment pipeline builds an image but never checks its operating-system packages. 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 deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.
  2. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.
  3. A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph.
  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

B:

Correct. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. This observable result is specific to the reported issue: An AKS deployment pipeline builds an image but never checks its operating-system packages. It checks the effectiveness of the proposed correction (Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.) 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. The relevant success criterion is container image vulnerability scanning; this measures a different function.

C:

A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph. Acceptance here depends on observing container image vulnerability scanning, not only that test.

D:

An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access. It does not establish the requested container image vulnerability scanning outcome.

Question 903

During a regulated production readiness review at a financial technology company, the team documents this issue: A container tag is scanned before another process overwrites it with a different image. 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. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.
  2. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.
  3. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.
  4. Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.

Explanation

Correct Answer

C:

Correct. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. The specific observed issue is: A container tag is scanned before another process overwrites it with a different image. The intervention addresses the container image vulnerability scanning exposure, where a container image may ship known vulnerable packages even when the application itself passes all functional tests. After the change, acceptance should establish: A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.

Incorrect Answers

A:

Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. That change would not implement container image vulnerability scanning.

B:

Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. The configuration must instead establish container image vulnerability scanning.

D:

Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. It changes a different feature than container image vulnerability scanning.

Question 904

During a regulated production readiness review at a financial technology company, the team documents this issue: A container tag is scanned before another process overwrites it with a different image. 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 seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process.
  2. An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access.
  3. A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.
  4. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.

Explanation

Correct Answer

D:

Correct. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. This observable result is specific to the reported issue: A container tag is scanned before another process overwrites it with a different image. It checks the effectiveness of the proposed correction (Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.) 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 container image vulnerability scanning, not only that test.

B:

An intentionally synthetic secret is blocked during push and a previously exposed test credential is revoked and removed from authorized access. It does not establish the requested container image vulnerability scanning outcome.

C:

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

Question 905

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A security policy blocks a container release but the deployment workflow ignores the scanner's exit status. 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. Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.
  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

C:

Correct. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. The specific observed issue is: A security policy blocks a container release but the deployment workflow ignores the scanner's exit status. The intervention addresses the container image vulnerability scanning exposure, where a container image may ship known vulnerable packages even when the application itself passes all functional tests. After the change, acceptance should establish: A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.

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 does not establish the requested container image vulnerability scanning outcome.

B:

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

D:

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 container image vulnerability scanning, not only that test.

Question 906

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A security policy blocks a container release but the deployment workflow ignores the scanner's exit status. 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 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. 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

C:

Correct. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. This observable result is specific to the reported issue: A security policy blocks a container release but the deployment workflow ignores the scanner's exit status. It checks the effectiveness of the proposed correction (Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.) 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. The relevant success criterion is container image vulnerability scanning; 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 container image vulnerability scanning.

D:

A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity. It does not establish the requested container image vulnerability scanning outcome.

Question 907

During a high-volume service modernization at a multinational retail group, the team documents this issue: A scanner finding remains unresolved although the image is repeatedly promoted to production. 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 CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.
  2. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.
  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

D:

Correct. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. The specific observed issue is: A scanner finding remains unresolved although the image is repeatedly promoted to production. The intervention addresses the container image vulnerability scanning exposure, where a container image may ship known vulnerable packages even when the application itself passes all functional tests. After the change, acceptance should establish: A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.

Incorrect Answers

A:

Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. That change would not implement container image vulnerability scanning.

B:

Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. The configuration must instead establish container image vulnerability scanning.

C:

Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. The container image vulnerability scanning prerequisite remains unaddressed.

Question 908

During a high-volume service modernization at a multinational retail group, the team documents this issue: A scanner finding remains unresolved although the image is repeatedly promoted to production. 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. 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 test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. This observable result is specific to the reported issue: A scanner finding remains unresolved although the image is repeatedly promoted to production. It checks the effectiveness of the proposed correction (Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.) 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. It does not establish the requested container image vulnerability scanning outcome.

C:

A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process. The relevant success criterion is container image vulnerability scanning; 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 container image vulnerability scanning.

Question 909

During an operational security assessment at a public-sector technology agency, the team documents this issue: A build uses a cached base image with known critical vulnerabilities despite a safe newer version. 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. A container image may ship known vulnerable packages even when the application itself passes all functional tests.
  2. Security-sensitive code paths may contain vulnerabilities not found by functional tests when scanning is absent or incomplete.
  3. Detecting a secret after publication is insufficient while the credential remains usable in history or forks.
  4. Transitive vulnerable dependencies remain unnoticed when projects only scan their own application source.

Explanation

Correct Answer

A:

Correct. A container image may ship known vulnerable packages even when the application itself passes all functional tests. This risk follows from the recorded condition: A build uses a cached base image with known critical vulnerabilities despite a safe newer version. The most relevant correction is scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

B:

Security-sensitive code paths may contain vulnerabilities not found by functional tests when scanning is absent or incomplete. It changes a different feature than container image vulnerability scanning.

C:

Detecting a secret after publication is insufficient while the credential remains usable in history or forks. That change would not implement container image vulnerability scanning.

D:

Transitive vulnerable dependencies remain unnoticed when projects only scan their own application source. The configuration must instead establish container image vulnerability scanning.

Question 910

During an operational security assessment at a public-sector technology agency, the team documents this issue: A build uses a cached base image with known critical vulnerabilities despite a safe newer version. 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 GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.
  2. A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.
  3. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.
  4. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.
  5. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.

Explanation

Correct Answers

C:

Correct corrective action. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. The action targets the recorded failure (A build uses a cached base image with known critical vulnerabilities despite a safe newer version), and is intended to reduce the corresponding risk: A container image may ship known vulnerable packages even when the application itself passes all functional tests.

D:

Correct verification. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. The measurement or controlled test provides evidence for the issue (A build uses a cached base image with known critical vulnerabilities despite a safe newer version) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. It is not the complementary risk control for container image vulnerability scanning.

B:

A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity. This does not supply the required container image vulnerability scanning action-and-control pair.

E:

Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The two-part container image vulnerability scanning control remains unsatisfied.