Question 160
A team has implemented the following change: Reject or inspect the tool action, verify the resolved path, and allow only scoped non-destructive commands until reviewed. The original requirement was: A terminal agent proposes to run `rm -rf` on a directory adjacent to the current repository during cleanup. Which ONE validation test best demonstrates the intended behavior?
- Review the exact proposed command and its file impact before approving execution.
- Inspect trust prompts and verify the chosen working directory contains approved files only.
- Resume the chosen session and verify the earlier task description and file references are present.
- Ask a factual question about a specific section and verify the file reference was used.
Explanation
Correct Answer
A:Review the exact proposed command and its file impact before approving execution.
Incorrect Answers
B:Cryptographic algorithm decisions must follow authoritative security standards rather than unverified model claims. Verification of this result involves reviewing the exact proposed command and its file impact before approving execution.
C:Resume the chosen session and verify the earlier task description and file references are present. Verification of this result involves reviewing the exact proposed command and its file impact before approving execution.
D:Ask a factual question about a specific section and verify the file reference was used. Verification of this result involves reviewing the exact proposed command and its file impact before approving execution.
Question 161
During troubleshooting, investigators observe: A cleanup action would delete untracked work outside the intended build cache. The system context is: A terminal agent proposes to run `rm -rf` on a directory adjacent to the current repository during cleanup. Which ONE cause most directly explains the observed failure?
- Shell history and Copilot session state are not equivalent.
- The actual file context was omitted from the terminal prompt.
- Agentic tool execution carries real filesystem side effects.
- The current directory was assumed safe solely because it was locally checked out.
Explanation
Correct Answer
C:The remedy should therefore be: Reject or inspect the tool action, verify the resolved path, and allow only scoped non-destructive commands until reviewed.
Incorrect Answers
A:Shell history and Copilot session state are not equivalent. Agentic tool execution carries real filesystem side effects.
B:The actual file context was omitted from the terminal prompt. Agentic tool execution carries real filesystem side effects.
D:The current directory was assumed safe solely because it was locally checked out. Agentic tool execution carries real filesystem side effects.
Question 162
The current design is: Reject or inspect the tool action, verify the resolved path, and allow only scoped non-destructive commands until reviewed. The prior failure was: A cleanup action would delete untracked work outside the intended build cache. Which ONE ongoing control best protects against recurrence of that specific failure?
- Require explicit command review and trusted directories for destructive CLI work.
- Use directory trust and scoped permissions for every new agentic workspace.
- Name or identify sessions for traceable multi-step CLI investigations.
- Attach explicit approved paths and avoid unnecessary secrets in CLI prompts.
Explanation
Correct Answer
A:Agentic tool execution carries real filesystem side effects. Require explicit command review and trusted directories for destructive CLI work.
Incorrect Answers
B:Use directory trust and scoped permissions for every new agentic workspace. It would leave safe execution of generated command-line actions without the specified safeguard.
C:Name or identify sessions for traceable multi-step CLI investigations. It would leave safe execution of generated command-line actions without the specified safeguard.
D:Cryptographic algorithm decisions must follow authoritative security standards rather than unverified model claims. Preventing this failure involves requiring explicit command review and trusted directories for destructive CLI work.
Question 163
A team reports: A feature request spans a service handler, database migration, and test suite; asking inline completion cannot coordinate multi-file changes. They observe: A one-file suggestion leaves the database and test contracts inconsistent. Which ONE technical decision most directly corrects the cause?
- Use a bounded multi-file editing workflow and manually review all proposed edits rather than authorizing agent tool execution.
- Limit MCP tool permissions and require review before actions; treat tool outputs as untrusted external context.
- Use supported IDE Agent mode with the repository, test commands, and precise acceptance criteria while supervising tool actions.
- Use a configured custom agent with relevant instructions and tool restrictions for the review task.
Explanation
Correct Answer
C:The task required multi-step file/tool coordination, not a single inline continuation.
Incorrect Answers
A:The selected workflow granted broader tools than the task required. The task required multi-step file/tool coordination, not a single inline continuation.
B:The MCP integration expanded the agent's data and action trust boundary. The task required multi-step file/tool coordination, not a single inline continuation.
D:Specialized objectives and tool boundaries were not provided. The task required multi-step file/tool coordination, not a single inline continuation.
Question 164
A team has implemented the following change: Use supported IDE Agent mode with the repository, test commands, and precise acceptance criteria while supervising tool actions. The original requirement was: A feature request spans a service handler, database migration, and test suite; asking inline completion cannot coordinate multi-file changes. Which ONE validation test best demonstrates the intended behavior?
- Run it against a sample auth change and inspect the reported code references without unexpected edits.
- Inspect the entire change set and validate the requested files changed as intended.
- Inspect the proposed multi-file diff and run the project's migration and test suite.
- Inspect granted tools and try a read-only metadata query without permitting ticket changes.
Explanation
Correct Answer
C:Inspect the proposed multi-file diff and run the project's migration and test suite.
Incorrect Answers
A:Run it against a sample auth change and inspect the reported code references without unexpected edits.
B:Inspect the entire change set and validate the requested files changed as intended. That check cannot demonstrate tested AI-assisted changes that preserve stated requirements.
D:Inspect granted tools and try a read-only metadata query without permitting ticket changes.
Question 165
During troubleshooting, investigators observe: A one-file suggestion leaves the database and test contracts inconsistent. The system context is: A feature request spans a service handler, database migration, and test suite; asking inline completion cannot coordinate multi-file changes. Which ONE cause most directly explains the observed failure?
- The selected workflow granted broader tools than the task required.
- The MCP integration expanded the agent's data and action trust boundary.
- The task required multi-step file/tool coordination, not a single inline continuation.
- Specialized objectives and tool boundaries were not provided.
Explanation
Correct Answer
C:The remedy should therefore be: Use supported IDE Agent mode with the repository, test commands, and precise acceptance criteria while supervising tool actions.
Incorrect Answers
A:The selected workflow granted broader tools than the task required. The task required multi-step file/tool coordination, not a single inline continuation.
B:The MCP integration expanded the agent's data and action trust boundary. The task required multi-step file/tool coordination, not a single inline continuation.
D:Specialized objectives and tool boundaries were not provided. The task required multi-step file/tool coordination, not a single inline continuation.
Question 166
The current design is: Use supported IDE Agent mode with the repository, test commands, and precise acceptance criteria while supervising tool actions. The prior failure was: A one-file suggestion leaves the database and test contracts inconsistent. Which ONE ongoing control best protects against recurrence of that specific failure?
- Keep custom agent scopes explicit and check output against human review requirements.
- Review MCP server provenance and per-tool approvals before enabling external actions.
- Review agent tool approvals, modified files and generated tests before merging.
- Choose the least-privileged Copilot interaction mode for the requested work.
Explanation
Correct Answer
C:The task required multi-step file/tool coordination, not a single inline continuation. Review agent tool approvals, modified files and generated tests before merging.
Incorrect Answers
A:Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves reviewing agent tool approvals, modified files and generated tests before merging.
B:Approved dependency sources and lockfiles protect builds against invented or impersonated packages. Preventing this failure involves reviewing agent tool approvals, modified files and generated tests before merging.
D:Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves reviewing agent tool approvals, modified files and generated tests before merging. The observed condition is use supported IDE Agent mode with the repository, test commands, and precise acceptance criteria while supervising tool actions. The prior failure was: A one-file.
Question 167
A team reports: An engineer wants Copilot to propose edits to several specific files but does not want it autonomously run terminal commands. They observe: An unconstrained agent attempts unrelated shell operations during a simple text refactor. Which ONE technical decision most directly corrects the cause?
- Use a configured custom agent with relevant instructions and tool restrictions for the review task.
- Use a bounded multi-file editing workflow and manually review all proposed edits rather than authorizing agent tool execution.
- Use supported IDE Agent mode with the repository, test commands, and precise acceptance criteria while supervising tool actions.
- Start an authorized cloud agent task scoped to the repository and base branch, then review its proposed pull request.
Explanation
Correct Answer
B:Confirm it by checking: Inspect the entire change set and validate the requested files changed as intended.
Incorrect Answers
A:Specialized objectives and tool boundaries were not provided. The selected workflow granted broader tools than the task required.
C:The task required multi-step file/tool coordination, not a single inline continuation. The selected workflow granted broader tools than the task required.
D:Cloud delegation creates a proposed change, not automatic correctness or release approval. The selected workflow granted broader tools than the task required.
Question 168
A team has implemented the following change: Use a bounded multi-file editing workflow and manually review all proposed edits rather than authorizing agent tool execution. The original requirement was: An engineer wants Copilot to propose edits to several specific files but does not want it autonomously run terminal commands. Which ONE validation test best demonstrates the intended behavior?
- Run it against a sample auth change and inspect the reported code references without unexpected edits.
- Inspect the proposed multi-file diff and run the project's migration and test suite.
- Verify the draft branch, changed files, checks and required pull-request approvals before merging.
- Inspect the entire change set and validate the requested files changed as intended.
Explanation
Correct Answer
D:Inspect the entire change set and validate the requested files changed as intended.
Incorrect Answers
A:Run it against a sample auth change and inspect the reported code references without unexpected edits. Verification of this result involves inspecting the entire change set and validate the requested files changed as intended.
B:Generated code requires independently defined acceptance tests and review against the real program contract. It does not inspect the entire change set and validate the requested files changed as intended.
C:Verify the draft branch, changed files, checks and required pull-request approvals before merging. It does not inspect the entire change set and validate the requested files changed as intended.
Question 169
During troubleshooting, investigators observe: An unconstrained agent attempts unrelated shell operations during a simple text refactor. The system context is: An engineer wants Copilot to propose edits to several specific files but does not want it autonomously run terminal commands. Which ONE cause most directly explains the observed failure?
- Specialized objectives and tool boundaries were not provided.
- Cloud delegation creates a proposed change, not automatic correctness or release approval.
- The task required multi-step file/tool coordination, not a single inline continuation.
- The selected workflow granted broader tools than the task required.
Explanation
Correct Answer
D:The remedy should therefore be: Use a bounded multi-file editing workflow and manually review all proposed edits rather than authorizing agent tool execution.
Incorrect Answers
A:Specialized objectives and tool boundaries were not provided. The selected workflow granted broader tools than the task required.
B:Cloud delegation creates a proposed change, not automatic correctness or release approval. The selected workflow granted broader tools than the task required.
C:The task required multi-step file/tool coordination, not a single inline continuation. The selected workflow granted broader tools than the task required.
Question 170
The current design is: Use a bounded multi-file editing workflow and manually review all proposed edits rather than authorizing agent tool execution. The prior failure was: An unconstrained agent attempts unrelated shell operations during a simple text refactor. Which ONE ongoing control best protects against recurrence of that specific failure?
- Keep branch protections and required checks for agent-created pull requests.
- Review agent tool approvals, modified files and generated tests before merging.
- Choose the least-privileged Copilot interaction mode for the requested work.
- Keep custom agent scopes explicit and check output against human review requirements.
Explanation
Correct Answer
C:The selected workflow granted broader tools than the task required. Choose the least-privileged Copilot interaction mode for the requested work.
Incorrect Answers
A:Keep branch protections and required checks for agent-created pull requests. It would leave tested AI-assisted changes that preserve stated requirements without the specified safeguard.
B:Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves choosing the least-privileged Copilot interaction mode for the requested work.
D:Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves choosing the least-privileged Copilot interaction mode for the requested work. The observed condition is use a bounded multi-file editing workflow and manually review all proposed edits rather than authorizing agent tool execution. The prior failure was: An.
GitHub Copilot (GH-300) Practice Tests