Question 40
During an operational security assessment at a public-sector technology agency, the team documents this issue: Test reports show passes yet the related user stories have no acceptance evidence. 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. Connect requirements, test cases, automated test runs, defects and deployment versions through Azure Test Plans or equivalent linked records. The action targets the recorded failure (Test reports show passes yet the related user stories have no acceptance evidence), and is intended to reduce the corresponding risk: Missing relationships between specifications, failed tests and releases allow defects to be waived without accountable evidence.
Correct verification. A failed acceptance test can be traced to a defect, corrective commit, rerun and released artifact with preserved IDs. The measurement or controlled test provides evidence for the issue (Test reports show passes yet the related user stories have no acceptance evidence) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
Use standardized GitHub issue templates, labels, assignments and notifications to route actionable user feedback into prioritized work and closure. The paired controls concern end-to-end quality and defect traceability, not that measure.
Link GitHub pull requests and commits to Azure Boards work items and require consistent identifiers and review evidence through delivery. It is not the complementary risk control for end-to-end quality and defect traceability.
A sample feature follows issue to short branch to reviewed PR to green checks to main, with an identifiable deployed commit. The two-part end-to-end quality and defect traceability control remains unsatisfied.