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 42

Question 410

During an operational security assessment at a public-sector technology agency, the team documents this issue: Release jobs fail intermittently because agent pool capacity is exhausted at peak time. 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. Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments.
  2. Organize nonsecret pipeline variables with explicit stage scopes and authorized variable groups, avoiding accidental overrides and secret exposure.
  3. Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass.
  4. Implement multi-stage build, test, staging and production stages with immutable artifact promotion and environment-specific checks.
  5. Authorized projects run successfully on the approved pool while an unrelated project cannot schedule work or access saved files.

Explanation

Correct Answers

A:

Correct corrective action. Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments. The action targets the recorded failure (Release jobs fail intermittently because agent pool capacity is exhausted at peak time), and is intended to reduce the corresponding risk: Broadly shared or stale agents can expose deployment credentials and create unreliable software builds.

E:

Correct verification. Authorized projects run successfully on the approved pool while an unrelated project cannot schedule work or access saved files. The measurement or controlled test provides evidence for the issue (Release jobs fail intermittently because agent pool capacity is exhausted at peak time) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

B:

Organize nonsecret pipeline variables with explicit stage scopes and authorized variable groups, avoiding accidental overrides and secret exposure. This does not supply the required azure pipelines self-hosted agent pool security action-and-control pair.

C:

Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass. The paired controls concern azure pipelines self-hosted agent pool security, not that measure.

D:

Implement multi-stage build, test, staging and production stages with immutable artifact promotion and environment-specific checks. The azure pipelines self-hosted agent pool security implementation and safeguard are still missing.

Question 411

During an enterprise platform consolidation at a large software services provider, the team documents this issue: Azure Pipelines cannot start builds after a GitHub repository ownership transfer. 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. Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions.
  2. Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments.
  3. Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution.
  4. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior.

Explanation

Correct Answer

D:

Correct. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. The specific observed issue is: Azure Pipelines cannot start builds after a GitHub repository ownership transfer. The intervention addresses the azure pipelines github repository integration exposure, where misconfigured connections may build unapproved source or fail to respond to authorized changes and PR checks. After the change, acceptance should establish: A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.

Incorrect Answers

A:

Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions. That change would not implement azure pipelines GitHub repository integration.

B:

Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments. The configuration must instead establish azure pipelines GitHub repository integration.

C:

Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. The azure pipelines GitHub repository integration prerequisite remains unaddressed.

Question 412

During an enterprise platform consolidation at a large software services provider, the team documents this issue: Azure Pipelines cannot start builds after a GitHub repository ownership transfer. 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. The same digest moves from a green build through staging to a protected production environment with recorded approval.
  2. Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass.
  3. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.
  4. Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy.

Explanation

Correct Answer

C:

Correct. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories. This observable result is specific to the reported issue: Azure Pipelines cannot start builds after a GitHub repository ownership transfer. It checks the effectiveness of the proposed correction (Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

The same digest moves from a green build through staging to a protected production environment with recorded approval. Acceptance here depends on observing azure pipelines GitHub repository integration, not only that test.

B:

Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass. It does not establish the requested azure pipelines GitHub repository integration outcome.

D:

Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy. That result could pass without demonstrating azure pipelines GitHub repository integration.

Question 413

During a regulated production readiness review at a financial technology company, the team documents this issue: A service connection is granted all repositories when only one repository is needed. 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 explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions.
  2. Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments.
  3. Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution.
  4. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior.

Explanation

Correct Answer

D:

Correct. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. The specific observed issue is: A service connection is granted all repositories when only one repository is needed. The intervention addresses the azure pipelines github repository integration exposure, where misconfigured connections may build unapproved source or fail to respond to authorized changes and PR checks. After the change, acceptance should establish: A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.

Incorrect Answers

A:

Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions. The azure pipelines GitHub repository integration prerequisite remains unaddressed.

B:

Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments. It changes a different feature than azure pipelines GitHub repository integration.

C:

Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. That change would not implement azure pipelines GitHub repository integration.

Question 414

During a regulated production readiness review at a financial technology company, the team documents this issue: A service connection is granted all repositories when only one repository is needed. 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. Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass.
  2. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.
  3. Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy.
  4. The same digest moves from a green build through staging to a protected production environment with recorded approval.

Explanation

Correct Answer

B:

Correct. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories. This observable result is specific to the reported issue: A service connection is granted all repositories when only one repository is needed. It checks the effectiveness of the proposed correction (Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass. The relevant success criterion is azure pipelines GitHub repository integration; this measures a different function.

C:

Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy. Acceptance here depends on observing azure pipelines GitHub repository integration, not only that test.

D:

The same digest moves from a green build through staging to a protected production environment with recorded approval. It does not establish the requested azure pipelines GitHub repository integration outcome.

Question 415

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: Pull-request validation tests a different commit from the one proposed for merging. 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 restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments.
  2. Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions.
  3. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior.
  4. Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution.

Explanation

Correct Answer

C:

Correct. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. The specific observed issue is: Pull-request validation tests a different commit from the one proposed for merging. The intervention addresses the azure pipelines github repository integration exposure, where misconfigured connections may build unapproved source or fail to respond to authorized changes and PR checks. After the change, acceptance should establish: A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.

Incorrect Answers

A:

Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments. That result could pass without demonstrating azure pipelines GitHub repository integration.

B:

Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions. Acceptance here depends on observing azure pipelines GitHub repository integration, not only that test.

D:

Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. The relevant success criterion is azure pipelines GitHub repository integration; this measures a different function.

Question 416

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: Pull-request validation tests a different commit from the one proposed for merging. 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. Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy.
  2. The same digest moves from a green build through staging to a protected production environment with recorded approval.
  3. Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass.
  4. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.

Explanation

Correct Answer

D:

Correct. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories. This observable result is specific to the reported issue: Pull-request validation tests a different commit from the one proposed for merging. It checks the effectiveness of the proposed correction (Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy. Acceptance here depends on observing azure pipelines GitHub repository integration, not only that test.

B:

The same digest moves from a green build through staging to a protected production environment with recorded approval. It does not establish the requested azure pipelines GitHub repository integration outcome.

C:

Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass. The relevant success criterion is azure pipelines GitHub repository integration; this measures a different function.

Question 417

During a high-volume service modernization at a multinational retail group, the team documents this issue: The expected branch push does not trigger Azure Pipelines after webhook credentials rotate. 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 restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments.
  2. Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions.
  3. Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution.
  4. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior.

Explanation

Correct Answer

D:

Correct. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. The specific observed issue is: The expected branch push does not trigger Azure Pipelines after webhook credentials rotate. The intervention addresses the azure pipelines github repository integration exposure, where misconfigured connections may build unapproved source or fail to respond to authorized changes and PR checks. After the change, acceptance should establish: A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.

Incorrect Answers

A:

Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments. The azure pipelines GitHub repository integration prerequisite remains unaddressed.

B:

Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions. It changes a different feature than azure pipelines GitHub repository integration.

C:

Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. That change would not implement azure pipelines GitHub repository integration.

Question 418

During a high-volume service modernization at a multinational retail group, the team documents this issue: The expected branch push does not trigger Azure Pipelines after webhook credentials rotate. 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 reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.
  2. The same digest moves from a green build through staging to a protected production environment with recorded approval.
  3. Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass.
  4. Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy.

Explanation

Correct Answer

A:

Correct. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories. This observable result is specific to the reported issue: The expected branch push does not trigger Azure Pipelines after webhook credentials rotate. It checks the effectiveness of the proposed correction (Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

The same digest moves from a green build through staging to a protected production environment with recorded approval. That result could pass without demonstrating azure pipelines GitHub repository integration.

C:

Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass. Acceptance here depends on observing azure pipelines GitHub repository integration, not only that test.

D:

Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy. It does not establish the requested azure pipelines GitHub repository integration outcome.

Question 419

During an operational security assessment at a public-sector technology agency, the team documents this issue: An untrusted fork PR executes a deployment stage using production connection permissions. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Which consequence is MOST directly supported by these facts?

  1. Misconfigured connections may build unapproved source or fail to respond to authorized changes and PR checks.
  2. Broadly shared or stale agents can expose deployment credentials and create unreliable software builds.
  3. Rebuilding artifacts separately by environment allows unreviewed changes between tested and production releases.
  4. Incorrect filters can skip critical CI validation or waste resources on irrelevant changes.

Explanation

Correct Answer

A:

Correct. Misconfigured connections may build unapproved source or fail to respond to authorized changes and PR checks. This risk follows from the recorded condition: An untrusted fork PR executes a deployment stage using production connection permissions. The most relevant correction is configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

B:

Broadly shared or stale agents can expose deployment credentials and create unreliable software builds. The configuration must instead establish azure pipelines GitHub repository integration.

C:

Rebuilding artifacts separately by environment allows unreviewed changes between tested and production releases. The azure pipelines GitHub repository integration prerequisite remains unaddressed.

D:

Incorrect filters can skip critical CI validation or waste resources on irrelevant changes. It changes a different feature than azure pipelines GitHub repository integration.

Question 420

During an operational security assessment at a public-sector technology agency, the team documents this issue: An untrusted fork PR executes a deployment stage using production connection permissions. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Choose TWO statements that provide both the appropriate correction and a meaningful test of its success. (Select TWO.)

  1. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior.
  2. Implement multi-stage build, test, staging and production stages with immutable artifact promotion and environment-specific checks.
  3. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.
  4. Organize nonsecret pipeline variables with explicit stage scopes and authorized variable groups, avoiding accidental overrides and secret exposure.
  5. Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass.

Explanation

Correct Answers

A:

Correct corrective action. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. The action targets the recorded failure (An untrusted fork PR executes a deployment stage using production connection permissions), and is intended to reduce the corresponding risk: Misconfigured connections may build unapproved source or fail to respond to authorized changes and PR checks.

C:

Correct verification. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories. The measurement or controlled test provides evidence for the issue (An untrusted fork PR executes a deployment stage using production connection permissions) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

B:

Implement multi-stage build, test, staging and production stages with immutable artifact promotion and environment-specific checks. The azure pipelines GitHub repository integration implementation and safeguard are still missing.

D:

Organize nonsecret pipeline variables with explicit stage scopes and authorized variable groups, avoiding accidental overrides and secret exposure. This does not supply the required azure pipelines GitHub repository integration action-and-control pair.

E:

Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass. The two-part azure pipelines GitHub repository integration control remains unsatisfied.