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 52

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.

Question 511

During an enterprise platform consolidation at a large software services provider, the team documents this issue: Builds reuse stale dependencies after package-lock.json changes. 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. 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. Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs.

Explanation

Correct Answer

D:

Correct. Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs. The specific observed issue is: Builds reuse stale dependencies after package-lock.json changes. The intervention addresses the pipeline caching and artifact identity exposure, where overbroad cache reuse can serve stale dependencies and confuse cache optimization with release artifact integrity. After the change, acceptance should establish: A changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum.

Incorrect Answers

A:

Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. That change would not implement pipeline caching and artifact identity.

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 pipeline caching and artifact identity.

C:

Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. The pipeline caching and artifact identity prerequisite remains unaddressed.

Question 512

During an enterprise platform consolidation at a large software services provider, the team documents this issue: Builds reuse stale dependencies after package-lock.json changes. 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 changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum.
  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 changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum. This observable result is specific to the reported issue: Builds reuse stale dependencies after package-lock.json changes. It checks the effectiveness of the proposed correction (Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs.) 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 pipeline caching and artifact identity, 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 pipeline caching and artifact identity outcome.

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 pipeline caching and artifact identity.

Question 513

During a regulated production readiness review at a financial technology company, the team documents this issue: A pipeline caches compiled binaries across incompatible runtime versions. 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. Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution.
  2. Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs.
  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

B:

Correct. Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs. The specific observed issue is: A pipeline caches compiled binaries across incompatible runtime versions. The intervention addresses the pipeline caching and artifact identity exposure, where overbroad cache reuse can serve stale dependencies and confuse cache optimization with release artifact integrity. After the change, acceptance should establish: A changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum.

Incorrect Answers

A:

Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. The pipeline caching and artifact identity 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 pipeline caching and artifact identity.

D:

Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments. The configuration must instead establish pipeline caching and artifact identity.

Question 514

During a regulated production readiness review at a financial technology company, the team documents this issue: A pipeline caches compiled binaries across incompatible runtime versions. 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. Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy.
  2. A changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum.
  3. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.
  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 changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum. This observable result is specific to the reported issue: A pipeline caches compiled binaries across incompatible runtime versions. It checks the effectiveness of the proposed correction (Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs.) 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. The relevant success criterion is pipeline caching and artifact identity; this measures a different function.

C:

A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories. Acceptance here depends on observing pipeline caching and artifact identity, 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 pipeline caching and artifact identity outcome.

Question 515

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: Production deployment accidentally consumes a dependency cache instead of a reviewed release artifact. 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. Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution.
  4. Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs.

Explanation

Correct Answer

D:

Correct. Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs. The specific observed issue is: Production deployment accidentally consumes a dependency cache instead of a reviewed release artifact. The intervention addresses the pipeline caching and artifact identity exposure, where overbroad cache reuse can serve stale dependencies and confuse cache optimization with release artifact integrity. After the change, acceptance should establish: A changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum.

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 pipeline caching and artifact identity.

B:

Configure the approved GitHub service connection or application integration for Azure Pipelines with restricted repository access and trigger behavior. Acceptance here depends on observing pipeline caching and artifact identity, not only that test.

C:

Provision self-hosted GitHub Actions runners with controlled network access, ephemeral job environments and restrictions on untrusted workflow execution. It does not establish the requested pipeline caching and artifact identity outcome.

Question 516

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: Production deployment accidentally consumes a dependency cache instead of a reviewed release artifact. 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 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. Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy.
  4. A changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum.

Explanation

Correct Answer

D:

Correct. A changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum. This observable result is specific to the reported issue: Production deployment accidentally consumes a dependency cache instead of a reviewed release artifact. It checks the effectiveness of the proposed correction (Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs.) 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 pipeline caching and artifact identity, 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 pipeline caching and artifact identity outcome.

C:

Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy. The relevant success criterion is pipeline caching and artifact identity; this measures a different function.

Question 517

During a high-volume service modernization at a multinational retail group, the team documents this issue: An agent cache is poisoned by a low-trust PR and later used by a privileged release. 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. Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs.
  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. Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs. The specific observed issue is: An agent cache is poisoned by a low-trust PR and later used by a privileged release. The intervention addresses the pipeline caching and artifact identity exposure, where overbroad cache reuse can serve stale dependencies and confuse cache optimization with release artifact integrity. After the change, acceptance should establish: A changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum.

Incorrect Answers

B:

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 pipeline caching and artifact identity.

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 pipeline caching and artifact identity.

D:

Create restricted Azure Pipelines agent pools with managed software images, network access and project authorization scoped to required deployments. The configuration must instead establish pipeline caching and artifact identity.

Question 518

During a high-volume service modernization at a multinational retail group, the team documents this issue: An agent cache is poisoned by a low-trust PR and later used by a privileged release. 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. The same digest moves from a green build through staging to a protected production environment with recorded approval.
  2. A changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum.
  3. Changes to a relevant source path trigger CI while documentation-only changes and disallowed branches follow the documented policy.
  4. A reviewed PR starts the expected pipeline with the exact source revision and cannot access unrelated private repositories.

Explanation

Correct Answer

B:

Correct. A changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum. This observable result is specific to the reported issue: An agent cache is poisoned by a low-trust PR and later used by a privileged release. It checks the effectiveness of the proposed correction (Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs.) 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 pipeline caching and artifact identity; 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 pipeline caching and artifact identity, 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 pipeline caching and artifact identity outcome.

Question 519

During an operational security assessment at a public-sector technology agency, the team documents this issue: Cache cleanup purges an artifact needed for an authorized rollback. 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. Overbroad cache reuse can serve stale dependencies and confuse cache optimization with release artifact integrity.
  2. Misconfigured connections may build unapproved source or fail to respond to authorized changes and PR checks.
  3. Incorrect filters can skip critical CI validation or waste resources on irrelevant changes.
  4. Broadly shared or stale agents can expose deployment credentials and create unreliable software builds.

Explanation

Correct Answer

A:

Correct. Overbroad cache reuse can serve stale dependencies and confuse cache optimization with release artifact integrity. This risk follows from the recorded condition: Cache cleanup purges an artifact needed for an authorized rollback. The most relevant correction is configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

B:

Misconfigured connections may build unapproved source or fail to respond to authorized changes and PR checks. Recurrence here depends on pipeline caching and artifact identity, not this safeguard.

C:

Incorrect filters can skip critical CI validation or waste resources on irrelevant changes. That protection can exist while pipeline caching and artifact identity is still missing.

D:

Broadly shared or stale agents can expose deployment credentials and create unreliable software builds. It protects a different risk than the pipeline caching and artifact identity requirement.

Question 520

During an operational security assessment at a public-sector technology agency, the team documents this issue: Cache cleanup purges an artifact needed for an authorized rollback. 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. Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs.
  2. The same digest moves from a green build through staging to a protected production environment with recorded approval.
  3. Centralize versioned YAML templates for mandatory security and build steps, and require tested template adoption for dependent pipelines.
  4. A changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum.
  5. Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions.

Explanation

Correct Answers

A:

Correct corrective action. Configure dependency caches keyed by immutable lockfile and toolchain inputs while using signed or hashed artifacts for promoted release outputs. The action targets the recorded failure (Cache cleanup purges an artifact needed for an authorized rollback), and is intended to reduce the corresponding risk: Overbroad cache reuse can serve stale dependencies and confuse cache optimization with release artifact integrity.

D:

Correct verification. A changed dependency lockfile causes a cache miss and subsequent builds reproduce the expected package checksum. The measurement or controlled test provides evidence for the issue (Cache cleanup purges an artifact needed for an authorized rollback) 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. The pipeline caching and artifact identity implementation and safeguard are still missing.

C:

Centralize versioned YAML templates for mandatory security and build steps, and require tested template adoption for dependent pipelines. It is not the complementary risk control for pipeline caching and artifact identity.

E:

Use explicit branch and path trigger filters with tested PR triggers so only relevant changes run the intended pipeline actions. The two-part pipeline caching and artifact identity control remains unsatisfied.