GH-300 - Use GitHub Copilot features (28% of the exam) - Section 2.4

Use MCP, Spaces, Spark, pull request summaries, code review, and instructions files to extend Copilot.

Extend GitHub Copilot with the Model Context Protocol (MCP) for external context and tools, organise context with Copilot Spaces, prototype with Spark, and use pull request summaries and Copilot code review. Use custom instructions and prompt files to make responses consistent across a team.

Model Context ProtocolCopilot SpacesPull request summariesCustom instructionsCopilot code review

Practice question for this objective

Free sampleUse GitHub Copilot featuresmedium

A developer wants Copilot Chat to be able to query the team's live ticketing system and read open issues directly while answering questions, rather than relying only on the open files. Which Copilot capability is designed to connect Chat to that external tool and its data?

AAdd the ticket descriptions to a custom instructions file so Copilot reads the team's standing context before it answers each question.
BDefine a content exclusion rule for the ticketing repository so that Copilot is permitted to read its issue data during a Chat session.
CConfigure a Model Context Protocol server for the ticketing system so Copilot Chat can call it as a tool and read live issue data while it answers. Correct
DCreate a Copilot Space that bundles the ticket exports so Chat can summarise the issues that were attached when the space was built.

Recognise that Model Context Protocol connects Copilot Chat to external tools and live data sources beyond the open files. Model Context Protocol defines servers that expose tools and resources which Copilot Chat can call during a conversation, so connecting a ticketing MCP server lets Chat read live issue data, something static instructions, exclusions, or attached space content cannot do.

Why A is wrong: Custom instructions inject standing guidance into prompts, but they are static text and cannot query a live ticketing system for current open issues on demand.

Why B is wrong: Content exclusions only stop named files being used as context and never grant access to an external live system, so they are the opposite of what is required here.

Why C is correct: Model Context Protocol lets Copilot Chat connect to external servers that expose tools and data, so a ticketing MCP server gives Chat live access to open issues exactly as needed.

Why D is wrong: A Copilot Space groups curated reference material, but it holds attached content rather than querying the ticketing system live for the latest open issues.

See more GH-300 practice questions, answers explained.

Exam traps in Use GitHub Copilot features

Answers that look right on this material and are not. Each one is a distractor from a different question in the GH-300 bank for this domain.

Open a Copilot Space and attach the framework documentation so any teammate browsing the space sees the conventions before they prompt Copilot.
Why it is wrong: A Copilot Space curates shared reference material to browse, but it does not automatically inject the team's standing rules into every Chat prompt in the repository.
Add the two files to a repository "content exclusion" rule so Copilot is forced to read them first when building context for the chat answer.
Why it is wrong: Content exclusions remove files from Copilot's context rather than adding them, so this control achieves the opposite of grounding the answer in those files.
Pull request summaries, so each opened pull request gains a prose overview of the change that reviewers read before they look at the diff.
Why it is wrong: Pull request summaries describe the change in prose but do not post review comments or suggested edits on the diff that the lead specifically wants.

Examworthy is not affiliated with or endorsed by GitHub. Original, blueprint-aligned practice material only.