100% Latest & Updated Microsoft AZ-400 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 360
A team treats successful container startup as proof that database migrations and external APIs are functional. Choose TWO measures that implement and verify an effective Azure DevOps response to this specific situation. (Choose TWO.)
- Declare staging smoke tests as environment approval gates successful solely from a green pipeline status and skip checking its actual control outcome.
- Dismiss the known risk for staging smoke tests as environment approval gates and keep no evidence or accountable owner after deployment.
- Define representative postdeployment smoke tests and make their results a required environment promotion check.
- Deploy a controlled faulty revision and verify the rollout gate blocks approval or initiates defined rollback behavior.
- Bypass review and testing for staging smoke tests as environment approval gates whenever the release deadline is urgent, applying the change to production immediately.
Explanation
Correct Answers
C:Define representative postdeployment smoke tests and make their results a required environment promotion check. Provisioning and container health do not establish that a usable customer transaction path is operating. A faulty build can be promoted simply because its infrastructure reported healthy.
D:Deploy a controlled faulty revision and verify the rollout gate blocks approval or initiates defined rollback behavior. Provisioning and container health do not establish that a usable customer transaction path is operating.
Incorrect Answers
A:Declare staging smoke tests as environment approval gates successful solely from a green pipeline status and skip checking its actual control outcome. It conflicts with the stated operating condition: Provisioning and container health do not establish that a usable customer transaction path is operating.
B:Dismiss the known risk for staging smoke tests as environment approval gates and keep no evidence or accountable owner after deployment. It conflicts with the stated operating condition: Provisioning and container health do not establish that a usable customer transaction path is operating.
E:Bypass review and testing for staging smoke tests as environment approval gates whenever the release deadline is urgent, applying the change to production immediately. It conflicts with the stated operating condition: Provisioning and container health do not establish that a usable customer transaction path is operating.
Question 361
A seasonal portal passes functional tests but stalls at peak concurrency because its new database query creates contention. Which solution should be prioritized to resolve the stated failure?
- Collect coverage from actual targeted tests and compare changed critical paths against meaningful risk-based thresholds.
- Run integration tests against provisioned test dependencies with controlled identities, seeded data, and predictable cleanup.
- Run representative load tests with accepted latency, error, throughput, and backlog thresholds before high-risk releases.
- Define representative postdeployment smoke tests and make their results a required environment promotion check.
Explanation
Correct Answer
C:Run representative load tests with accepted latency, error, throughput, and backlog thresholds before high-risk releases. Functional correctness under light traffic is not proof of safe behavior at production concurrency. A logically correct update can nevertheless cause a widespread performance incident at expected load.
Incorrect Answers
A:Collect coverage from actual targeted tests and compare changed critical paths against meaningful risk-based thresholds.
B:Run integration tests against provisioned test dependencies with controlled identities, seeded data, and predictable cleanup. That applies to service integration tests with ephemeral environments, not load testing and latency thresholds before promotion.
D:Define representative postdeployment smoke tests and make their results a required environment promotion check. That applies to staging smoke tests as environment approval gates, not load testing and latency thresholds before promotion.
Question 362
A seasonal portal passes functional tests but stalls at peak concurrency because its new database query creates contention. Which evidence would BEST demonstrate that the fix operates as intended?
- Run recorded older consumer contract cases against the candidate service before allowing production promotion.
- Compare baseline and candidate performance under consistent demand with p95 latency and resource saturation evidence.
- Introduce a known failing assertion in a test branch and verify the required check blocks merge.
- Compare repeated test execution histories and reproduce the failure with controlled clocks, fixtures, or dependency conditions.
Explanation
Correct Answer
B:Compare baseline and candidate performance under consistent demand with p95 latency and resource saturation evidence. Functional correctness under light traffic is not proof of safe behavior at production concurrency.
Incorrect Answers
A:Run recorded older consumer contract cases against the candidate service before allowing production promotion. That applies to consumer-driven api contract compatibility testing, not load testing and latency thresholds before promotion.
C:Introduce a known failing assertion in a test branch and verify the required check blocks merge. That applies to pull-request unit tests gating azure pipelines builds, not load testing and latency thresholds before promotion.
D:Compare repeated test execution histories and reproduce the failure with controlled clocks, fixtures, or dependency conditions. That applies to flaky test detection and root-cause remediation, not load testing and latency thresholds before promotion.
Question 363
A seasonal portal passes functional tests but stalls at peak concurrency because its new database query creates contention. Which design distinction is MOST relevant in these conditions?
- Provisioning and container health do not establish that a usable customer transaction path is operating.
- Unit tests cannot prove correctness at remote service and serialization boundaries.
- Functional correctness under light traffic is not proof of safe behavior at production concurrency.
- A headline coverage percentage is insufficient unless it measures relevant code and behavior.
Explanation
Correct Answer
C:Functional correctness under light traffic is not proof of safe behavior at production concurrency. A logically correct update can nevertheless cause a widespread performance incident at expected load.
Incorrect Answers
A:Provisioning and container health do not establish that a usable customer transaction path is operating.
B:Unit tests cannot prove correctness at remote service and serialization boundaries. That applies to service integration tests with ephemeral environments, not controlling principle for load testing and latency thresholds before promotion.
D:A headline coverage percentage is insufficient unless it measures relevant code and behavior. That applies to code coverage analysis for critical logic changes, not controlling principle for load testing and latency thresholds before promotion.
Question 364
A seasonal portal passes functional tests but stalls at peak concurrency because its new database query creates contention. Which ongoing guardrail would BEST prevent this problem from recurring?
- Maintain smoke-test coverage of top user journeys and retest gates after dependency changes.
- Version test-environment definitions and refresh contract fixtures after upstream API changes.
- Keep realistic test profiles and update capacity gates after business demand or architecture changes.
- Monitor agent image drift and alert when expected test counts or reporting artifacts disappear.
Explanation
Correct Answer
C:Keep realistic test profiles and update capacity gates after business demand or architecture changes. A logically correct update can nevertheless cause a widespread performance incident at expected load.
Incorrect Answers
A:Maintain smoke-test coverage of top user journeys and retest gates after dependency changes. This helps sustain a control for staging smoke tests as environment approval gates; it does not directly stop recurrence of load testing and latency thresholds before promotion described in this case.
B:Version test-environment definitions and refresh contract fixtures after upstream API changes. This helps sustain a control for service integration tests with ephemeral environments; it does not directly stop recurrence of load testing and latency thresholds before promotion described in this case.
D:Monitor agent image drift and alert when expected test counts or reporting artifacts disappear. This helps sustain a control for azure pipelines test results and agent capability validation; it does not directly stop recurrence of load testing and latency thresholds before promotion described in this case.
Question 365
A seasonal portal passes functional tests but stalls at peak concurrency because its new database query creates contention. Which risk is directly created by the described failure?
- A logically correct update can nevertheless cause a widespread performance incident at expected load.
- 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
A:A logically correct update can nevertheless cause a widespread performance incident at expected load. This is the directly relevant business or security consequence of load testing and latency thresholds before promotion. Root cause: Functional correctness under light traffic is not proof of safe behavior at production concurrency.
Incorrect Answers
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 load testing and latency thresholds before promotion and has a different direct consequence.
C:An apparently successful build can ship a defect already revealed by automated unit tests. That risk is relevant to pull-request unit tests gating azure pipelines builds, but the specific unresolved condition here concerns load testing and latency thresholds before promotion 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 load testing and latency thresholds before promotion and has a different direct consequence.
Question 366
A queue consumer processes test messages reliably but accumulates unsustainable backlog during production-volume spikes. Which implementation BEST addresses the operational issue?
- Run representative load tests with accepted latency, error, throughput, and backlog thresholds before high-risk releases.
- 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.
- Collect coverage from actual targeted tests and compare changed critical paths against meaningful risk-based thresholds.
Explanation
Correct Answer
A:Run representative load tests with accepted latency, error, throughput, and backlog thresholds before high-risk releases. Functional correctness under light traffic is not proof of safe behavior at production concurrency. A logically correct update can nevertheless cause a widespread performance incident at expected load.
Incorrect Answers
B:Define representative postdeployment smoke tests and make their results a required environment promotion check. That applies to staging smoke tests as environment approval gates, not load testing and latency thresholds before promotion.
C:Run integration tests against provisioned test dependencies with controlled identities, seeded data, and predictable cleanup. That applies to service integration tests with ephemeral environments, not load testing and latency thresholds before promotion.
D:Collect coverage from actual targeted tests and compare changed critical paths against meaningful risk-based thresholds.
Question 367
A queue consumer processes test messages reliably but accumulates unsustainable backlog during production-volume spikes. How should the team validate the intended result?
- Compare repeated test execution histories and reproduce the failure with controlled clocks, fixtures, or dependency conditions.
- Run recorded older consumer contract cases against the candidate service before allowing production promotion.
- Introduce a known failing assertion in a test branch and verify the required check blocks merge.
- Compare baseline and candidate performance under consistent demand with p95 latency and resource saturation evidence.
Explanation
Correct Answer
D:Compare baseline and candidate performance under consistent demand with p95 latency and resource saturation evidence. Functional correctness under light traffic is not proof of safe behavior at production concurrency.
Incorrect Answers
A:Compare repeated test execution histories and reproduce the failure with controlled clocks, fixtures, or dependency conditions. That applies to flaky test detection and root-cause remediation, not load testing and latency thresholds before promotion.
B:Run recorded older consumer contract cases against the candidate service before allowing production promotion. That applies to consumer-driven api contract compatibility testing, not load testing and latency thresholds before promotion.
C:Introduce a known failing assertion in a test branch and verify the required check blocks merge. That applies to pull-request unit tests gating azure pipelines builds, not load testing and latency thresholds before promotion.
Question 368
A queue consumer processes test messages reliably but accumulates unsustainable backlog during production-volume spikes. Which design distinction is MOST relevant in these conditions?
- Provisioning and container health do not establish that a usable customer transaction path is operating.
- Unit tests cannot prove correctness at remote service and serialization boundaries.
- Functional correctness under light traffic is not proof of safe behavior at production concurrency.
- A headline coverage percentage is insufficient unless it measures relevant code and behavior.
Explanation
Correct Answer
C:Functional correctness under light traffic is not proof of safe behavior at production concurrency. A logically correct update can nevertheless cause a widespread performance incident at expected load.
Incorrect Answers
A:Provisioning and container health do not establish that a usable customer transaction path is operating.
B:Unit tests cannot prove correctness at remote service and serialization boundaries. That applies to service integration tests with ephemeral environments, not controlling principle for load testing and latency thresholds before promotion.
D:A headline coverage percentage is insufficient unless it measures relevant code and behavior. That applies to code coverage analysis for critical logic changes, not controlling principle for load testing and latency thresholds before promotion.
Question 369
A queue consumer processes test messages reliably but accumulates unsustainable backlog during production-volume spikes. Which ongoing guardrail would BEST prevent this problem from recurring?
- Monitor agent image drift and alert when expected test counts or reporting artifacts disappear.
- Keep realistic test profiles and update capacity gates after business demand or architecture changes.
- Maintain smoke-test coverage of top user journeys and retest gates after dependency changes.
- Version test-environment definitions and refresh contract fixtures after upstream API changes.
Explanation
Correct Answer
B:Keep realistic test profiles and update capacity gates after business demand or architecture changes. A logically correct update can nevertheless cause a widespread performance incident at expected load.
Incorrect Answers
A:Monitor agent image drift and alert when expected test counts or reporting artifacts disappear. This helps sustain a control for azure pipelines test results and agent capability validation; it does not directly stop recurrence of load testing and latency thresholds before promotion described in this case.
C:Maintain smoke-test coverage of top user journeys and retest gates after dependency changes. This helps sustain a control for staging smoke tests as environment approval gates; it does not directly stop recurrence of load testing and latency thresholds before promotion described in this case.
D:Version test-environment definitions and refresh contract fixtures after upstream API changes. This helps sustain a control for service integration tests with ephemeral environments; it does not directly stop recurrence of load testing and latency thresholds before promotion described in this case.
Question 370
A queue consumer processes test messages reliably but accumulates unsustainable backlog during production-volume spikes. Which risk is directly created by the described failure?
- A faulty build can be promoted simply because its infrastructure reported healthy.
- A release may break at runtime even though each individual code module passed its unit tests.
- A logically correct update can nevertheless cause a widespread performance incident at expected load.
- An apparently successful build can ship a defect already revealed by automated unit tests.
Explanation
Correct Answer
C:A logically correct update can nevertheless cause a widespread performance incident at expected load. This is the directly relevant business or security consequence of load testing and latency thresholds before promotion. Root cause: Functional correctness under light traffic is not proof of safe behavior at production concurrency.
Incorrect Answers
A: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 load testing and latency thresholds before promotion and has a different direct consequence.
B: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 load testing and latency thresholds before promotion and has a different direct consequence.
D:An apparently successful build can ship a defect already revealed by automated unit tests. That risk is relevant to pull-request unit tests gating azure pipelines builds, but the specific unresolved condition here concerns load testing and latency thresholds before promotion and has a different direct consequence.
Designing and Implementing Microsoft DevOps Solutions (AZ-400) Practice Tests
