Microsoft AZ-400 Practice Test 33

Question 320

A security investigation cannot retrieve the container image that ran during a payment incident from last quarter. Choose TWO measures that implement and verify an effective Azure DevOps response to this specific situation. (Choose TWO.)

Define version-specific artifact retention and immutable references aligned to recovery and evidence requirements.
Declare build artifact retention and reproducible rollback windows successful solely from a green pipeline status and skip checking its actual control outcome.
Bypass review and testing for build artifact retention and reproducible rollback windows whenever the release deadline is urgent, applying the change to production immediately.
Dismiss the known risk for build artifact retention and reproducible rollback windows and keep no evidence or accountable owner after deployment.
Retrieve an archived release and validate its digest, access history, and ability to deploy into a safe test environment.

Explanation

Correct Answers

A:

Define version-specific artifact retention and immutable references aligned to recovery and evidence requirements. A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log. Premature artifact deletion can make incident reconstruction and safe restoration impossible.

E:

Retrieve an archived release and validate its digest, access history, and ability to deploy into a safe test environment. A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log.

Incorrect Answers

B:

Declare build artifact retention and reproducible rollback windows successful solely from a green pipeline status and skip checking its actual control outcome. It conflicts with the stated operating condition: A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log.

C:

Bypass review and testing for build artifact retention and reproducible rollback windows whenever the release deadline is urgent, applying the change to production immediately. It conflicts with the stated operating condition: A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log.

D:

Dismiss the known risk for build artifact retention and reproducible rollback windows and keep no evidence or accountable owner after deployment. It conflicts with the stated operating condition: A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log.

Question 321

Developers merge a broken tax calculation because unit tests run only nightly after the protected branch has changed. Which solution should be prioritized to resolve the stated failure?

Choose agents with required capabilities and publish authenticated, machine-readable test results as release-gate evidence.
Run deterministic unit tests as required pull-request checks and fail the merge or promotion on genuine test failure.
Run integration tests against provisioned test dependencies with controlled identities, seeded data, and predictable cleanup.
Define representative postdeployment smoke tests and make their results a required environment promotion check.

Explanation

Correct Answer

B:

Run deterministic unit tests as required pull-request checks and fail the merge or promotion on genuine test failure. Fast code-level tests detect known regressions only if their failure status controls integration. An apparently successful build can ship a defect already revealed by automated unit tests.

Incorrect Answers

A:

Choose agents with required capabilities and publish authenticated, machine-readable test results as release-gate evidence.

C:

Run integration tests against provisioned test dependencies with controlled identities, seeded data, and predictable cleanup.

D:

Define representative postdeployment smoke tests and make their results a required environment promotion check.

Question 322

Developers merge a broken tax calculation because unit tests run only nightly after the protected branch has changed. Which evidence would BEST demonstrate that the fix operates as intended?

Introduce a known failing assertion in a test branch and verify the required check blocks merge.
Re-run a platform-specific test and verify the expected agent image, test totals, failures, and output artifacts are recorded.
Inspect line and branch coverage for the altered code and confirm failing edge cases are represented by tests.
Deploy a controlled faulty revision and verify the rollout gate blocks approval or initiates defined rollback behavior.

Explanation

Correct Answer

A:

Introduce a known failing assertion in a test branch and verify the required check blocks merge. Fast code-level tests detect known regressions only if their failure status controls integration.

Incorrect Answers

B:

Re-run a platform-specific test and verify the expected agent image, test totals, failures, and output artifacts are recorded.

C:

Inspect line and branch coverage for the altered code and confirm failing edge cases are represented by tests.

D:

Deploy a controlled faulty revision and verify the rollout gate blocks approval or initiates defined rollback behavior.

Question 323

Developers merge a broken tax calculation because unit tests run only nightly after the protected branch has changed. Which DevOps implementation principle BEST explains the issue?

Fast code-level tests detect known regressions only if their failure status controls integration.
A successful job exit does not establish coverage when tests may have been skipped or results dropped.
A headline coverage percentage is insufficient unless it measures relevant code and behavior.
Unit tests cannot prove correctness at remote service and serialization boundaries.

Explanation

Correct Answer

A:

Fast code-level tests detect known regressions only if their failure status controls integration. An apparently successful build can ship a defect already revealed by automated unit tests.

Incorrect Answers

B:

A successful job exit does not establish coverage when tests may have been skipped or results dropped.

C:

A headline coverage percentage is insufficient unless it measures relevant code and behavior.

D:

Unit tests cannot prove correctness at remote service and serialization boundaries.

Question 324

Developers merge a broken tax calculation because unit tests run only nightly after the protected branch has changed. What preventive practice should be maintained after the fix?

Maintain smoke-test coverage of top user journeys and retest gates after dependency changes.
Protect test workflows and review skipped or disabled test gates when pipeline configuration changes.
Version test-environment definitions and refresh contract fixtures after upstream API changes.
Monitor agent image drift and alert when expected test counts or reporting artifacts disappear.

Explanation

Correct Answer

B:

Protect test workflows and review skipped or disabled test gates when pipeline configuration changes. An apparently successful build can ship a defect already revealed by automated unit tests.

Incorrect Answers

A:

Maintain smoke-test coverage of top user journeys and retest gates after dependency changes.

C:

Version test-environment definitions and refresh contract fixtures after upstream API changes.

D:

Monitor agent image drift and alert when expected test counts or reporting artifacts disappear.

Question 325

Developers merge a broken tax calculation because unit tests run only nightly after the protected branch has changed. What outcome most clearly explains the business impact?

An apparently successful service rollout may interrupt customers still using supported older clients.
A faulty build can be promoted simply because its infrastructure reported healthy.
An apparently successful build can ship a defect already revealed by automated unit tests.
A release may break at runtime even though each individual code module passed its unit tests.

Explanation

Correct Answer

C:

An apparently successful build can ship a defect already revealed by automated unit tests. This is the directly relevant business or security consequence of pull-request unit tests gating azure pipelines builds. Root cause: Fast code-level tests detect known regressions only if their failure status controls integration.

Incorrect Answers

A:

An apparently successful service rollout may interrupt customers still using supported older clients. That risk is relevant to consumer-driven api contract compatibility testing, but the specific unresolved condition here concerns pull-request unit tests gating azure pipelines builds and has a different direct consequence.

B:

A faulty build can be promoted simply because its infrastructure reported healthy. That risk is relevant to staging smoke tests as environment approval gates, but the specific unresolved condition here concerns pull-request unit tests gating azure pipelines builds and has a different direct consequence.

D:

A release may break at runtime even though each individual code module passed its unit tests. That risk is relevant to service integration tests with ephemeral environments, but the specific unresolved condition here concerns pull-request unit tests gating azure pipelines builds and has a different direct consequence.

Question 326

A GitHub Actions test step uses a command that swallows nonzero exit codes and reports green despite failing cases. Which implementation BEST addresses the operational issue?

Run deterministic unit tests as required pull-request checks and fail the merge or promotion on genuine test failure.
Choose agents with required capabilities and publish authenticated, machine-readable test results as release-gate evidence.
Define representative postdeployment smoke tests and make their results a required environment promotion check.
Run integration tests against provisioned test dependencies with controlled identities, seeded data, and predictable cleanup.

Explanation

Correct Answer

A:

Run deterministic unit tests as required pull-request checks and fail the merge or promotion on genuine test failure. Fast code-level tests detect known regressions only if their failure status controls integration. An apparently successful build can ship a defect already revealed by automated unit tests.

Incorrect Answers

B:

Choose agents with required capabilities and publish authenticated, machine-readable test results as release-gate evidence.

C:

Define representative postdeployment smoke tests and make their results a required environment promotion check.

D:

Run integration tests against provisioned test dependencies with controlled identities, seeded data, and predictable cleanup.

Question 327

A GitHub Actions test step uses a command that swallows nonzero exit codes and reports green despite failing cases. How should the team validate the intended result?

Introduce a known failing assertion in a test branch and verify the required check blocks merge.
Deploy a controlled faulty revision and verify the rollout gate blocks approval or initiates defined rollback behavior.
Inspect line and branch coverage for the altered code and confirm failing edge cases are represented by tests.
Re-run a platform-specific test and verify the expected agent image, test totals, failures, and output artifacts are recorded.

Explanation

Correct Answer

A:

Introduce a known failing assertion in a test branch and verify the required check blocks merge. Fast code-level tests detect known regressions only if their failure status controls integration.

Incorrect Answers

B:

Deploy a controlled faulty revision and verify the rollout gate blocks approval or initiates defined rollback behavior.

C:

Inspect line and branch coverage for the altered code and confirm failing edge cases are represented by tests.

D:

Re-run a platform-specific test and verify the expected agent image, test totals, failures, and output artifacts are recorded.

Question 328

A GitHub Actions test step uses a command that swallows nonzero exit codes and reports green despite failing cases. Which DevOps implementation principle BEST explains the issue?

A successful job exit does not establish coverage when tests may have been skipped or results dropped.
Fast code-level tests detect known regressions only if their failure status controls integration.
Unit tests cannot prove correctness at remote service and serialization boundaries.
A headline coverage percentage is insufficient unless it measures relevant code and behavior.

Explanation

Correct Answer

B:

Fast code-level tests detect known regressions only if their failure status controls integration. An apparently successful build can ship a defect already revealed by automated unit tests.

Incorrect Answers

A:

A successful job exit does not establish coverage when tests may have been skipped or results dropped.

C:

Unit tests cannot prove correctness at remote service and serialization boundaries.

D:

A headline coverage percentage is insufficient unless it measures relevant code and behavior.

Question 329

A GitHub Actions test step uses a command that swallows nonzero exit codes and reports green despite failing cases. What preventive practice should be maintained after the fix?

Maintain smoke-test coverage of top user journeys and retest gates after dependency changes.
Protect test workflows and review skipped or disabled test gates when pipeline configuration changes.
Version test-environment definitions and refresh contract fixtures after upstream API changes.
Monitor agent image drift and alert when expected test counts or reporting artifacts disappear.

Explanation

Correct Answer

B:

Protect test workflows and review skipped or disabled test gates when pipeline configuration changes. An apparently successful build can ship a defect already revealed by automated unit tests.

Incorrect Answers

A:

Maintain smoke-test coverage of top user journeys and retest gates after dependency changes.

C:

Version test-environment definitions and refresh contract fixtures after upstream API changes.

D:

Monitor agent image drift and alert when expected test counts or reporting artifacts disappear.

Question 330

A GitHub Actions test step uses a command that swallows nonzero exit codes and reports green despite failing cases. What outcome most clearly explains the business impact?

A release may break at runtime even though each individual code module passed its unit tests.
A faulty build can be promoted simply because its infrastructure reported healthy.
An apparently successful service rollout may interrupt customers still using supported older clients.
An apparently successful build can ship a defect already revealed by automated unit tests.

Explanation

Correct Answer

D:

An apparently successful build can ship a defect already revealed by automated unit tests. This is the directly relevant business or security consequence of pull-request unit tests gating azure pipelines builds. Root cause: Fast code-level tests detect known regressions only if their failure status controls integration.

Incorrect Answers

A:

A release may break at runtime even though each individual code module passed its unit tests. That risk is relevant to service integration tests with ephemeral environments, but the specific unresolved condition here concerns pull-request unit tests gating azure pipelines builds and has a different direct consequence.

B:

A faulty build can be promoted simply because its infrastructure reported healthy. That risk is relevant to staging smoke tests as environment approval gates, but the specific unresolved condition here concerns pull-request unit tests gating azure pipelines builds and has a different direct consequence.

C:

An apparently successful service rollout may interrupt customers still using supported older clients. That risk is relevant to consumer-driven api contract compatibility testing, but the specific unresolved condition here concerns pull-request unit tests gating azure pipelines builds and has a different direct consequence.

Microsoft AZ-400 Exam Dumps, Practice Test Questions

Question 320

Explanation

Correct Answers

Incorrect Answers

Question 321

Explanation

Correct Answer

Incorrect Answers

Question 322

Explanation

Correct Answer

Incorrect Answers

Question 323

Explanation

Correct Answer

Incorrect Answers

Question 324

Explanation

Correct Answer

Incorrect Answers

Question 325

Explanation

Correct Answer

Incorrect Answers

Question 326

Explanation

Correct Answer

Incorrect Answers

Question 327

Explanation

Correct Answer

Incorrect Answers

Question 328

Explanation

Correct Answer

Incorrect Answers

Question 329

Explanation

Correct Answer

Incorrect Answers

Question 330

Explanation

Correct Answer

Incorrect Answers