Question 30
During an operational security assessment at a public-sector technology agency, the team documents this issue: Release feedback is accepted verbally and never reaches the backlog. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Choose TWO statements that provide both the appropriate correction and a meaningful test of its success. (Select TWO.)
Explanation
Correct Answers
Correct corrective action. Use standardized GitHub issue templates, labels, assignments and notifications to route actionable user feedback into prioritized work and closure. The action targets the recorded failure (Release feedback is accepted verbally and never reaches the backlog), and is intended to reduce the corresponding risk: Ad hoc feedback in chat and email is lost or duplicated and cannot be evaluated against customer impact.
Correct verification. A reported defect creates a categorized, owned issue with reproducible evidence, linked fix and timely closure notification. The measurement or controlled test provides evidence for the issue (Release feedback is accepted verbally and never reaches the backlog) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
An approved work item links to the merged PR, build run, release and relevant defect evidence through the configured integration. It is not the complementary risk control for GitHub issues feedback triage.
Connect requirements, test cases, automated test runs, defects and deployment versions through Azure Test Plans or equivalent linked records. The GitHub issues feedback triage implementation and safeguard are still missing.
Adopt short-lived branches from main with reviewed pull requests, automated checks, and frequent integration instead of prolonged parallel development. The two-part GitHub issues feedback triage control remains unsatisfied.