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 51

Question 500

During an operational security assessment at a public-sector technology agency, the team documents this issue: A deployment environment gate remains unresolved but a script proceeds using the service connection. 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. Centralize versioned YAML templates for mandatory security and build steps, and require tested template adoption for dependent pipelines.
  2. Configure Azure Pipelines environment approval checks and permitted branch controls at the protected resource, not only in editable pipeline YAML.
  3. Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions.
  4. The same digest moves from a green build through staging to a protected production environment with recorded approval.
  5. A release from an unapproved branch cannot consume production and a qualified approver authorizes a valid release before execution.

Explanation

Correct Answers

B:

Correct corrective action. Configure Azure Pipelines environment approval checks and permitted branch controls at the protected resource, not only in editable pipeline YAML. The action targets the recorded failure (A deployment environment gate remains unresolved but a script proceeds using the service connection), and is intended to reduce the corresponding risk: Authors can bypass YAML-only approval logic or deploy unauthorized branch content if the environment is unprotected.

E:

Correct verification. A release from an unapproved branch cannot consume production and a qualified approver authorizes a valid release before execution. The measurement or controlled test provides evidence for the issue (A deployment environment gate remains unresolved but a script proceeds using the service connection) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

Centralize versioned YAML templates for mandatory security and build steps, and require tested template adoption for dependent pipelines. The paired controls concern environment approval checks and branch controls, not that measure.

C:

Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions. It is not the complementary risk control for environment approval checks and branch controls.

D:

The same digest moves from a green build through staging to a protected production environment with recorded approval. This does not supply the required environment approval checks and branch controls action-and-control pair.

Question 501

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A hosted agent cannot connect to a database accessible only through a private endpoint. 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. Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments.
  2. Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions.
  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

B:

Correct. Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions. The specific observed issue is: A hosted agent cannot connect to a database accessible only through a private endpoint. The intervention addresses the hybrid agent networking and private endpoints exposure, where hosted agents cannot reliably reach private endpoints and ad hoc network exceptions increase attack surface. After the change, acceptance should establish: A job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity.

Incorrect Answers

A:

Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments. The hybrid agent networking and private endpoints prerequisite remains unaddressed.

C:

Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. That change would not implement hybrid agent networking and private endpoints.

D:

Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. The configuration must instead establish hybrid agent networking and private endpoints.

Question 502

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A hosted agent cannot connect to a database accessible only through a private endpoint. 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. Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy.
  3. A job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity.
  4. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.

Explanation

Correct Answer

C:

Correct. A job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity. This observable result is specific to the reported issue: A hosted agent cannot connect to a database accessible only through a private endpoint. It checks the effectiveness of the proposed correction (Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions.) 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. The relevant success criterion is hybrid agent networking and private endpoints; this measures a different function.

B:

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 hybrid agent networking and private endpoints.

D:

A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories. It does not establish the requested hybrid agent networking and private endpoints outcome.

Question 503

During a regulated production readiness review at a financial technology company, the team documents this issue: Engineers open a production database to the public internet to let CI jobs run migrations. 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. Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions.
  2. Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution.
  3. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior.
  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. Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions. The specific observed issue is: Engineers open a production database to the public internet to let CI jobs run migrations. The intervention addresses the hybrid agent networking and private endpoints exposure, where hosted agents cannot reliably reach private endpoints and ad hoc network exceptions increase attack surface. After the change, acceptance should establish: A job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity.

Incorrect Answers

B:

Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. The configuration must instead establish hybrid agent networking and private endpoints.

C:

Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. The hybrid agent networking and private endpoints prerequisite remains unaddressed.

D:

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 hybrid agent networking and private endpoints.

Question 504

During a regulated production readiness review at a financial technology company, the team documents this issue: Engineers open a production database to the public internet to let CI jobs run migrations. 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 reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.
  2. Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy.
  3. A job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity.
  4. The same digest moves from a green build through staging to a protected production environment with recorded approval.

Explanation

Correct Answer

C:

Correct. A job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity. This observable result is specific to the reported issue: Engineers open a production database to the public internet to let CI jobs run migrations. It checks the effectiveness of the proposed correction (Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories. Acceptance here depends on observing hybrid agent networking and private endpoints, not only that test.

B:

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 hybrid agent networking and private endpoints outcome.

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 hybrid agent networking and private endpoints.

Question 505

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A Kubernetes build requires an internal artifact server but public runners cannot route to it. 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. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior.
  3. Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions.
  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. Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions. The specific observed issue is: A Kubernetes build requires an internal artifact server but public runners cannot route to it. The intervention addresses the hybrid agent networking and private endpoints exposure, where hosted agents cannot reliably reach private endpoints and ad hoc network exceptions increase attack surface. After the change, acceptance should establish: A job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity.

Incorrect Answers

A:

Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments. It does not establish the requested hybrid agent networking and private endpoints outcome.

B:

Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. The relevant success criterion is hybrid agent networking and private endpoints; this measures a different function.

D:

Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. Acceptance here depends on observing hybrid agent networking and private endpoints, not only that test.

Question 506

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A Kubernetes build requires an internal artifact server but public runners cannot route to it. 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. A job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity.
  2. Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy.
  3. The same digest moves from a green build through staging to a protected production environment with recorded approval.
  4. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.

Explanation

Correct Answer

A:

Correct. A job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity. This observable result is specific to the reported issue: A Kubernetes build requires an internal artifact server but public runners cannot route to it. It checks the effectiveness of the proposed correction (Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

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 hybrid agent networking and private endpoints.

C:

The same digest moves from a green build through staging to a protected production environment with recorded approval. Acceptance here depends on observing hybrid agent networking and private endpoints, not only that test.

D:

A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories. It does not establish the requested hybrid agent networking and private endpoints outcome.

Question 507

During a high-volume service modernization at a multinational retail group, the team documents this issue: A self-hosted runner can reach every corporate subnet though it only needs one release endpoint. 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. Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior.
  3. Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions.
  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. Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions. The specific observed issue is: A self-hosted runner can reach every corporate subnet though it only needs one release endpoint. The intervention addresses the hybrid agent networking and private endpoints exposure, where hosted agents cannot reliably reach private endpoints and ad hoc network exceptions increase attack surface. After the change, acceptance should establish: A job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity.

Incorrect Answers

A:

Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments. That change would not implement hybrid agent networking and private endpoints.

B:

Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. The configuration must instead establish hybrid agent networking and private endpoints.

D:

Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. It changes a different feature than hybrid agent networking and private endpoints.

Question 508

During a high-volume service modernization at a multinational retail group, the team documents this issue: A self-hosted runner can reach every corporate subnet though it only needs one release endpoint. 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 job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity.
  2. Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy.
  3. The same digest moves from a green build through staging to a protected production environment with recorded approval.
  4. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.

Explanation

Correct Answer

A:

Correct. A job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity. This observable result is specific to the reported issue: A self-hosted runner can reach every corporate subnet though it only needs one release endpoint. It checks the effectiveness of the proposed correction (Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

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 hybrid agent networking and private endpoints outcome.

C:

The same digest moves from a green build through staging to a protected production environment with recorded approval. The relevant success criterion is hybrid agent networking and private endpoints; this measures a different function.

D:

A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories. That result could pass without demonstrating hybrid agent networking and private endpoints.

Question 509

During an operational security assessment at a public-sector technology agency, the team documents this issue: Deployment fails in a hybrid environment because DNS resolution differs between hosted and private agents. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Why is the current implementation not a reliable control?

  1. Incorrect filters can skip critical CI validation or waste resources on irrelevant changes.
  2. Broadly shared or stale agents can expose deployment credentials and create unreliable software builds.
  3. Hosted agents cannot reliably reach private endpoints and ad hoc network exceptions increase attack surface.
  4. Misconfigured connections may build unapproved source or fail to respond to authorized changes and PR checks.

Explanation

Correct Answer

C:

Correct. Hosted agents cannot reliably reach private endpoints and ad hoc network exceptions increase attack surface. This risk follows from the recorded condition: Deployment fails in a hybrid environment because DNS resolution differs between hosted and private agents. The most relevant correction is place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Incorrect filters can skip critical CI validation or waste resources on irrelevant changes. The hybrid agent networking and private endpoints prerequisite remains unaddressed.

B:

Broadly shared or stale agents can expose deployment credentials and create unreliable software builds. It changes a different feature than hybrid agent networking and private endpoints.

D:

Misconfigured connections may build unapproved source or fail to respond to authorized changes and PR checks. The configuration must instead establish hybrid agent networking and private endpoints.

Question 510

During an operational security assessment at a public-sector technology agency, the team documents this issue: Deployment fails in a hybrid environment because DNS resolution differs between hosted and private agents. 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. Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions.
  2. The same digest moves from a green build through staging to a protected production environment with recorded approval.
  3. Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions.
  4. A job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity.
  5. Centralize versioned YAML templates for mandatory security and build steps, and require tested template adoption for dependent pipelines.

Explanation

Correct Answers

A:

Correct corrective action. Place approved private-network agents or runners where they can securely reach required internal services, with firewall rules and identity restrictions. The action targets the recorded failure (Deployment fails in a hybrid environment because DNS resolution differs between hosted and private agents), and is intended to reduce the corresponding risk: Hosted agents cannot reliably reach private endpoints and ad hoc network exceptions increase attack surface.

D:

Correct verification. A job on the approved network-reachable agent can reach only authorized private dependencies and completes the deployment with recorded identity. The measurement or controlled test provides evidence for the issue (Deployment fails in a hybrid environment because DNS resolution differs between hosted and private agents) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

B:

The same digest moves from a green build through staging to a protected production environment with recorded approval. This does not supply the required hybrid agent networking and private endpoints action-and-control pair.

C:

Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions. The paired controls concern hybrid agent networking and private endpoints, not that measure.

E:

Centralize versioned YAML templates for mandatory security and build steps, and require tested template adoption for dependent pipelines. The two-part hybrid agent networking and private endpoints control remains unsatisfied.