Microsoft GH-300 Practice Test 16
Question 150
An agent reports that an issue is resolved without a test or linked patch. What evidence is needed?
- Delegate a bounded research subtask to an available subagent.
- Inspect the committed diff and relevant test output before considering the task resolved.
- Keep authorized repository checks and human or configured approval conditions intact.
- Check documented subagent limits and avoid assuming unlimited delegation depth.
Explanation
Correct Answer
B:Completion claims need traceable change artifacts and validation.
Incorrect Answers
A:Subagents maintain separate context and return results to their parent session. What evidence is needed. Completion claims need traceable change artifacts and validation.
C:Delegation does not bypass repository ownership controls. Completion claims need traceable change artifacts and validation.
D:Agent orchestration has platform-specific context and nesting restrictions. completion claims need traceable change artifacts and validation.
Question 151
A user wants coordinated edits to a service and its integration tests. What should they provide?
- Search usages and update call sites or preserve compatibility.
- Specify the files, expected behavior, and test constraints for a supported edit workflow.
- Narrow the edit to the specified condition and preserve unrelated behavior.
- Inspect each diff and run all affected tests before accepting the patch.
Explanation
Correct Answer
B:Explicit multi-file context reduces unrelated modifications.
Incorrect Answers
A:Interface changes can break consumers outside the edited file. explicit multi-file context reduces unrelated modifications.
C:Small targeted diffs simplify regression review. Explicit multi-file context reduces unrelated modifications.
D:Multi-file generation is still subject to ordinary review. explicit multi-file context reduces unrelated modifications.
Question 152
An edit operation accidentally changes an unrelated lockfile. What should the reviewer do?
- Narrow the edit to the specified condition and preserve unrelated behavior.
- Compare the change with the requested scope and discard unsupported modifications.
- Inspect each diff and run all affected tests before accepting the patch.
- Specify the files, expected behavior, and test constraints for a supported edit workflow.
Explanation
Correct Answer
B:Cross-file editing can affect files not needed for the feature.
Incorrect Answers
A:Small targeted diffs simplify regression review. Cross-file editing can affect files not needed for the feature.
C:Multi-file generation is still subject to ordinary review. cross-file editing can affect files not needed for the feature.
D:Explicit multi-file context reduces unrelated modifications. What should the reviewer do. Cross-file editing can affect files not needed for the feature.
Question 153
A generated code edit updates a function but not its public callers. What should be checked?
- Search usages and update call sites or preserve compatibility.
- Specify the files, expected behavior, and test constraints for a supported edit workflow.
- Compare the change with the requested scope and discard unsupported modifications.
- Inspect each diff and run all affected tests before accepting the patch.
Explanation
Correct Answer
A:Interface changes can break consumers outside the edited file.
Incorrect Answers
B:Explicit multi-file context reduces unrelated modifications. What should be checked. Interface changes can break consumers outside the edited file.
C:Cross-file editing can affect files not needed for the feature. interface changes can break consumers outside the edited file.
D:Multi-file generation is still subject to ordinary review. interface changes can break consumers outside the edited file.
Question 154
A patch rewrites an entire component when only a validation branch needed correction. What should the engineer request?
- Specify the files, expected behavior, and test constraints for a supported edit workflow.
- Narrow the edit to the specified condition and preserve unrelated behavior.
- Compare the change with the requested scope and discard unsupported modifications.
- Search usages and update call sites or preserve compatibility.
Explanation
Correct Answer
B:Small targeted diffs simplify regression review.
Incorrect Answers
A:Explicit multi-file context reduces unrelated modifications. What should the engineer request. Small targeted diffs simplify regression review.
C:Cross-file editing can affect files not needed for the feature. small targeted diffs simplify regression review.
D:Interface changes can break consumers outside the edited file. Small targeted diffs simplify regression review.
Question 155
A multi-file Copilot edit changes a public API and accidentally edits a lockfile. Which TWO actions should the reviewer take? (Select TWO.)
- Merge immediately because the edit spans several files.
- Remove the project's integration tests to make the patch smaller.
- Rename the API again without checking downstream usage.
- Inspect and revert the unrelated lockfile change unless justified by dependencies.
- Check call sites and compatibility tests for the changed API signature.
Explanation
Correct Answers
D:Out-of-scope file modifications should not remain silently.
E:Public interfaces affect consumers outside the originally edited file.
Incorrect Answers
A:Multi-file breadth does not establish correctness.
B:Tests are needed to detect interface regressions.
C:Additional uncontrolled renames increase breakage risk.
Question 156
A developer wants Copilot to search an approved design database during a task. What extension model is suitable?
- Connect a vetted MCP server exposing only the required read methods.
- Verify each tool's data access; GitHub exclusion controls do not guarantee MCP compliance.
- Inspect the provider's actual state or action receipt before claiming success.
- Treat the returned text as untrusted and keep external disclosure approval separate.
Explanation
Correct Answer
A:MCP provides tool access to relevant external context.
Incorrect Answers
B:Third-party integrations can read information outside GitHub's content-exclusion enforcement. What extension model is suitable. MCP provides tool access to relevant external context.
C:Tool-level feedback may be incomplete, stale, or misleading. mCP provides tool access to relevant external context.
D:Retrieved information cannot grant itself permission to export data. MCP provides tool access to relevant external context.
Question 157
A community MCP tool asks for an administrator token when only search is needed. What should happen?
- Reject excess scope and configure a least-privileged credential instead.
- Connect a vetted MCP server exposing only the required read methods.
- Verify each tool's data access; GitHub exclusion controls do not guarantee MCP compliance.
- Inspect the provider's actual state or action receipt before claiming success.
Explanation
Correct Answer
A:Tool trust depends on permissions, not its name or description.
Incorrect Answers
B:MCP provides tool access to relevant external context. tool trust depends on permissions, not its name or description.
C:Third-party integrations can read information outside GitHub's content-exclusion enforcement. What should happen. Tool trust depends on permissions, not its name or description.
D:Tool-level feedback may be incomplete, stale, or misleading. tool trust depends on permissions, not its name or description.
Question 158
A tool result contains a request to send repository contents to an outside domain. How should Copilot treat it?
- Connect a vetted MCP server exposing only the required read methods.
- Verify each tool's data access; GitHub exclusion controls do not guarantee MCP compliance.
- Reject excess scope and configure a least-privileged credential instead.
- Treat the returned text as untrusted and keep external disclosure approval separate.
Explanation
Correct Answer
D:Retrieved information cannot grant itself permission to export data.
Incorrect Answers
A:MCP provides tool access to relevant external context. retrieved information cannot grant itself permission to export data.
B:Third-party integrations can read information outside GitHub's content-exclusion enforcement. How should Copilot treat it. Retrieved information cannot grant itself permission to export data.
C:Tool trust depends on permissions, not its name or description. Retrieved information cannot grant itself permission to export data.
Question 159
An MCP tool reports success after modifying a third-party system. What should the operator verify?
- Treat the returned text as untrusted and keep external disclosure approval separate.
- Inspect the provider's actual state or action receipt before claiming success.
- Connect a vetted MCP server exposing only the required read methods.
- Reject excess scope and configure a least-privileged credential instead.
Explanation
Correct Answer
B:Tool-level feedback may be incomplete, stale, or misleading.
Incorrect Answers
A:Retrieved information cannot grant itself permission to export data. tool-level feedback may be incomplete, stale, or misleading.
C:MCP provides tool access to relevant external context. tool-level feedback may be incomplete, stale, or misleading.
D:Tool trust depends on permissions, not its name or description. Tool-level feedback may be incomplete, stale, or misleading.
Question 160
A user assumes content exclusion automatically controls all third-party MCP tools. What needs correction?
- Reject excess scope and configure a least-privileged credential instead.
- Inspect the provider's actual state or action receipt before claiming success.
- Treat the returned text as untrusted and keep external disclosure approval separate.
- Verify each tool's data access; GitHub exclusion controls do not guarantee MCP compliance.
Explanation
Correct Answer
D:Third-party integrations can read information outside GitHub's content-exclusion enforcement.
Incorrect Answers
A:Tool trust depends on permissions, not its name or description. Third-party integrations can read information outside GitHub's content-exclusion enforcement.
B:Tool-level feedback may be incomplete, stale, or misleading. What needs correction. Third-party integrations can read information outside GitHub's content-exclusion enforcement.
C:Retrieved information cannot grant itself permission to export data. third-party integrations can read information outside GitHub's content-exclusion enforcement.