ExamworthyExamworthy
Open the appStart free

GH-300 - Use GitHub Copilot features - Section 2.1

Enable GitHub Copilot in the IDE and use inline suggestions and the editor experience.

Enable GitHub Copilot in a supported IDE, accept and dismiss inline (ghost-text) suggestions, and cycle alternatives. Recognise when an inline completion is the right surface versus Copilot Chat, and how open files and the editor selection shape a suggestion.

Inline suggestionsGhost textIDE integrationCopilot extension

Practice question for this objective

Free sampleUse GitHub Copilot featureseasy

A developer wants to start using GitHub Copilot inline suggestions inside Visual Studio Code for the first time. Their editor is installed and they hold an active Copilot subscription, but no Copilot features appear yet. Which step is required before ghost text can appear as they type?

  • AOpen a pull request in the repository so that Copilot code review can begin posting inline suggestions directly into the editor window.
  • BInstall the GitHub Copilot extension from the Visual Studio Code Marketplace and sign in with the GitHub account that holds the subscription. Correct
  • CAdd a Model Context Protocol server to the workspace so that the editor can reach the Copilot completion service for suggestions.
  • DCreate a custom instructions file in the repository root so that the editor knows to display Copilot completions inline.
Inline Copilot suggestions require the Copilot extension installed in the editor and a signed-in, licensed GitHub account. Ghost text comes from the Copilot extension running inside the editor and talking to the completion service on the developer's behalf. Without the extension installed and an authenticated, licensed account behind it, the editor has nothing to request or render inline suggestions from, so installation plus sign-in is the prerequisite step.

Why A is wrong: Copilot code review posts comments on pull request diffs on GitHub, not ghost text in the editor, so opening a pull request does nothing to enable inline completions while typing.

Why B is correct: Inline suggestions are delivered by the GitHub Copilot extension, which must be installed in the editor and authenticated against the GitHub account holding the licence before any ghost text is produced.

Why C is wrong: Model Context Protocol connects Copilot Chat to external tools and data, not the inline completion path, so adding an MCP server cannot make ghost text begin to appear.

Why D is wrong: Custom instructions shape the content of responses once Copilot is active, but they do not install or authenticate the extension that produces inline suggestions in the first place.

See more GH-300 practice questions, answers explained.

More in this domain

Back to all Use GitHub Copilot features objectives, or the GH-300 cert hub.

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