Microsoft GH-300 Practice Test 17
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.
Question 161
A team wants AI comments on a pull request before human review. What workflow is appropriate?
- Add security review criteria in supported repository custom instructions.
- Request Copilot code review and examine findings alongside required human checks.
- Preserve required tests, security assessment, and accountable human approval.
- Invoke the supported re-review action or configure applicable automatic reviews for new pushes.
Explanation
Correct Answer
B:Automated review can highlight issues but is not authoritative approval.
Incorrect Answers
A:Shared instructions make recurring review priorities explicit. What workflow is appropriate. Automated review can highlight issues but is not authoritative approval.
C:A clean AI review is not proof of absence of vulnerabilities. automated review can highlight issues but is not authoritative approval.
D:A previous review does not necessarily re-run after every push. automated review can highlight issues but is not authoritative approval.
Question 162
A Copilot review incorrectly flags an intentional exception with no project context. What can improve it?
- Request Copilot code review and examine findings alongside required human checks.
- Add concise repository or path-specific review instructions describing the exception.
- Add security review criteria in supported repository custom instructions.
- Preserve required tests, security assessment, and accountable human approval.
Explanation
Correct Answer
B:Relevant local standards help the reviewer interpret intended patterns.
Incorrect Answers
A:Automated review can highlight issues but is not authoritative approval. Relevant local standards help the reviewer interpret intended patterns.
C:Shared instructions make recurring review priorities explicit. What can improve it. Relevant local standards help the reviewer interpret intended patterns.
D:A clean AI review is not proof of absence of vulnerabilities. relevant local standards help the reviewer interpret intended patterns.
Question 163
A new commit addresses a Copilot review finding. How can a reviewer request another pass?
- Preserve required tests, security assessment, and accountable human approval.
- Add concise repository or path-specific review instructions describing the exception.
- Request Copilot code review and examine findings alongside required human checks.
- Invoke the supported re-review action or configure applicable automatic reviews for new pushes.
Explanation
Correct Answer
D:A previous review does not necessarily re-run after every push.
Incorrect Answers
A:A clean AI review is not proof of absence of vulnerabilities. a previous review does not necessarily re-run after every push.
B:Relevant local standards help the reviewer interpret intended patterns. a previous review does not necessarily re-run after every push.
C:Automated review can highlight issues but is not authoritative approval. A previous review does not necessarily re-run after every push.
Question 164
A team wants Copilot reviews to check for hardcoded secrets across every PR. What should it configure?
- Add concise repository or path-specific review instructions describing the exception.
- Add security review criteria in supported repository custom instructions.
- Invoke the supported re-review action or configure applicable automatic reviews for new pushes.
- Request Copilot code review and examine findings alongside required human checks.
Explanation
Correct Answer
B:Shared instructions make recurring review priorities explicit.
Incorrect Answers
A:Relevant local standards help the reviewer interpret intended patterns. shared instructions make recurring review priorities explicit.
C:A previous review does not necessarily re-run after every push. What should it configure. Shared instructions make recurring review priorities explicit.
D:Automated review can highlight issues but is not authoritative approval. Shared instructions make recurring review priorities explicit.
Question 165
Copilot code review flags a project-specific exception, while a security finding may be real. Which TWO steps improve review quality? (Select TWO.)
- Verify the security finding against the actual diff and tests before disposition.
- Provide concise repository-specific instructions describing the intentional exception.
- Remove branch protections to avoid further reviewer questions.
- Ignore all code review findings because one was wrong.
- Treat an automated no-findings result as proof of security.
Explanation
Correct Answers
A:Review comments are hypotheses requiring contextual validation.
B:Documented local standards help interpret the unusual code.
Incorrect Answers
C:Policy removal does not correct the code.
D:One false positive does not invalidate all other evidence.
E:No single review eliminates testing and human accountability.
Question 166
A product team repeatedly explains the same architecture documents in separate Copilot chats. What feature can provide shared context?
- Bring the related artifacts into a Space or supported shared context source.
- Check sharing settings and confidentiality of all included artifacts.
- Confirm the Space has the current approved material and validate the answer against it.
- Create a Copilot Space containing the approved design notes and source references.
Explanation
Correct Answer
D:Spaces organize reusable material for grounded conversations.
Incorrect Answers
A:Unified relevant context can reduce omissions across separate objects. spaces organize reusable material for grounded conversations.
B:A public Space may expose shared notes even when private linked sources retain access checks. Spaces organize reusable material for grounded conversations.
C:Shared context can become stale or incomplete. What feature can provide shared context. Spaces organize reusable material for grounded conversations.
Question 167
A team shares a Space that references a private repository with an external viewer. What should it expect?
- Check sharing settings and confidentiality of all included artifacts.
- Create a Copilot Space containing the approved design notes and source references.
- Bring the related artifacts into a Space or supported shared context source.
- Verify the viewer's underlying source permissions rather than assuming Space access grants repository rights.
Explanation
Correct Answer
D:Space references do not automatically make otherwise protected content readable.
Incorrect Answers
A:A public Space may expose shared notes even when private linked sources retain access checks. Space references do not automatically make otherwise protected content readable.
B:Spaces organize reusable material for grounded conversations. space references do not automatically make otherwise protected content readable.
C:Unified relevant context can reduce omissions across separate objects. space references do not automatically make otherwise protected content readable.
Question 168
A Space answer contradicts a recently revised design document. What should the user check?
- Confirm the Space has the current approved material and validate the answer against it.
- Check sharing settings and confidentiality of all included artifacts.
- Create a Copilot Space containing the approved design notes and source references.
- Verify the viewer's underlying source permissions rather than assuming Space access grants repository rights.
Explanation
Correct Answer
A:Shared context can become stale or incomplete.
Incorrect Answers
B:A public Space may expose shared notes even when private linked sources retain access checks. Shared context can become stale or incomplete.
C:Spaces organize reusable material for grounded conversations. shared context can become stale or incomplete.
D:Space references do not automatically make otherwise protected content readable. What should the user check. Shared context can become stale or incomplete.
Question 169
A developer wants to ask a question about an issue, PR, and architecture note together. Which context workflow fits?
- Verify the viewer's underlying source permissions rather than assuming Space access grants repository rights.
- Bring the related artifacts into a Space or supported shared context source.
- Create a Copilot Space containing the approved design notes and source references.
- Confirm the Space has the current approved material and validate the answer against it.
Explanation
Correct Answer
B:Unified relevant context can reduce omissions across separate objects.
Incorrect Answers
A:Space references do not automatically make otherwise protected content readable. Which context workflow fits. Unified relevant context can reduce omissions across separate objects.
C:Spaces organize reusable material for grounded conversations. unified relevant context can reduce omissions across separate objects.
D:Shared context can become stale or incomplete. unified relevant context can reduce omissions across separate objects.
Question 170
A team considers making an internal Space public for onboarding. What should be reviewed first?
- Check sharing settings and confidentiality of all included artifacts.
- Confirm the Space has the current approved material and validate the answer against it.
- Verify the viewer's underlying source permissions rather than assuming Space access grants repository rights.
- Bring the related artifacts into a Space or supported shared context source.
Explanation
Correct Answer
A:A public Space may expose shared notes even when private linked sources retain access checks.
Incorrect Answers
B:Shared context can become stale or incomplete. a public Space may expose shared notes even when private linked sources retain access checks.
C:Space references do not automatically make otherwise protected content readable. What should be reviewed first. A public Space may expose shared notes even when private linked sources retain access checks.
D:Unified relevant context can reduce omissions across separate objects. A public Space may expose shared notes even when private linked sources retain access checks.