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 40

Question 390

During an operational security assessment at a public-sector technology agency, the team documents this issue: Platform owners cannot explain how the selected CI service supports required private network access. 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. Implement multi-stage build, test, staging and production stages with immutable artifact promotion and environment-specific checks.
  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. Select GitHub Actions or Azure Pipelines based on repository integration, deployment resources, governance controls, runner availability and required support.
  5. A representative pipeline on the selected platform meets checkout, testing, secure deployment and audit-trail requirements end to end.

Explanation

Correct Answers

D:

Correct corrective action. Select GitHub Actions or Azure Pipelines based on repository integration, deployment resources, governance controls, runner availability and required support. The action targets the recorded failure (Platform owners cannot explain how the selected CI service supports required private network access), and is intended to reduce the corresponding risk: Choosing an automation platform solely by familiarity can omit necessary approvals, identity and environment capabilities.

E:

Correct verification. A representative pipeline on the selected platform meets checkout, testing, secure deployment and audit-trail requirements end to end. The measurement or controlled test provides evidence for the issue (Platform owners cannot explain how the selected CI service supports required private network access) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

Implement multi-stage build, test, staging and production stages with immutable artifact promotion and environment-specific checks. It is not the complementary risk control for GitHub actions versus azure pipelines platform choice.

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 GitHub actions versus azure pipelines platform choice 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 GitHub actions versus azure pipelines platform choice, not that measure.

Question 391

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A public repository PR executes arbitrary code on a runner with production network access. 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

C:

Correct. Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. The specific observed issue is: A public repository PR executes arbitrary code on a runner with production network access. The intervention addresses the github actions self-hosted runner isolation exposure, where untrusted code may access runner credentials, internal networks or residual build data when execution is insufficiently isolated. After the change, acceptance should establish: An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files.

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 GitHub actions self-hosted runner isolation.

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 GitHub actions self-hosted runner isolation.

D:

Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. It changes a different feature than GitHub actions self-hosted runner isolation.

Question 392

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A public repository PR executes arbitrary code on a runner with production network access. 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. Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass.
  2. An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files.
  3. The same digest moves from a green build through staging to a protected production environment with recorded approval.
  4. Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy.

Explanation

Correct Answer

B:

Correct. An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files. This observable result is specific to the reported issue: A public repository PR executes arbitrary code on a runner with production network access. It checks the effectiveness of the proposed correction (Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution.) 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. Acceptance here depends on observing GitHub actions self-hosted runner isolation, not only that test.

C:

The same digest moves from a green build through staging to a protected production environment with recorded approval. The relevant success criterion is GitHub actions self-hosted runner isolation; this measures a different function.

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 GitHub actions self-hosted runner isolation.

Question 393

During a regulated production readiness review at a financial technology company, the team documents this issue: A self-hosted runner retains deployment tokens in its workspace between jobs. 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. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior.
  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. Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions.

Explanation

Correct Answer

C:

Correct. Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. The specific observed issue is: A self-hosted runner retains deployment tokens in its workspace between jobs. The intervention addresses the github actions self-hosted runner isolation exposure, where untrusted code may access runner credentials, internal networks or residual build data when execution is insufficiently isolated. After the change, acceptance should establish: An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files.

Incorrect Answers

A:

Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. The GitHub actions self-hosted runner isolation 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 GitHub actions self-hosted runner isolation.

D:

Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions. The configuration must instead establish GitHub actions self-hosted runner isolation.

Question 394

During a regulated production readiness review at a financial technology company, the team documents this issue: A self-hosted runner retains deployment tokens in its workspace between jobs. 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. An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files.
  2. The same digest moves from a green build through staging to a protected production environment with recorded approval.
  3. Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy.
  4. Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass.

Explanation

Correct Answer

A:

Correct. An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files. This observable result is specific to the reported issue: A self-hosted runner retains deployment tokens in its workspace between jobs. It checks the effectiveness of the proposed correction (Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution.) 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 GitHub actions self-hosted runner isolation.

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 GitHub actions self-hosted runner isolation, not only that test.

D:

Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass. It does not establish the requested GitHub actions self-hosted runner isolation outcome.

Question 395

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

Explanation

Correct Answer

A:

Correct. Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. The specific observed issue is: A runner group permits every repository to schedule jobs on sensitive build machines. The intervention addresses the github actions self-hosted runner isolation exposure, where untrusted code may access runner credentials, internal networks or residual build data when execution is insufficiently isolated. After the change, acceptance should establish: An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files.

Incorrect Answers

B:

Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments. Acceptance here depends on observing GitHub actions self-hosted runner isolation, not only that test.

C:

Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions. It does not establish the requested GitHub actions self-hosted runner isolation outcome.

D:

Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. The relevant success criterion is GitHub actions self-hosted runner isolation; this measures a different function.

Question 396

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A runner group permits every repository to schedule jobs on sensitive build machines. 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. An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files.
  3. Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass.
  4. The same digest moves from a green build through staging to a protected production environment with recorded approval.

Explanation

Correct Answer

B:

Correct. An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files. This observable result is specific to the reported issue: A runner group permits every repository to schedule jobs on sensitive build machines. It checks the effectiveness of the proposed correction (Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution.) 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 GitHub actions self-hosted runner isolation, not only that test.

C:

Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass. The relevant success criterion is GitHub actions self-hosted runner isolation; this measures a different function.

D:

The same digest moves from a green build through staging to a protected production environment with recorded approval. That result could pass without demonstrating GitHub actions self-hosted runner isolation.

Question 397

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

Explanation

Correct Answer

A:

Correct. Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. The specific observed issue is: A compromised build container can inspect host credentials because isolation is weak. The intervention addresses the github actions self-hosted runner isolation exposure, where untrusted code may access runner credentials, internal networks or residual build data when execution is insufficiently isolated. After the change, acceptance should establish: An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files.

Incorrect Answers

B:

Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. This observation would miss the actual GitHub actions self-hosted runner isolation fault.

C:

Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions. That evidence would not isolate GitHub actions self-hosted runner isolation.

D:

Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments. The decisive diagnostic evidence must instead cover GitHub actions self-hosted runner isolation.

Question 398

During a high-volume service modernization at a multinational retail group, the team documents this issue: A compromised build container can inspect host credentials because isolation is weak. 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. Two consuming repositories adopt a reviewed template version and execute the same mandatory control without local bypass.
  2. An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files.
  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. An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files. This observable result is specific to the reported issue: A compromised build container can inspect host credentials because isolation is weak. It checks the effectiveness of the proposed correction (Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution.) 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 GitHub actions self-hosted runner isolation; 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 GitHub actions self-hosted runner isolation, 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 GitHub actions self-hosted runner isolation outcome.

Question 399

During an operational security assessment at a public-sector technology agency, the team documents this issue: Critical pipelines queue behind unreliable shared runners without capacity controls. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Which risk statement BEST explains the problem described?

  1. Rebuilding artifacts separately by environment allows unreviewed changes between tested and production releases.
  2. Untrusted code may access runner credentials, internal networks or residual build data when execution is insufficiently isolated.
  3. Incorrect filters can skip critical CI validation or waste resources on irrelevant changes.
  4. Misconfigured connections may build unapproved source or fail to respond to authorized changes and PR checks.

Explanation

Correct Answer

B:

Correct. Untrusted code may access runner credentials, internal networks or residual build data when execution is insufficiently isolated. This risk follows from the recorded condition: Critical pipelines queue behind unreliable shared runners without capacity controls. The most relevant correction is provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Rebuilding artifacts separately by environment allows unreviewed changes between tested and production releases. It does not retain the GitHub actions self-hosted runner isolation control over time.

C:

Incorrect filters can skip critical CI validation or waste resources on irrelevant changes. That protection can exist while GitHub actions self-hosted runner isolation is still missing.

D:

Misconfigured connections may build unapproved source or fail to respond to authorized changes and PR checks. It protects a different risk than the GitHub actions self-hosted runner isolation requirement.

Question 400

During an operational security assessment at a public-sector technology agency, the team documents this issue: Critical pipelines queue behind unreliable shared runners without capacity controls. 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. Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution.
  2. Organize nonsecret pipeline variables with explicit stage scopes and authorized variable groups, avoiding accidental overrides and secret exposure.
  3. An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files.
  4. Implement multi-stage build, test, staging and production stages with immutable artifact promotion and environment-specific checks.
  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. Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. The action targets the recorded failure (Critical pipelines queue behind unreliable shared runners without capacity controls), and is intended to reduce the corresponding risk: Untrusted code may access runner credentials, internal networks or residual build data when execution is insufficiently isolated.

C:

Correct verification. An untrusted fork workflow cannot reach protected runner resources and a new job has no leftover secrets or workspace files. The measurement or controlled test provides evidence for the issue (Critical pipelines queue behind unreliable shared runners without capacity controls) 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. The GitHub actions self-hosted runner isolation implementation and safeguard are still missing.

D:

Implement multi-stage build, test, staging and production stages with immutable artifact promotion and environment-specific checks. This does not supply the required GitHub actions self-hosted runner isolation 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 GitHub actions self-hosted runner isolation control remains unsatisfied.