Question 480
The team has implemented a fix for this Copilot-related requirement: A tutorial response from Copilot quotes a command that could delete a production dataset. Which outcome directly validates the intended behavior?
Explanation
Correct Answer
This is the specific observable acceptance result for the scenario. Copilot CLI tool and path authorization are separate from the correctness of generated shell text; blanket allow-all permissions can remove important operator confirmation. It demonstrates the required behavior, rather than merely showing that a setting was changed.
Incorrect Answers
Relevant tests and security checks pass on the exact proposed change set. However, this does not establish the required outcome: the command path and target are verified in the tested sandbox, high-impact tool invocation is individually approved under manual permissions, and no production deletion was executed in testing.
The implementation uses a supported authenticated-encryption primitive with validated key management. However, this does not establish the required outcome: the command path and target are verified in the tested sandbox, high-impact tool invocation is individually approved under manual permissions, and no production deletion was executed in testing.
The tested ranking behavior meets documented fairness and compliance requirements after human review. However, this does not establish the required outcome: the command path and target are verified in the tested sandbox, high-impact tool invocation is individually approved under manual permissions, and no production deletion was executed in testing.