Copilot Chat reviews a data-access method and suggests replacing string-concatenated SQL with a parameterised query to address an injection risk. The change passes the developer's quick local smoke test. What is the most responsible next step before shipping this security improvement?
- AShip immediately, treating the passing smoke test as confirmation that the parameterised query is correct and that the injection risk has been fully eliminated by Copilot.
- BEnable Copilot duplication detection for the repository, relying on it to confirm the parameterised query is safe because the snippet does not match any public code.
- CMove the team to Copilot Business, expecting that the Business plan validates each suggested security fix before it is shown so the rewrite needs no further checking.
- DReview the parameterised query and run it through the team's security checks, since the developer who merges the change stays accountable for confirming it is secure. Correct
Why A is wrong: A smoke test exercises a happy path and is tempting to trust, but it does not prove the rewrite is secure, so shipping on it alone leaves the change unverified.
Why B is wrong: Duplication detection blocks suggestions matching public code based on similarity, not security, so it cannot confirm the parameterised query closes the injection risk.
Why C is wrong: Copilot Business adds organisation and policy controls but does not validate the security of individual suggestions, so a plan change does not remove the need to verify the fix.
Why D is correct: Copilot can propose the safer pattern, but the developer remains accountable, so reviewing the query and applying the team's security checks is what confirms the improvement before shipping.