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 87

Question 860

During an operational security assessment at a public-sector technology agency, the team documents this issue: A release stage references an insecure plain variable for a sensitive token despite an available Key Vault link. 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. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.
  2. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.
  3. A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.
  4. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.
  5. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.

Explanation

Correct Answers

A:

Correct corrective action. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. The action targets the recorded failure (A release stage references an insecure plain variable for a sensitive token despite an available Key Vault link), and is intended to reduce the corresponding risk: Treating arbitrary certificates as linked secrets or exposing secure files broadly can leak deployment material and cause pipeline failures.

D:

Correct verification. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. The measurement or controlled test provides evidence for the issue (A release stage references an insecure plain variable for a sensitive token despite an available Key Vault link) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

B:

Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. The azure pipelines secure files and key vault variable groups implementation and safeguard are still missing.

C:

A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value. It is not the complementary risk control for azure pipelines secure files and key vault variable groups.

E:

Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The two-part azure pipelines secure files and key vault variable groups control remains unsatisfied.

Question 861

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A new web repository has no code-scanning workflow although it processes customer input. 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 CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.
  2. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.
  3. Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.
  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

A:

Correct. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The specific observed issue is: A new web repository has no code-scanning workflow although it processes customer input. The intervention addresses the github code scanning with codeql exposure, where security-sensitive code paths may contain vulnerabilities not found by functional tests when scanning is absent or incomplete. After the change, acceptance should establish: A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process.

Incorrect Answers

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 GitHub code scanning with codeql.

C:

Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. That change would not implement GitHub code scanning with codeql.

D:

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 GitHub code scanning with codeql.

Question 862

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A new web repository has no code-scanning workflow although it processes customer input. 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 seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process.
  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

B:

Correct. A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process. This observable result is specific to the reported issue: A new web repository has no code-scanning workflow although it processes customer input. It checks the effectiveness of the proposed correction (Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.) 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 GitHub code scanning with codeql; this measures a different function.

C:

A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity. Acceptance here depends on observing GitHub code scanning with codeql, 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 code scanning with codeql outcome.

Question 863

During a regulated production readiness review at a financial technology company, the team documents this issue: CodeQL is enabled only for one of three languages actually compiled by the project. 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 Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.
  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. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.

Explanation

Correct Answer

C:

Correct. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The specific observed issue is: CodeQL is enabled only for one of three languages actually compiled by the project. The intervention addresses the github code scanning with codeql exposure, where security-sensitive code paths may contain vulnerabilities not found by functional tests when scanning is absent or incomplete. After the change, acceptance should establish: A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process.

Incorrect Answers

A:

Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. That change would not implement GitHub code scanning with codeql.

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 GitHub code scanning with codeql.

D:

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 GitHub code scanning with codeql.

Question 864

During a regulated production readiness review at a financial technology company, the team documents this issue: CodeQL is enabled only for one of three languages actually compiled by the project. 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. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.
  4. A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph.

Explanation

Correct Answer

B:

Correct. A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process. This observable result is specific to the reported issue: CodeQL is enabled only for one of three languages actually compiled by the project. It checks the effectiveness of the proposed correction (Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.) 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 code scanning with codeql, not only that test.

C:

A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. The relevant success criterion is GitHub code scanning with codeql; this measures a different function.

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 code scanning with codeql.

Question 865

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: Security findings are reported but the protected branch ignores high-severity alerts. 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. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.
  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. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.

Explanation

Correct Answer

C:

Correct. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The specific observed issue is: Security findings are reported but the protected branch ignores high-severity alerts. The intervention addresses the github code scanning with codeql exposure, where security-sensitive code paths may contain vulnerabilities not found by functional tests when scanning is absent or incomplete. After the change, acceptance should establish: A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process.

Incorrect Answers

A:

Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. It does not establish the requested GitHub code scanning with codeql outcome.

B:

Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. The relevant success criterion is GitHub code scanning with codeql; this measures a different function.

D:

Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. Acceptance here depends on observing GitHub code scanning with codeql, not only that test.

Question 866

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: Security findings are reported but the protected branch ignores high-severity alerts. 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 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

C:

Correct. A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process. This observable result is specific to the reported issue: Security findings are reported but the protected branch ignores high-severity alerts. It checks the effectiveness of the proposed correction (Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.) 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 GitHub code scanning with codeql; 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 GitHub code scanning with codeql.

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 GitHub code scanning with codeql outcome.

Question 867

During a high-volume service modernization at a multinational retail group, the team documents this issue: A scanning job runs on a schedule but new PRs can merge before any code analysis. 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. 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. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.

Explanation

Correct Answer

B:

Correct. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The specific observed issue is: A scanning job runs on a schedule but new PRs can merge before any code analysis. The intervention addresses the github code scanning with codeql exposure, where security-sensitive code paths may contain vulnerabilities not found by functional tests when scanning is absent or incomplete. After the change, acceptance should establish: A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process.

Incorrect Answers

A:

Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. That change would not implement GitHub code scanning with codeql.

C:

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

D:

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 GitHub code scanning with codeql.

Question 868

During a high-volume service modernization at a multinational retail group, the team documents this issue: A scanning job runs on a schedule but new PRs can merge before any code analysis. 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 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 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 seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process. This observable result is specific to the reported issue: A scanning job runs on a schedule but new PRs can merge before any code analysis. It checks the effectiveness of the proposed correction (Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.) 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 code scanning with codeql, not only that test.

C:

A known vulnerable dependency produces an attributable alert and an approved update restores the tested safe dependency graph. The relevant success criterion is GitHub code scanning with codeql; 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 GitHub code scanning with codeql.

Question 869

During an operational security assessment at a public-sector technology agency, the team documents this issue: An engineer marks a genuine alert dismissed without recording a justification or review. 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. Disconnected or partial code-to-cloud coverage can hide high-risk vulnerabilities and mislead central governance.
  2. Detecting a secret after publication is insufficient while the credential remains usable in history or forks.
  3. Transitive vulnerable dependencies remain unnoticed when projects only scan their own application source.
  4. Security-sensitive code paths may contain vulnerabilities not found by functional tests when scanning is absent or incomplete.

Explanation

Correct Answer

D:

Correct. Security-sensitive code paths may contain vulnerabilities not found by functional tests when scanning is absent or incomplete. This risk follows from the recorded condition: An engineer marks a genuine alert dismissed without recording a justification or review. The most relevant correction is enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Disconnected or partial code-to-cloud coverage can hide high-risk vulnerabilities and mislead central governance. The GitHub code scanning with codeql prerequisite remains unaddressed.

B:

Detecting a secret after publication is insufficient while the credential remains usable in history or forks. It changes a different feature than GitHub code scanning with codeql.

C:

Transitive vulnerable dependencies remain unnoticed when projects only scan their own application source. That change would not implement GitHub code scanning with codeql.

Question 870

During an operational security assessment at a public-sector technology agency, the team documents this issue: An engineer marks a genuine alert dismissed without recording a justification or review. 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. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.
  2. A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process.
  3. Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages.
  4. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.
  5. Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context.

Explanation

Correct Answers

A:

Correct corrective action. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The action targets the recorded failure (An engineer marks a genuine alert dismissed without recording a justification or review), and is intended to reduce the corresponding risk: Security-sensitive code paths may contain vulnerabilities not found by functional tests when scanning is absent or incomplete.

B:

Correct verification. A seeded insecure code pattern generates a CodeQL finding and a protected PR cannot dismiss it without the approved review process. The measurement or controlled test provides evidence for the issue (An engineer marks a genuine alert dismissed without recording a justification or review) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

C:

Enable Dependabot alerts and appropriate dependency updates with reviewed lockfile changes and a policy for vulnerable packages. The paired controls concern GitHub code scanning with codeql, not that measure.

D:

A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. The GitHub code scanning with codeql implementation and safeguard are still missing.

E:

Connect supported DevOps repositories to Microsoft Defender for Cloud DevOps Security and evaluate findings in the correct subscription and project context. The two-part GitHub code scanning with codeql control remains unsatisfied.