Question 370
During an operational security assessment at a public-sector technology agency, the team documents this issue: Concurrent suites interfere with shared data and produce inconsistent results. 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.)
Explanation
Correct Answers
Correct corrective action. Publish structured test results and classify repeated flaky failures, with quarantine and correction procedures that preserve a visible release risk. The action targets the recorded failure (Concurrent suites interfere with shared data and produce inconsistent results), and is intended to reduce the corresponding risk: Silently rerunning unreliable tests until green hides defects and makes quality gates untrustworthy.
Correct verification. A reproducible failure trend identifies the unstable test and corrective change while failures remain observable to reviewers. The measurement or controlled test provides evidence for the issue (Concurrent suites interfere with shared data and produce inconsistent results) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
Run representative load tests before production and enforce agreed latency, throughput and error-rate thresholds in the release process. The paired controls concern test results and flaky-test investigation, not that measure.
Use standardized, versioned build/test agent images with required runtimes and test tools, and isolate incompatible test workloads appropriately. The test results and flaky-test investigation implementation and safeguard are still missing.
A change affecting a critical branch shows targeted tests and a reproducible coverage report before PR approval. The two-part test results and flaky-test investigation control remains unsatisfied.