Microsoft AZ-400 Practice Test 19

Question 180

A second team blocks developers from pushing feature branches, causing changes to circulate as unreviewed ZIP files. Which unsupported assumption should the engineer challenge FIRST?

Resetting a local branch pointer does not safely undo a published change for every collaborator.
A reference to a moving shared branch does not guarantee repeatable pipeline behavior.
A sparse checkout cannot replace a permission boundary for files that users should not access.
Preventing developers from opening change branches can push work outside the reviewed source system.

Explanation

Correct Answer

Preventing developers from opening change branches can push work outside the reviewed source system. This is the relevant unsupported assumption because a safe branch strategy must balance collaborative change proposals with protected shared integration.

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: Preventing developers from opening change branches can push work outside the reviewed source system.

Question 181

A repository contains multi-gigabyte machine-learning model binaries that make every clone slow and break ordinary Git hosting limits. Which design or operational change MOST directly satisfies the requirement?

Adopt an explicit small-change integration policy using feature flags for incomplete behavior where appropriate.
Define a release/hotfix branch flow with reviewed back-merges or cherry-picks into supported branches.
Use short-lived branches and frequent validated integration to a protected main branch, with release controls separated from integration.
Store large binary assets in Git LFS with pointer files and manage access to the LFS object store.

Explanation

Correct Answer

Git LFS keeps large object payloads outside normal Git object history while retaining versioned references. The most directly responsive design or operational step is: Store large binary assets in Git LFS with pointer files and manage access to the LFS object store. Confirm the result by: Inspect Git pointer entries, LFS fetch behavior and clone size for a representative asset revision.

Incorrect Answers

Feature flags can decouple code integration from user exposure when defaults and cleanup are governed. The needed step here is to store large binary assets in Git LFS with pointer files and manage access to the LFS object store.

Long-lived maintenance lines require explicit propagation of fixes to prevent divergent defects. The appropriate remedy is to store large binary assets in Git LFS with pointer files and manage access to the LFS object store.

Trunk-based integration limits divergence and makes failures easier to attribute when tests run on each change. Instead, the response must store large binary assets in Git LFS with pointer files and manage access to the LFS object store.

Question 182

After the team applies this response: Store large binary assets in Git LFS with pointer files and manage access to the LFS object store. In the situation—A repository contains multi-gigabyte machine-learning model binaries that make every clone slow and break ordinary Git hosting limits. Which evidence BEST demonstrates the response is effective?

Inspect Git pointer entries, LFS fetch behavior and clone size for a representative asset revision.
Push a controlled change after approval and confirm merge is blocked until required new review completes.
Introduce a new commit or target update and confirm the policy requires a current successful validation run.
Attempt a merge with an unsigned commit and verify the protection rule and identity records reject it.

Explanation

Correct Answer

This evidence directly verifies the proposed control under the stated failure scenario: Inspect Git pointer entries, LFS fetch behavior and clone size for a representative asset revision. The governing engineering principle is: Git LFS keeps large object payloads outside normal Git object history while retaining versioned references.

Incorrect Answers

Approval integrity requires binding review decisions to the current content of the change, not an earlier version. The relevant control is to inspect Git pointer entries, LFS fetch behavior and clone size for a representative asset revision.

Merge gates must verify the code state that will be integrated, not a stale earlier validation. The needed step here is to inspect Git pointer entries, LFS fetch behavior and clone size for a representative asset revision.

Commit authenticity controls address provenance only when verified identities and enforcement are configured. The appropriate remedy is to inspect Git pointer entries, LFS fetch behavior and clone size for a representative asset revision.

Question 183

Another product commits large media assets directly into Git history and sees repository sizes grow on every revision. Which engineering principle BEST explains the relevant requirement?

Protected pull-request workflows enforce separation of duties only when enforcement and exceptions are controlled.
Approval integrity requires binding review decisions to the current content of the change, not an earlier version.
Git LFS keeps large object payloads outside normal Git object history while retaining versioned references.
Feature flags can decouple code integration from user exposure when defaults and cleanup are governed.

Explanation

Correct Answer

The second engineering situation illustrates the control boundary captured by this principle: Git LFS keeps large object payloads outside normal Git object history while retaining versioned references. The scenario is not resolved by an unrelated pipeline or policy activity.

Incorrect Answers

Protected pull-request workflows enforce separation of duties only when enforcement and exceptions are controlled. That principle concerns design and implement branching strategies for the source code, whereas this specific incident is governed by: Git LFS keeps large object payloads outside normal Git object history while retaining versioned references.

Approval integrity requires binding review decisions to the current content of the change, not an earlier version. That principle concerns design and implement branching strategies for the source code, whereas this specific incident is governed by: Git LFS keeps large object payloads outside normal Git object history while retaining versioned references.

Feature flags can decouple code integration from user exposure when defaults and cleanup are governed. That principle concerns design and implement branching strategies for the source code, whereas this specific incident is governed by: Git LFS keeps large object payloads outside normal Git object history while retaining versioned references.

Question 184

Another product commits large media assets directly into Git history and sees repository sizes grow on every revision. Which unsupported assumption should the engineer challenge FIRST?

Creating a permanent branch for every feature does not automatically reduce merge or release risk.
Adding .gitattributes after years of large commits does not automatically remove all prior binary blobs.
An urgent production issue does not by itself justify disabling all protected-branch rules.
Creating strict branch policies does not protect a repository when every contributor can disable them.

Explanation

Correct Answer

Adding .gitattributes after years of large commits does not automatically remove all prior binary blobs. This is the relevant unsupported assumption because git LFS keeps large object payloads outside normal Git object history while retaining versioned references.

Incorrect Answers

This caution is valid in design and implement branching strategies for the source code, but it is not the failure assumption illustrated by this scenario. The directly relevant risk is: Adding .gitattributes after years of large commits does not automatically remove all prior binary blobs.

Question 185

A monorepo with millions of files has unacceptable checkout times for developers working on a small component. Which design or operational change MOST directly satisfies the requirement?

Use short-lived branches and frequent validated integration to a protected main branch, with release controls separated from integration.
Scope administrative bypass and require documented exception approval with audit logging for protected branch overrides.
Restrict tag creation and update permissions and use protected or signed annotated release tags where supported.
Evaluate Scalar, sparse checkout or partial clone for large-repository performance and scope working trees appropriately.

Explanation

Correct Answer

Large repository optimizations reduce local data and work without necessarily changing source ownership boundaries. The most directly responsive design or operational step is: Evaluate Scalar, sparse checkout or partial clone for large-repository performance and scope working trees appropriately. Confirm the result by: Measure cold clone, checkout and fetch performance and validate required file visibility after configuration.

Incorrect Answers

Trunk-based integration limits divergence and makes failures easier to attribute when tests run on each change. Instead, the response must evaluate Scalar, sparse checkout or partial clone for large-repository performance and scope working trees appropriately.

Branch policy integrity depends on tightly limited bypass privileges and transparent exceptional use. The relevant control is to evaluate Scalar, sparse checkout or partial clone for large-repository performance and scope working trees appropriately.

Release labels are trustworthy only when the tagged revision and tag governance are controlled. The needed step here is to evaluate Scalar, sparse checkout or partial clone for large-repository performance and scope working trees appropriately.

Question 186

After the team applies this response: Evaluate Scalar, sparse checkout or partial clone for large-repository performance and scope working trees appropriately. In the situation—A monorepo with millions of files has unacceptable checkout times for developers working on a small component. Which evidence BEST demonstrates the response is effective?

Push a controlled change after approval and confirm merge is blocked until required new review completes.
Attempt an unapproved PR merge and inspect required checks, reviewer approvals and the ruleset bypass log.
Audit a security fix across affected maintenance branches and confirm relevant deployed versions include it.
Measure cold clone, checkout and fetch performance and validate required file visibility after configuration.

Explanation

Correct Answer

The governing engineering principle is: Large repository optimizations reduce local data and work without necessarily changing source ownership boundaries.

Incorrect Answers

Approval integrity requires binding review decisions to the current content of the change, not an earlier version. The appropriate remedy is to measure cold clone, checkout and fetch performance and validate required file visibility after configuration.

Protected pull-request workflows enforce separation of duties only when enforcement and exceptions are controlled. Instead, the response must measure cold clone, checkout and fetch performance and validate required file visibility after configuration.

Multi-version source support requires explicit patch propagation and documented branch retirement. The relevant control is to measure cold clone, checkout and fetch performance and validate required file visibility after configuration.

Question 187

Another enterprise wants to optimize Git operations without splitting a tightly coupled repository immediately. Which engineering principle BEST explains the relevant requirement?

Merge gates must verify the code state that will be integrated, not a stale earlier validation.
Protected pull-request workflows enforce separation of duties only when enforcement and exceptions are controlled.
An emergency workflow should shorten lead time without abandoning auditable source-control safeguards.
Large repository optimizations reduce local data and work without necessarily changing source ownership boundaries.

Explanation

Correct Answer

The second engineering situation illustrates the control boundary captured by this principle: Large repository optimizations reduce local data and work without necessarily changing source ownership boundaries. The scenario is not resolved by an unrelated pipeline or policy activity.

Incorrect Answers

Merge gates must verify the code state that will be integrated, not a stale earlier validation. That principle concerns design and implement branching strategies for the source code, whereas this specific incident is governed by: Large repository optimizations reduce local data and work without necessarily changing source ownership boundaries.

Protected pull-request workflows enforce separation of duties only when enforcement and exceptions are controlled. That principle concerns design and implement branching strategies for the source code, whereas this specific incident is governed by: Large repository optimizations reduce local data and work without necessarily changing source ownership boundaries.

An emergency workflow should shorten lead time without abandoning auditable source-control safeguards. That principle concerns design and implement branching strategies for the source code, whereas this specific incident is governed by: Large repository optimizations reduce local data and work without necessarily changing source ownership boundaries.

Question 188

Another enterprise wants to optimize Git operations without splitting a tightly coupled repository immediately. Which unsupported assumption should the engineer challenge FIRST?

A sparse checkout cannot replace a permission boundary for files that users should not access.
Preventing developers from opening change branches can push work outside the reviewed source system.
A patch merged into main does not automatically remediate an already supported older release.
Creating a permanent branch for every feature does not automatically reduce merge or release risk.

Explanation

Correct Answer

A sparse checkout cannot replace a permission boundary for files that users should not access. This is the relevant unsupported assumption because large repository optimizations reduce local data and work without necessarily changing source ownership boundaries.

Incorrect Answers

This caution is valid in design and implement branching strategies for the source code, but it is not the failure assumption illustrated by this scenario. The directly relevant risk is: A sparse checkout cannot replace a permission boundary for files that users should not access.

Question 189

Several service repositories copy the same infrastructure deployment templates and now differ in policy enforcement. Which design or operational change MOST directly satisfies the requirement?

Adopt an explicit small-change integration policy using feature flags for incomplete behavior where appropriate.
Enforce build validation on the current merge candidate and expire stale statuses after relevant source or target updates.
Capture the merge strategy, resulting commit identities and PR linkage in work and build records.
Use versioned shared template repositories or package sources with reviewed update and ownership workflows.

Explanation

Correct Answer

Shared repository assets should be reusable through versioned contracts rather than unmanaged copy-paste duplication. The most directly responsive design or operational step is: Use versioned shared template repositories or package sources with reviewed update and ownership workflows. Confirm the result by: Inspect consumers' pinned references and confirm a released template update can be adopted predictably.

Incorrect Answers

Feature flags can decouple code integration from user exposure when defaults and cleanup are governed. The needed step here is to use versioned shared template repositories or package sources with reviewed update and ownership workflows.

Merge gates must verify the code state that will be integrated, not a stale earlier validation. The appropriate remedy is to use versioned shared template repositories or package sources with reviewed update and ownership workflows.

Git merge strategies can change commit identity while preserving review provenance through stable PR references. Instead, the response must use versioned shared template repositories or package sources with reviewed update and ownership workflows.

Question 190

After the team applies this response: Use versioned shared template repositories or package sources with reviewed update and ownership workflows. In the situation—Several service repositories copy the same infrastructure deployment templates and now differ in policy enforcement. Which evidence BEST demonstrates the response is effective?

Review branch ages, merge history, test status and mainline stability across a recent release cycle.
Inspect consumers' pinned references and confirm a released template update can be adopted predictably.
Inspect a disabled feature's merge, guarded runtime behavior and subsequent enabled production release.
Attempt an unapproved PR merge and inspect required checks, reviewer approvals and the ruleset bypass log.

Explanation

Correct Answer

The governing engineering principle is: Shared repository assets should be reusable through versioned contracts rather than unmanaged copy-paste duplication.

Incorrect Answers

Trunk-based integration limits divergence and makes failures easier to attribute when tests run on each change. The relevant control is to inspect consumers' pinned references and confirm a released template update can be adopted predictably.

Feature flags can decouple code integration from user exposure when defaults and cleanup are governed. The needed step here is to inspect consumers' pinned references and confirm a released template update can be adopted predictably.

Protected pull-request workflows enforce separation of duties only when enforcement and exceptions are controlled. The appropriate remedy is to inspect consumers' pinned references and confirm a released template update can be adopted predictably.

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

Microsoft AZ-400 Practice Test 17 - 10 Questions (Last Reviewed 29-Oct-2026)
Microsoft AZ-400 Practice Test 18 - 10 Questions (Last Reviewed 28-Oct-2026)
Microsoft AZ-400 Practice Test 19 - 10 Questions (Last Reviewed 27-Oct-2026)
Microsoft AZ-400 Practice Test 20 - 10 Questions (Last Reviewed 26-Oct-2026)
Microsoft AZ-400 Practice Test 21 - 10 Questions (Last Reviewed 25-Oct-2026)

Pass Your Microsoft AZ-400 Exam Easy!

Question 180

Explanation

Correct Answer

Incorrect Answers

Question 181

Explanation

Correct Answer

Incorrect Answers

Question 182

Explanation

Correct Answer

Incorrect Answers

Question 183

Explanation

Correct Answer

Incorrect Answers

Question 184

Explanation

Correct Answer

Incorrect Answers

Question 185

Explanation

Correct Answer

Incorrect Answers

Question 186

Explanation

Correct Answer

Incorrect Answers

Question 187

Explanation

Correct Answer

Incorrect Answers

Question 188

Explanation

Correct Answer

Incorrect Answers

Question 189

Explanation

Correct Answer

Incorrect Answers

Question 190

Explanation

Correct Answer

Incorrect Answers

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