Microsoft AZ-400 Practice Test 14

Question 130

After the team applies this response: Configure Azure Repos policies to reset or require renewed approvals when updates change the reviewed PR content. In the situation—Azure Repos reviewers approve a PR before a new commit is pushed, yet the original approval remains accepted automatically. Which evidence BEST demonstrates the response is effective?

Inspect the recovered commit tree and run required review and tests before re-integrating it.
Push a controlled change after approval and confirm merge is blocked until required new review completes.
Attempt a force push in a test protected branch and verify policy denial and audit evidence.
Compare pipeline clone time and confirm version calculation and checkout remain correct under the optimized fetch.

Explanation

Correct Answer

The governing engineering principle is: Approval integrity requires binding review decisions to the current content of the change, not an earlier version.

Incorrect Answers

Git recovery should restore a specific verified revision rather than guess based on branch names. What must be demonstrated is: Push a controlled change after approval and confirm merge is blocked until required new review completes.

Shared branch history needs protection against unreviewed rewriting to preserve collaboration and provenance. The appropriate comparison is: Push a controlled change after approval and confirm merge is blocked until required new review completes.

Source retrieval should match the build's history requirements rather than always download the entire repository. The relevant evidence instead is: Push a controlled change after approval and confirm merge is blocked until required new review completes.

Question 131

A separate team has last-minute force pushes after review and cannot tell which exact change the approver considered. Which engineering principle BEST explains the relevant requirement?

Cross-repository collaboration should expose only intended source and dependencies across trust boundaries.
Large repository optimizations reduce local data and work without necessarily changing source ownership boundaries.
Approval integrity requires binding review decisions to the current content of the change, not an earlier version.
Git checkout optimization is not an access-control mechanism because authorized clones can request other objects.

Explanation

Correct Answer

The second engineering situation illustrates the control boundary captured by this principle: Approval integrity requires binding review decisions to the current content of the change, not an earlier version. The scenario is not resolved by an unrelated pipeline or policy activity.

Incorrect Answers

Cross-repository collaboration should expose only intended source and dependencies across trust boundaries. That principle concerns configure and manage repositories, whereas this specific incident is governed by: Approval integrity requires binding review decisions to the current content of the change, not an earlier version.

Large repository optimizations reduce local data and work without necessarily changing source ownership boundaries. That principle concerns configure and manage repositories, whereas this specific incident is governed by: Approval integrity requires binding review decisions to the current content of the change, not an earlier version.

Git checkout optimization is not an access-control mechanism because authorized clones can request other objects. That principle concerns configure and manage repositories, whereas this specific incident is governed by: Approval integrity requires binding review decisions to the current content of the change, not an earlier version.

Question 132

A separate team has last-minute force pushes after review and cannot tell which exact change the approver considered. Which unsupported assumption should the engineer challenge FIRST?

An approval on yesterday's diff is not proof that today's updated diff was reviewed.
A normal push permission is not necessarily authorization to rewrite already published branch history.
Removing someone from one project team does not always revoke access inherited through other groups.
A direct Deny or removal from one group may not describe the complete effective authorization picture.

Explanation

Correct Answer

An approval on yesterday's diff is not proof that today's updated diff was reviewed. This is the relevant unsupported assumption because approval integrity requires binding review decisions to the current content of the change, not an earlier version.

Incorrect Answers

This caution is valid in configure and manage repositories, but it is not the failure assumption illustrated by this scenario. The directly relevant risk is: An approval on yesterday's diff is not proof that today's updated diff was reviewed.

Question 133

An enterprise uses a release branch for monthly patches but merges fixes only there, leaving the main branch vulnerable to regression. Which design or operational change MOST directly satisfies the requirement?

Define a release/hotfix branch flow with reviewed back-merges or cherry-picks into supported branches.
Split privileged content into independently controlled repositories or boundaries rather than rely on sparse checkout.
Audit effective permissions and inherited group grants, then narrow the permission model to required actions.
Pin shared source dependencies to accessible immutable revisions and validate submodule or package availability in CI.

Explanation

Correct Answer

Long-lived maintenance lines require explicit propagation of fixes to prevent divergent defects. The most directly responsive design or operational step is: Define a release/hotfix branch flow with reviewed back-merges or cherry-picks into supported branches. Confirm the result by: Trace a sample hotfix commit through production, the supported release branch and the main development branch.

Incorrect Answers

Git checkout optimization is not an access-control mechanism because authorized clones can request other objects. Instead, the response must define a release/hotfix branch flow with reviewed back-merges or cherry-picks into supported branches.

Source control access must be evaluated as effective permissions across direct and inherited grants. The relevant control is to define a release/hotfix branch flow with reviewed back-merges or cherry-picks into supported branches.

Source dependency reproducibility depends on fixed, accessible references and explicit retrieval processes. The needed step here is to define a release/hotfix branch flow with reviewed back-merges or cherry-picks into supported branches.

Question 134

After the team applies this response: Define a release/hotfix branch flow with reviewed back-merges or cherry-picks into supported branches. In the situation—An enterprise uses a release branch for monthly patches but merges fixes only there, leaving the main branch vulnerable to regression. Which evidence BEST demonstrates the response is effective?

Check token invalidation, cleaned reachable history, protected tags and stakeholder re-clone guidance.
Check the tracked file inventory and perform a clean dependency restore followed by a successful controlled build.
Test contractor access to the separate sensitive repository and confirm authorization differs from the frontend.
Trace a sample hotfix commit through production, the supported release branch and the main development branch.

Explanation

Correct Answer

The governing engineering principle is: Long-lived maintenance lines require explicit propagation of fixes to prevent divergent defects.

Incorrect Answers

Secret remediation requires credential invalidation plus careful history cleanup because Git preserves earlier versions. The appropriate remedy is to trace a sample hotfix commit through production, the supported release branch and the main development branch.

Good repository hygiene versions intentional source inputs, not disposable locally generated outputs. Instead, the response must trace a sample hotfix commit through production, the supported release branch and the main development branch.

Git checkout optimization is not an access-control mechanism because authorized clones can request other objects. The relevant control is to trace a sample hotfix commit through production, the supported release branch and the main development branch.

Question 135

A maintenance team ships emergency fixes from an old branch and forgets to bring the fix into ongoing development. Which engineering principle BEST explains the relevant requirement?

Git LFS keeps large object payloads outside normal Git object history while retaining versioned references.
Long-lived maintenance lines require explicit propagation of fixes to prevent divergent defects.
Git recovery should restore a specific verified revision rather than guess based on branch names.
Shared branch history needs protection against unreviewed rewriting to preserve collaboration and provenance.

Explanation

Correct Answer

The second engineering situation illustrates the control boundary captured by this principle: Long-lived maintenance lines require explicit propagation of fixes to prevent divergent defects. The scenario is not resolved by an unrelated pipeline or policy activity.

Incorrect Answers

Git LFS keeps large object payloads outside normal Git object history while retaining versioned references. That principle concerns configure and manage repositories, whereas this specific incident is governed by: Long-lived maintenance lines require explicit propagation of fixes to prevent divergent defects.

The second engineering situation illustrates the control boundary captured by this principle: Git recovery should restore a specific verified revision rather than guess based on branch names. The acceptance criterion here is: Long-lived maintenance lines require explicit propagation of fixes to prevent divergent defects.

Shared branch history needs protection against unreviewed rewriting to preserve collaboration and provenance. That principle concerns configure and manage repositories, whereas this specific incident is governed by: Long-lived maintenance lines require explicit propagation of fixes to prevent divergent defects.

Question 136

A maintenance team ships emergency fixes from an old branch and forgets to bring the fix into ongoing development. Which unsupported assumption should the engineer challenge FIRST?

Resetting a local branch pointer does not safely undo a published change for every collaborator.
A fix applied on one maintenance branch is not automatically present on every supported branch.
A normal push permission is not necessarily authorization to rewrite already published branch history.
A reference to a moving shared branch does not guarantee repeatable pipeline behavior.

Explanation

Correct Answer

A fix applied on one maintenance branch is not automatically present on every supported branch. This is the relevant unsupported assumption because long-lived maintenance lines require explicit propagation of fixes to prevent divergent defects.

Incorrect Answers

This caution is valid in configure and manage repositories, but it is not the failure assumption illustrated by this scenario. The directly relevant risk is: A fix applied on one maintenance branch is not automatically present on every supported branch.

Question 137

A critical library needs emergency changes, but deployment branches cannot be created or merged because branch naming and permissions are inconsistent. Which design or operational change MOST directly satisfies the requirement?

Define documented naming, protected release branches and controlled emergency PR workflow with traceable approvals.
Store large binary assets in Git LFS with pointer files and manage access to the LFS object store.
Use Git reflog or known object identifiers to locate and restore the correct commit into a reviewed branch.
Audit effective permissions and inherited group grants, then narrow the permission model to required actions.

Explanation

Correct Answer

An emergency workflow should shorten lead time without abandoning auditable source-control safeguards. The most directly responsive design or operational step is: Define documented naming, protected release branches and controlled emergency PR workflow with traceable approvals. Confirm the result by: Simulate a high-priority fix and verify authorized reviewers can approve while normal direct pushes remain blocked.

Incorrect Answers

Git LFS keeps large object payloads outside normal Git object history while retaining versioned references. The needed step here is to define documented naming, protected release branches and controlled emergency PR workflow with traceable approvals.

Git recovery should restore a specific verified revision rather than guess based on branch names. The appropriate remedy is to define documented naming, protected release branches and controlled emergency PR workflow with traceable approvals.

Source control access must be evaluated as effective permissions across direct and inherited grants. Instead, the response must define documented naming, protected release branches and controlled emergency PR workflow with traceable approvals.

Question 138

After the team applies this response: Define documented naming, protected release branches and controlled emergency PR workflow with traceable approvals. In the situation—A critical library needs emergency changes, but deployment branches cannot be created or merged because branch naming and permissions are inconsistent. Which evidence BEST demonstrates the response is effective?

Inspect the recovered commit tree and run required review and tests before re-integrating it.
Reconcile tag protections and release metadata to the approved build for a sampled deployment.
Simulate a high-priority fix and verify authorized reviewers can approve while normal direct pushes remain blocked.
Test contractor access to the separate sensitive repository and confirm authorization differs from the frontend.

Explanation

Correct Answer

The governing engineering principle is: An emergency workflow should shorten lead time without abandoning auditable source-control safeguards.

Incorrect Answers

Git recovery should restore a specific verified revision rather than guess based on branch names. The relevant control is to simulate a high-priority fix and verify authorized reviewers can approve while normal direct pushes remain blocked.

Organized release tagging improves traceability when lifecycle meaning and ownership are explicit. The needed step here is to simulate a high-priority fix and verify authorized reviewers can approve while normal direct pushes remain blocked.

Git checkout optimization is not an access-control mechanism because authorized clones can request other objects. The appropriate remedy is to simulate a high-priority fix and verify authorized reviewers can approve while normal direct pushes remain blocked.

Question 139

Another organization gives broad push rights to every release branch instead of using narrow emergency paths. Which engineering principle BEST explains the relevant requirement?

Source retrieval should match the build's history requirements rather than always download the entire repository.
Git recovery should restore a specific verified revision rather than guess based on branch names.
An emergency workflow should shorten lead time without abandoning auditable source-control safeguards.
Git LFS keeps large object payloads outside normal Git object history while retaining versioned references.

Explanation

Correct Answer

The second engineering situation illustrates the control boundary captured by this principle: An emergency workflow should shorten lead time without abandoning auditable source-control safeguards. The scenario is not resolved by an unrelated pipeline or policy activity.

Incorrect Answers

The second engineering situation illustrates the control boundary captured by this principle: Source retrieval should match the build's history requirements rather than always download the entire repository. What must be demonstrated is: An emergency workflow should shorten lead time without abandoning auditable source-control safeguards.

The second engineering situation illustrates the control boundary captured by this principle: Git recovery should restore a specific verified revision rather than guess based on branch names. The appropriate comparison is: An emergency workflow should shorten lead time without abandoning auditable source-control safeguards.

Git LFS keeps large object payloads outside normal Git object history while retaining versioned references. That principle concerns configure and manage repositories, whereas this specific incident is governed by: An emergency workflow should shorten lead time without abandoning auditable source-control safeguards.

Question 140

Another organization gives broad push rights to every release branch instead of using narrow emergency paths. Which unsupported assumption should the engineer challenge FIRST?

A reference to a moving shared branch does not guarantee repeatable pipeline behavior.
Hiding a folder from the working directory does not make committed secrets inaccessible to repository readers.
A sparse checkout cannot replace a permission boundary for files that users should not access.
An urgent production issue does not by itself justify disabling all protected-branch rules.

Explanation

Correct Answer

An urgent production issue does not by itself justify disabling all protected-branch rules. This is the relevant unsupported assumption because an emergency workflow should shorten lead time without abandoning auditable source-control safeguards.

Incorrect Answers

This caution is valid in configure and manage repositories, but it is not the failure assumption illustrated by this scenario. The directly relevant risk is: An urgent production issue does not by itself justify disabling all protected-branch rules.

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

Microsoft AZ-400 Practice Test 12 - 10 Questions (Last Reviewed 03-Nov-2026)
Microsoft AZ-400 Practice Test 13 - 10 Questions (Last Reviewed 02-Nov-2026)
Microsoft AZ-400 Practice Test 14 - 10 Questions (Last Reviewed 01-Nov-2026)
Microsoft AZ-400 Practice Test 15 - 10 Questions (Last Reviewed 31-Oct-2026)
Microsoft AZ-400 Practice Test 16 - 10 Questions (Last Reviewed 30-Oct-2026)

Pass Your Microsoft AZ-400 Exam Easy!

Question 130

Explanation

Correct Answer

Incorrect Answers

Question 131

Explanation

Correct Answer

Incorrect Answers

Question 132

Explanation

Correct Answer

Incorrect Answers

Question 133

Explanation

Correct Answer

Incorrect Answers

Question 134

Explanation

Correct Answer

Incorrect Answers

Question 135

Explanation

Correct Answer

Incorrect Answers

Question 136

Explanation

Correct Answer

Incorrect Answers

Question 137

Explanation

Correct Answer

Incorrect Answers

Question 138

Explanation

Correct Answer

Incorrect Answers

Question 139

Explanation

Correct Answer

Incorrect Answers

Question 140

Explanation

Correct Answer

Incorrect Answers

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