McAfee Secure

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

Microsoft AZ-400 Bundle $44.99

100% Microsoft AZ-400 Guaranteed Success With Testking Training Materials

Get Real AZ-400 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    AZ-400 Questions & Answers

    398 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual AZ-400 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • AZ-400 Video Course

    AZ-400 Training Course

    27 Video Lectures

    AZ-400 Video Course is developed by Microsoft Professionals to help you pass the AZ-400 exam.

    Description

    This course will improve your knowledge and skills required to pass Designing and Implementing Microsoft DevOps Solutions exam.
  • Study Guide

    AZ-400 Study Guide

    784 PDF Pages

    Developed by industry experts, this 784-page guide spells out in painstaking detail all of the information you need to ace AZ-400 exam.

Designing and Implementing Microsoft DevOps Solutions (AZ-400) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    398 Questions

    $124.99
  • AZ-400 Video Course

    Training Course

    27 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    784 PDF Pages

    $29.99

Microsoft AZ-400 Practice Test 21

Question 200

At the Redhaven customer support provider, following an unexpected peak in customer demand, a security patch for an older supported version accidentally ships unfinished new features from main. Which maintenance practice best addresses the continuing risk?

  1. Audit repository reviewer policies and stale approval dismissal settings
  2. Review trigger and token permissions after workflow changes
  3. Review sparse selection rules whenever project dependencies change
  4. Review branch support windows and backport approvals after each product release

Explanation

Correct Answer

D:

After the immediate fix, the priority is to review branch support windows and backport approvals after each product release. This reinforces the control against the original weakness: applying an unrelated development head can introduce changes outside a maintenance release. This directly addresses the reported issue at the Redhaven customer support provider.

Incorrect Answers

A:

This routine applies to branch policy required reviewers, but it does not maintain the specific correction needed for the problem at the Redhaven customer support provider.

B:

That practice helps control a different risk: untrusted pull request code can abuse secrets or privileged runner contexts if not separated. The recurring control here should be to review branch support windows and backport approvals after each product release. For the Redhaven customer support provider, the priority is to maintain controlled maintenance branches for supported releases and backport only verified fixes.

C:

The alternative suggests that the team review sparse selection rules whenever project dependencies change; it would not directly prevent the observed issue from returning. For the Redhaven customer support provider, the priority is to maintain controlled maintenance branches for supported releases and backport only verified fixes.

Question 201

At the Dunbridge enterprise software provider, during a continuity exercise, urgent production patches are committed directly to a release branch and never returned to development. What should the team implement to resolve the issue?

  1. Use a reviewed merge strategy that preserves required change and work-item traceability
  2. Merge or cherry-pick approved fixes back to the main development line and verify both paths
  3. Audit inherited repository and team permissions and explicitly restrict confidential projects
  4. Enable supported secret scanning and push protection with governed exception handling

Explanation

Correct Answer

B:

The reported behavior calls for a focused correction: merge or cherry-pick approved fixes back to the main development line and verify both paths. It is necessary because unreconciled hotfixes can disappear in the next normal release or be reintroduced incorrectly. Verification should establish that the emergency fix exists with passing tests in both supported code lines. This directly addresses the reported issue at the Dunbridge enterprise software provider.

Incorrect Answers

A:

The proposed action would be to use a reviewed merge strategy that preserves required change and work-item traceability, which is relevant to merge strategy for auditability. It would leave the main reported problem unresolved. For the Dunbridge enterprise software provider, the priority is to merge or cherry-pick approved fixes back to the main development line and verify both paths.

C:

This is appropriate in cases involving repository permission inheritance, but the facts here call for the team to merge or cherry-pick approved fixes back to the main development line and verify both paths. For the Dunbridge enterprise software provider, the priority is to merge or cherry-pick approved fixes back to the main development line and verify both paths.

D:

That change could address repository secret push protection, but it does not resolve the specific weakness here: unreconciled hotfixes can disappear in the next normal release or be reintroduced incorrectly. For the Dunbridge enterprise software provider, the priority is to merge or cherry-pick approved fixes back to the main development line and verify both paths.

Question 202

At the Dunbridge enterprise software provider, during a continuity exercise, urgent production patches are committed directly to a release branch and never returned to development. What underlying weakness best explains these results?

  1. Long waits for a launch create avoidable branch drift and late integration risk
  2. Discovering credentials after merge leaves a window in which secrets may be copied or abused
  3. Unreconciled hotfixes can disappear in the next normal release or be reintroduced incorrectly
  4. Deleting the current file does not erase secret values from earlier commits and clones

Explanation

Correct Answer

C:

The critical gap is that unreconciled hotfixes can disappear in the next normal release or be reintroduced incorrectly. At the Dunbridge enterprise software provider, correcting that gap requires the team to merge or cherry-pick approved fixes back to the main development line and verify both paths.

Incorrect Answers

A:

The alternative “Long waits for a launch create avoidable branch drift and late integration risk” tests a different outcome. The case describes: At the Dunbridge enterprise software provider, during a continuity exercise, urgent production patches are committed directly to a release branch and never returned to development. The selected response is “Unreconciled hotfixes can disappear in the next normal release or be reintroduced incorrectly”.

B:

That statement concerns repository secret push protection; here the reported facts point to a different issue: unreconciled hotfixes can disappear in the next normal release or be reintroduced incorrectly. For the Dunbridge enterprise software provider, the priority is to merge or cherry-pick approved fixes back to the main development line and verify both paths.

D:

This explanation belongs to history rewrite for leaked secret. The immediate weakness in the question is that unreconciled hotfixes can disappear in the next normal release or be reintroduced incorrectly. For the Dunbridge enterprise software provider, the priority is to merge or cherry-pick approved fixes back to the main development line and verify both paths.

Question 203

At the Dunbridge enterprise software provider, during a continuity exercise, urgent production patches are committed directly to a release branch and never returned to development. What evidence most directly demonstrates that the fix works?

  1. Two interdependent changes enter the queue and only a passing combined result reaches main
  2. A restored file matches the selected reviewed commit and passes its validation checks
  3. A deployed version remains retrievable by immutable reference after later commits and branch changes
  4. The emergency fix exists with passing tests in both supported code lines

Explanation

Correct Answer

D:

The team needs direct evidence that the emergency fix exists with passing tests in both supported code lines. That result verifies whether the action to merge or cherry-pick approved fixes back to the main development line and verify both paths has been effective. This directly addresses the reported issue at the Dunbridge enterprise software provider.

Incorrect Answers

A:

The proposed proof concerns a different control: two interdependent changes enter the queue and only a passing combined result reaches main. It would not establish that the emergency fix exists with passing tests in both supported code lines. For the Dunbridge enterprise software provider, the priority is to merge or cherry-pick approved fixes back to the main development line and verify both paths.

B:

That observation can be useful for partial history recovery, but at the Dunbridge enterprise software provider the required outcome is that the emergency fix exists with passing tests in both supported code lines.

C:

The reported facts are: At the Dunbridge enterprise software provider, during a continuity exercise, urgent production patches are committed directly to a release branch and never returned to development. “A deployed version remains retrievable by immutable reference after later commits and branch changes” addresses a different task, while “The emergency fix exists with passing tests in both supported code lines” responds directly to this problem.

Question 204

At the Dunbridge enterprise software provider, during a continuity exercise, urgent production patches are committed directly to a release branch and never returned to development. Which routine control would most effectively sustain the fix?

  1. Review feature flag ownership and remove obsolete flags after release
  2. Include back-merge confirmation in emergency release closure
  3. Review signing keys and attestation verification after contributor changes
  4. Restrict tag creation and verify release references in deployment records

Explanation

Correct Answer

B:

This is the relevant recurring safeguard: include back-merge confirmation in emergency release closure. It is tied directly to the observed failure mode rather than a separate system concern. This directly addresses the reported issue at the Dunbridge enterprise software provider.

Incorrect Answers

A:

This maintenance work is reasonable for feature-flag branch reduction. The continuing exposure described here is that unreconciled hotfixes can disappear in the next normal release or be reintroduced incorrectly. For the Dunbridge enterprise software provider, the priority is to merge or cherry-pick approved fixes back to the main development line and verify both paths.

C:

This routine applies to signed commit policy, but it does not maintain the specific correction needed for the problem at the Dunbridge enterprise software provider.

D:

That practice helps control a different risk: mutable release identifiers undermine repeatable deployment and rollback evidence. The recurring control here should be to include back-merge confirmation in emergency release closure. For the Dunbridge enterprise software provider, the priority is to merge or cherry-pick approved fixes back to the main development line and verify both paths.

Question 205

At the Quayford public university, while preparing a multi-team release, an access token was committed and deleting the latest file leaves it visible in earlier Git history. What is the best recommendation to correct this problem?

  1. Grant least-privilege repository access and use pull requests for controlled contributions
  2. Use a merge queue or equivalent integration validation against the combined change set
  3. Revoke the exposed credential and perform a controlled history-removal procedure where required
  4. Integrate reviewed changes behind controlled flags while keeping user exposure disabled until approved

Explanation

Correct Answer

C:

Because deleting the current file does not erase secret values from earlier commits and clones, the team should revoke the exposed credential and perform a controlled history-removal procedure where required. The most useful check is that the credential is rotated and automated history checks no longer expose the removed token in the maintained repository. This directly addresses the reported issue at the Quayford public university.

Incorrect Answers

A:

That change could address repository contributor permissions, but it does not resolve the specific weakness here: deleting the current file does not erase secret values from earlier commits and clones. For the Quayford public university, the priority is to revoke the exposed credential and perform a controlled history-removal procedure where required.

B:

This option deals with a related concern where successful isolated checks do not guarantee that concurrent merges remain compatible. The case at the Quayford public university instead requires the correction to revoke the exposed credential and perform a controlled history-removal procedure where required.

D:

The scenario states: At the Quayford public university, while preparing a multi-team release, an access token was committed and deleting the latest file leaves it visible in earlier Git history. “Integrate reviewed changes behind controlled flags while keeping user exposure disabled until approved” does not correct this failure. Deleting the current file does not erase secret values from earlier commits and clones, the team should revoke the exposed credential and perform a controlled history-removal procedure where required. The more directly supported option is “Revoke the exposed credential and perform a controlled history-removal procedure where required”.

Question 206

At the Quayford public university, while preparing a multi-team release, an access token was committed and deleting the latest file leaves it visible in earlier Git history. What is the most significant cause of this behavior?

  1. Untrusted pull request code can abuse secrets or privileged runner contexts if not separated
  2. Direct pushes bypass independent checks and may introduce untested production changes
  3. Deleting the current file does not erase secret values from earlier commits and clones
  4. Long-running divergent branches increase merge conflict and inconsistent code behavior

Explanation

Correct Answer

C:

This is the most direct cause because deleting the current file does not erase secret values from earlier commits and clones. The team can address it by choosing to revoke the exposed credential and perform a controlled history-removal procedure where required. This directly addresses the reported issue at the Quayford public university.

Incorrect Answers

A:

This explanation belongs to forked repository pull request security. The immediate weakness in the question is that deleting the current file does not erase secret values from earlier commits and clones. For the Quayford public university, the priority is to revoke the exposed credential and perform a controlled history-removal procedure where required.

B:

Although direct pushes bypass independent checks and may introduce untested production changes, the situation does not describe that specific cause; it instead indicates that deleting the current file does not erase secret values from earlier commits and clones. For the Quayford public university, the priority is to revoke the exposed credential and perform a controlled history-removal procedure where required.

D:

That statement concerns trunk-based integration; here the reported facts point to a different issue: deleting the current file does not erase secret values from earlier commits and clones. For the Quayford public university, the priority is to revoke the exposed credential and perform a controlled history-removal procedure where required.

Question 207

At the Quayford public university, while preparing a multi-team release, an access token was committed and deleting the latest file leaves it visible in earlier Git history. Which evidence best supports closing this issue?

  1. A test secret is rejected before acceptance and any approved bypass is logged
  2. A test edit under the protected path requests and obtains the designated platform review
  3. A change cannot complete until an independent permitted reviewer approves it
  4. The credential is rotated and automated history checks no longer expose the removed token in the maintained repository

Explanation

Correct Answer

D:

For the Quayford public university, the credential is rotated and automated history checks no longer expose the removed token in the maintained repository confirms the control rather than only documenting a proposed change. The corrective action is to revoke the exposed credential and perform a controlled history-removal procedure where required.

Incorrect Answers

A:

The reported facts are: At the Quayford public university, while preparing a multi-team release, an access token was committed and deleting the latest file leaves it visible in earlier Git history. “A test secret is rejected before acceptance and any approved bypass is logged” addresses a different task, while “The credential is rotated and automated history checks no longer expose the removed token in the maintained repository” responds directly to this problem.

B:

This result would test codeowners required review, not the failure described here. The more direct evidence is that the credential is rotated and automated history checks no longer expose the removed token in the maintained repository. For the Quayford public university, the priority is to revoke the exposed credential and perform a controlled history-removal procedure where required.

C:

The proposed proof concerns a different control: a change cannot complete until an independent permitted reviewer approves it. It would not establish that the credential is rotated and automated history checks no longer expose the removed token in the maintained repository. For the Quayford public university, the priority is to revoke the exposed credential and perform a controlled history-removal procedure where required.

Question 208

At the Quayford public university, while preparing a multi-team release, an access token was committed and deleting the latest file leaves it visible in earlier Git history. Which ongoing practice would best prevent a recurrence?

  1. Add secret scanning and prevention rules before accepting new commits
  2. Restrict tag creation and verify release references in deployment records
  3. Update code ownership when protected paths and team responsibilities change
  4. Review protection exemptions and administrator bypass rights regularly

Explanation

Correct Answer

A:

For the Quayford public university, the control should be maintained by having the team add secret scanning and prevention rules before accepting new commits. It reduces the chance that deleting the current file does not erase secret values from earlier commits and clones.

Incorrect Answers

B:

The alternative suggests that the team restrict tag creation and verify release references in deployment records; it would not directly prevent the observed issue from returning. For the Quayford public university, the priority is to revoke the exposed credential and perform a controlled history-removal procedure where required.

C:

This maintenance work is reasonable for codeowners required review. The continuing exposure described here is that deleting the current file does not erase secret values from earlier commits and clones. For the Quayford public university, the priority is to revoke the exposed credential and perform a controlled history-removal procedure where required.

D:

“Review protection exemptions and administrator bypass rights regularly” addresses an adjacent control. The reported case is: At the Quayford public university, while preparing a multi-team release, an access token was committed and deleting the latest file leaves it visible in earlier Git history. The case-matched answer is “Add secret scanning and prevention rules before accepting new commits”.

Question 209

At the Eastbrook analytics division, after adding an external software supplier, a monorepo contains millions of files and full checkout slows every build worker. What should the DevOps team change first?

  1. Protect release tags and associate each version with a fixed reviewed commit and artifact
  2. Use appropriate sparse checkout or Scalar/Git optimization for the workload without omitting required source
  3. Use a merge queue or equivalent integration validation against the combined change set
  4. Maintain controlled maintenance branches for supported releases and backport only verified fixes

Explanation

Correct Answer

B:

This is the appropriate response because full working-tree materialization can waste resources when a job needs only selected projects. Implementing the control means the team will use appropriate sparse checkout or Scalar/Git optimization for the workload without omitting required source, then test that a clean build retrieves its required paths and produces the same tested output with reduced checkout time. This directly addresses the reported issue at the Eastbrook analytics division.

Incorrect Answers

A:

The scenario states: At the Eastbrook analytics division, after adding an external software supplier, a monorepo contains millions of files and full checkout slows every build worker. “Protect release tags and associate each version with a fixed reviewed commit and artifact” does not correct this failure. Full working-tree materialization can waste resources when a job needs only selected projects. The more directly supported option is “Use appropriate sparse checkout or Scalar/Git optimization for the workload without omitting required source”.

C:

That change could address merge queue validation, but it does not resolve the specific weakness here: full working-tree materialization can waste resources when a job needs only selected projects. For the Eastbrook analytics division, the priority is to use appropriate sparse checkout or Scalar/Git optimization for the workload without omitting required source.

D:

This option deals with a related concern where applying an unrelated development head can introduce changes outside a maintenance release. The case at the Eastbrook analytics division instead requires the correction to use appropriate sparse checkout or Scalar/Git optimization for the workload without omitting required source.

Question 210

At the Eastbrook analytics division, after adding an external software supplier, a monorepo contains millions of files and full checkout slows every build worker. What is the primary reason this approach is unreliable?

  1. Displayed author names alone are not strong proof of the identity controlling a change
  2. Self-approval eliminates meaningful challenge for sensitive repository changes
  3. Full working-tree materialization can waste resources when a job needs only selected projects
  4. Generic peer approval may not cover specialist risks in critical automation files

Explanation

Correct Answer

C:

This explanation matches the reported facts: full working-tree materialization can waste resources when a job needs only selected projects. A corrective test should establish that a clean build retrieves its required paths and produces the same tested output with reduced checkout time. This directly addresses the reported issue at the Eastbrook analytics division.

Incorrect Answers

A:

That statement concerns signed commit policy; here the reported facts point to a different issue: full working-tree materialization can waste resources when a job needs only selected projects. For the Eastbrook analytics division, the priority is to use appropriate sparse checkout or Scalar/Git optimization for the workload without omitting required source.

B:

Self-approval eliminates meaningful challenge for sensitive repository changes. This can occur in other projects, but it is not the primary explanation at the Eastbrook analytics division.

D:

Although generic peer approval may not cover specialist risks in critical automation files, the situation does not describe that specific cause; it instead indicates that full working-tree materialization can waste resources when a job needs only selected projects. For the Eastbrook analytics division, the priority is to use appropriate sparse checkout or Scalar/Git optimization for the workload without omitting required source.