Question 200
A software team reports this Copilot-related situation: A team needs a prompt that cannot accidentally request production deployment. Which action most directly satisfies the requirement?
Explanation
Correct Answer
Permission and side-effect boundaries belong in task instructions. Acceptance evidence: No remote deployment or production write occurs.
Incorrect Answers
Tight output constraints support reliable automation. That recommendation is relevant to a different task: A code response is verbose and cannot be used by a schema-constrained integration. In this case the main need is: A team needs a prompt that cannot accidentally request production deployment.
Iterative prompting can correct assumptions with grounded evidence. That recommendation is relevant to a different task: A first Copilot response misinterprets the return type for a library function. In this case the main need is: A team needs a prompt that cannot accidentally request production deployment.
Contradictory constraints cannot both be honored reliably. That recommendation is relevant to a different task: A prompt includes contradictory instructions to both preserve and rename public interfaces. In this case the main need is: A team needs a prompt that cannot accidentally request production deployment.