Question 350
During an operational security assessment at a public-sector technology agency, the team documents this issue: A pull request deletes important tests without triggering any coverage review. 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.)
Explanation
Correct Answers
Correct corrective action. Publish code coverage results from the test runner and enforce a focused policy for critical code without treating high percentages as proof of quality. The action targets the recorded failure (A pull request deletes important tests without triggering any coverage review), and is intended to reduce the corresponding risk: Unmeasured or misleading test coverage can hide untested branches despite passing test suites.
Correct verification. A change affecting a critical branch shows targeted tests and a reproducible coverage report before PR approval. The measurement or controlled test provides evidence for the issue (A pull request deletes important tests without triggering any coverage review) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
Run required unit tests in Azure Pipelines before artifact publishing and propagate nonzero failure status to the pipeline result. It is not the complementary risk control for code coverage reporting and thresholds.
Publish structured test results and classify repeated flaky failures, with quarantine and correction procedures that preserve a visible release risk. The paired controls concern code coverage reporting and thresholds, not that measure.
A deliberately critical scan finding or missing mandatory review blocks promotion while an approved clean artifact proceeds. The code coverage reporting and thresholds implementation and safeguard are still missing.