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 17

Question 160

During an operational security assessment at a public-sector technology agency, the team documents this issue: An old Azure Repos project uses weaker approval rules than other production projects. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Select TWO: one corrective action and one test that confirms its effectiveness. (Select TWO.)

  1. Two independent features merge behind flags without visible unfinished behavior and can be released separately.
  2. Define a documented release-branch strategy with controlled hotfix propagation back to main and automated divergence checks.
  3. Configure Azure Repos branch policies for minimum reviewer count, linked work items and build validation on critical branches.
  4. A targeted PR cannot complete until reviewer and build policies pass and an associated work item is linked.
  5. Require pull-request review, current required status checks and ruleset protections for the protected default branch, limiting bypass authority.

Explanation

Correct Answers

C:

Correct corrective action. Configure Azure Repos branch policies for minimum reviewer count, linked work items and build validation on critical branches. The action targets the recorded failure (An old Azure Repos project uses weaker approval rules than other production projects), and is intended to reduce the corresponding risk: Inconsistent project branch policies make source review optional and disconnect changes from approved work.

D:

Correct verification. A targeted PR cannot complete until reviewer and build policies pass and an associated work item is linked. The measurement or controlled test provides evidence for the issue (An old Azure Repos project uses weaker approval rules than other production projects) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

Two independent features merge behind flags without visible unfinished behavior and can be released separately. The paired controls concern azure repos branch policies for reviewers, not that measure.

B:

Define a documented release-branch strategy with controlled hotfix propagation back to main and automated divergence checks. The azure repos branch policies for reviewers implementation and safeguard are still missing.

E:

Require pull-request review, current required status checks and ruleset protections for the protected default branch, limiting bypass authority. The two-part azure repos branch policies for reviewers control remains unsatisfied.

Question 161

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A machine learning test fixture is committed as a 500 MB binary for each minor revision. 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. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.
  2. Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos.
  3. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.
  4. Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure.

Explanation

Correct Answer

A:

Correct. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. The specific observed issue is: A machine learning test fixture is committed as a 500 MB binary for each minor revision. The intervention addresses the git lfs for large binary assets exposure, where large binary blobs inflate every clone and make source-control operations slow and expensive. After the change, acceptance should establish: Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.

Incorrect Answers

B:

Use partial clone and sparse-checkout or supported Scalar workflows to reduce download and working-tree cost for large monorepos. It changes a different feature than git lfs for large binary assets.

C:

Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. That change would not implement git lfs for large binary assets.

D:

Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure. The configuration must instead establish git lfs for large binary assets.

Question 162

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A machine learning test fixture is committed as a 500 MB binary for each minor revision. 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 external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants.
  2. A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change.
  3. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.
  4. A new developer checks out a targeted component with required history while repository transfer and disk use are reduced.

Explanation

Correct Answer

C:

Correct. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version. This observable result is specific to the reported issue: A machine learning test fixture is committed as a 500 MB binary for each minor revision. It checks the effectiveness of the proposed correction (Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

An external collaborator can propose a PR but cannot modify protection settings or protected branches; review logs match grants. The relevant success criterion is git lfs for large binary assets; this measures a different function.

B:

A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change. That result could pass without demonstrating git lfs for large binary assets.

D:

A new developer checks out a targeted component with required history while repository transfer and disk use are reduced. It does not establish the requested git lfs for large binary assets outcome.

Question 163

During a regulated production readiness review at a financial technology company, the team documents this issue: Git repository clones take twenty minutes because designers repeatedly add image binaries. 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. Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure.
  2. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.
  3. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.
  4. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.

Explanation

Correct Answer

D:

Correct. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. The specific observed issue is: Git repository clones take twenty minutes because designers repeatedly add image binaries. The intervention addresses the git lfs for large binary assets exposure, where large binary blobs inflate every clone and make source-control operations slow and expensive. After the change, acceptance should establish: Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.

Incorrect Answers

A:

Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure. That change would not implement git lfs for large binary assets.

B:

Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. The configuration must instead establish git lfs for large binary assets.

C:

Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. The git lfs for large binary assets prerequisite remains unaddressed.

Question 164

During a regulated production readiness review at a financial technology company, the team documents this issue: Git repository clones take twenty minutes because designers repeatedly add image binaries. 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 new developer checks out a targeted component with required history while repository transfer and disk use are reduced.
  2. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.
  3. A change to a protected deployment file requests the listed code owner and cannot merge until that review passes.
  4. A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change.

Explanation

Correct Answer

B:

Correct. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version. This observable result is specific to the reported issue: Git repository clones take twenty minutes because designers repeatedly add image binaries. It checks the effectiveness of the proposed correction (Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A new developer checks out a targeted component with required history while repository transfer and disk use are reduced. Acceptance here depends on observing git lfs for large binary assets, not only that test.

C:

A change to a protected deployment file requests the listed code owner and cannot merge until that review passes. The relevant success criterion is git lfs for large binary assets; this measures a different function.

D:

A release can be rebuilt from a pinned shared component revision and an approved upgrade produces a traceable dependency change. That result could pass without demonstrating git lfs for large binary assets.

Question 165

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A large SDK archive changes weekly and is tracked directly as ordinary Git objects. 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. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.
  2. Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required.
  3. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.
  4. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.

Explanation

Correct Answer

C:

Correct. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. The specific observed issue is: A large SDK archive changes weekly and is tracked directly as ordinary Git objects. The intervention addresses the git lfs for large binary assets exposure, where large binary blobs inflate every clone and make source-control operations slow and expensive. After the change, acceptance should establish: Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.

Incorrect Answers

A:

Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. It does not establish the requested git lfs for large binary assets outcome.

B:

Revoke and rotate exposed credentials immediately, then use approved history-rewrite tooling and coordinated cleanup where required. The relevant success criterion is git lfs for large binary assets; this measures a different function.

D:

Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. Acceptance here depends on observing git lfs for large binary assets, not only that test.

Question 166

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A large SDK archive changes weekly and is tracked directly as ordinary Git objects. 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. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.
  2. A new developer checks out a targeted component with required history while repository transfer and disk use are reduced.
  3. A change to a protected deployment file requests the listed code owner and cannot merge until that review passes.
  4. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.

Explanation

Correct Answer

A:

Correct. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version. This observable result is specific to the reported issue: A large SDK archive changes weekly and is tracked directly as ordinary Git objects. It checks the effectiveness of the proposed correction (Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

A new developer checks out a targeted component with required history while repository transfer and disk use are reduced. That result could pass without demonstrating git lfs for large binary assets.

C:

A change to a protected deployment file requests the listed code owner and cannot merge until that review passes. Acceptance here depends on observing git lfs for large binary assets, not only that test.

D:

A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value. It does not establish the requested git lfs for large binary assets outcome.

Question 167

During a high-volume service modernization at a multinational retail group, the team documents this issue: Developers delete a large binary from the tip but history remains bloated. 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. Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines.
  2. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.
  3. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.
  4. Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review.

Explanation

Correct Answer

B:

Correct. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. The specific observed issue is: Developers delete a large binary from the tip but history remains bloated. The intervention addresses the git lfs for large binary assets exposure, where large binary blobs inflate every clone and make source-control operations slow and expensive. After the change, acceptance should establish: Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.

Incorrect Answers

A:

Create protected signed or otherwise controlled release tags tied to deployed immutable commits and verify tag provenance in pipelines. That change would not implement git lfs for large binary assets.

C:

Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. The git lfs for large binary assets prerequisite remains unaddressed.

D:

Assign GitHub or Azure Repos repository roles at the minimum needed scope, with protected administrators and periodic access review. It changes a different feature than git lfs for large binary assets.

Question 168

During a high-volume service modernization at a multinational retail group, the team documents this issue: Developers delete a large binary from the tip but history remains bloated. 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 published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history.
  2. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.
  3. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.
  4. A change to a protected deployment file requests the listed code owner and cannot merge until that review passes.

Explanation

Correct Answer

C:

Correct. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version. This observable result is specific to the reported issue: Developers delete a large binary from the tip but history remains bloated. It checks the effectiveness of the proposed correction (Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A published defective commit is reversed by a traceable new commit while other collaborators can pull without repairing history. Acceptance here depends on observing git lfs for large binary assets, not only that test.

B:

A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value. It does not establish the requested git lfs for large binary assets outcome.

D:

A change to a protected deployment file requests the listed code owner and cannot merge until that review passes. That result could pass without demonstrating git lfs for large binary assets.

Question 169

During an operational security assessment at a public-sector technology agency, the team documents this issue: The team needs consistent versioned game assets without embedding them in every normal clone. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. If this issue remains unresolved, what is the PRIMARY DevOps risk?

  1. Moving a release tag after deployment breaks auditability, rollback and artifact-to-source correspondence.
  2. Excessive write permissions let unintended users alter protected code, policies or release workflows.
  3. Resetting shared history disrupts collaborators and can erase the audit trail of a production correction.
  4. Large binary blobs inflate every clone and make source-control operations slow and expensive.

Explanation

Correct Answer

D:

Correct. Large binary blobs inflate every clone and make source-control operations slow and expensive. This risk follows from the recorded condition: The team needs consistent versioned game assets without embedding them in every normal clone. The most relevant correction is move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Moving a release tag after deployment breaks auditability, rollback and artifact-to-source correspondence. That protection can exist while git lfs for large binary assets is still missing.

B:

Excessive write permissions let unintended users alter protected code, policies or release workflows. It protects a different risk than the git lfs for large binary assets requirement.

C:

Resetting shared history disrupts collaborators and can erase the audit trail of a production correction. It does not retain the git lfs for large binary assets control over time.

Question 170

During an operational security assessment at a public-sector technology agency, the team documents this issue: The team needs consistent versioned game assets without embedding them in every normal clone. 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 repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure.
  2. Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history.
  3. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies.
  4. A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value.
  5. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version.

Explanation

Correct Answers

C:

Correct corrective action. Move large versioned binary assets into Git LFS and enforce repository rules so normal Git history contains pointers rather than growing binary copies. The action targets the recorded failure (The team needs consistent versioned game assets without embedding them in every normal clone), and is intended to reduce the corresponding risk: Large binary blobs inflate every clone and make source-control operations slow and expensive.

E:

Correct verification. Fresh clones retrieve a small Git history and obtain the correct asset through LFS tracking, including a prior tagged version. The measurement or controlled test provides evidence for the issue (The team needs consistent versioned game assets without embedding them in every normal clone) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

Use repository CODEOWNERS rules with protected branch required code-owner reviews for sensitive paths such as deployment workflows and infrastructure. It is not the complementary risk control for git lfs for large binary assets.

B:

Use non-destructive git revert for changes already shared or deployed, and reserve reset or history rewriting for carefully controlled private history. This does not supply the required git lfs for large binary assets action-and-control pair.

D:

A rotated credential can no longer authenticate and repository history plus mirrors are inspected for the exposed value. The git lfs for large binary assets implementation and safeguard are still missing.