2026 Actual Microsoft GH-600 Dumps, Updated Exam Questions for Guaranteed Pass

GH-600 free sample questions and answers

Microsoft GH-600 practice quiz with correct answers for search indexing.

1. Question 1

   You use the GitHub Copilot CLI in a developer terminal.

   You plan to use Copilot CLI programmatically to summarize recent commits.

   You need to ensure that Copilot performs a low-risk, read-only action without granting Copilot broad write or execution capability.

   Which Copilot CLI configuration should you use?

   Acopilot -p '' --allow-all-tools
   

   Bcopilot -p '' --deny-tool 'shell(git)'
   

   Ccopilot -p '' --allow-tool 'shell(git)'
   

   Dcopilot -p '' --allow-tool 'write'
   

   Correct answer: C

   Option C is the intended answer because it grants a specific tool permission associated with Git rather than enabling every tool or allowing general file modification. The -p argument supplies the prompt programmatically, making the command suitable for a script that requests a summary of recent repository activity.

   Option A grants unnecessarily broad tool access. Option B denies the Git capability needed to inspect commit history. Option D authorizes file-writing functionality, which is unrelated to producing a read-only summary.

   The permission boundary nevertheless requires precise interpretation. Allowing Git is not inherently equivalent to enforcing read-only behavior: Git includes commands that modify files, repository state, and remote branches. A strict implementation should authorize only the required inspection commands, such as git log, using the permission-pattern syntax supported by the installed CLI version. The prompt should request summarization, but the prompt itself is not an access-control mechanism.

   Therefore, C is the narrowest relevant selection among the supplied options, while command-specific restrictions are necessary to establish a genuinely read-only execution policy.

   Relevant curriculum topics are selecting required tools, configuring tool permissions, and applying least privilege to agent execution.

   
   

   ===============

2. Question 2

   You have a repository on github.com that uses the GitHub Copilot coding agent.

   You also use the GitHub Copilot CLI locally to reproduce failures and continue the same work from your terminal.

   You need to verify the current token usage.

   Which Copilot CLI slash command should you run?

   A/compact
   

   B/diff
   

   C/usage
   

   D/context
   

   Correct answer: D

   The correct answer is /context when the requirement is to verify the current token usage of the active context window. GitHub documents /context as the command that displays the active model and the number of tokens currently in use relative to the model's total context capacity. It also provides a breakdown across the system prompt, custom instructions, built-in tools, MCP tools, conversation messages, free space, and reserved buffer.

   This is distinct from /usage. /usage reports broader session statistics, including AI Credits consumed, session duration, lines edited, and per-model token totals. Therefore, /usage is appropriate when reviewing cumulative session consumption, but /context is the more precise answer to a question asking for the current token usage of the working context.

   /compact reduces context pressure by summarizing earlier conversation history; it does not merely report the current token state. /diff reviews code changes and is unrelated to context or token accounting.

   Study Guide Reference Topics: Manage Memory, State, and Execution; context-window monitoring; token-budget management; maintaining effective long-running agent sessions.

   
   

3. Question 3

   You have a GitHub repository that contains an agent named Orchestrator. Orchestrator delegates work to the following specialized subagents:

   Planner reviews issues and creates a plan of action.

   Implementer writes code based on the plan of action.

   Reviewer reviews the code.

   You create a new agent named Summarizer that produces a concise summary of the work performed by the other agents.

   You need to ensure that Orchestrator can invoke Summarizer as part of its workflow.

   What should you do?

   AIn the YAML frontmatter of the Orchestrator agent, add Summarizer to the agents list.
   

   BIn the YAML frontmatter of the Reviewer agent, add a handoffs entry that points to the Summarizer agent.
   

   CIn the YAML frontmatter of the Orchestrator agent, add Summarizer to the tools list.
   

   DIn the YAML frontmatter of the Reviewer agent, add Summarizer to the agents list.
   

   Correct answer: A

   The configuration must be changed on the agent that performs the delegation. Orchestrator is responsible for coordinating the workflow, so its allowed subagent list must include Summarizer. Adding the new agent to that list makes it an available delegation target alongside Planner, Implementer, and Reviewer.

   An agent's agents property identifies the custom agents it can invoke as subagents. The tools property serves a different purpose: it identifies available capabilities such as reading files, editing code, or invoking agents. Adding a custom agent's name to the tools list does not register that agent as a callable subagent. The agent invocation tool must also be available; the scenario already establishes that Orchestrator delegates to other subagents.

   Changing Reviewer's configuration would enable a relationship originating from Reviewer, rather than the requested direct invocation by Orchestrator. A handoff also represents a different interaction pattern from having the orchestrating agent invoke a subagent and receive its result.

   Availability does not force execution on every task. Orchestrator's instructions should indicate when a summary is required and what information it should contain.

   Study-guide topics: delegation permissions, orchestrator responsibilities, and specialized subagents. Reference: VS Code---Subagents.

   ===============

   
   

4. Question 4

   You want to grant the Copilot coding agent access to only a narrowly scoped set of repository permissions (e.g., read code, write pull requests) rather than full admin access. What governs this scope?

   AThe agent's GITHUB_TOKEN permissions, configured per workflow/repo policy
   

   B.copilotignore
   

   Ccopilot-instructions.md
   

   DThe /context command
   

   Correct answer: A

   The correct answer is the GITHUB_TOKEN permission configuration. GitHub uses the automatically generated GITHUB_TOKEN to authenticate workflow operations against the repository, and its authorization scope can be reduced through repository defaults and the workflow permissions key. Permissions can be set globally for a workflow or narrowed further at the individual job level. GitHub recommends granting only the minimum access necessary for the task.

   For example, a workflow that only needs repository content access and pull-request modification can explicitly grant appropriate contents and pull-requests permissions rather than broad write access. Importantly, once individual permissions are specified, unspecified permission categories are set to none, providing a concrete least-privilege security boundary. Repository or organization policy can also establish restrictive default GITHUB_TOKEN permissions.

   .copilotignore concerns which content Copilot should exclude, while copilot-instructions.md provides behavioral and coding guidance; neither is an authorization mechanism. /context reports information about the Copilot CLI context and does not control repository privileges.

   Study Guide Reference Topics: Implement Guardrails and Accountability; least-privilege authorization; tool and execution permissions; repository security boundaries; controlled agent access.

   
   

5. Question 5

   You assigned an issue to the Copilot coding agent, and it opened a pull request. You want to inspect exactly what code changes were made before merging. Which CLI slash command lets you view the change set directly in the terminal?

   A/context
   

   B/diff
   

   C/compact
   

   D/plan
   

   Correct answer: B

   The correct command is /diff. GitHub Copilot CLI provides /diff specifically for reviewing code changes directly from the terminal. GitHub's current CLI command reference defines /diff as a command that reviews changes in the current directory and can automatically switch to a branch comparison when the working tree is clean. This makes it the appropriate command when validating an agent-generated change set before accepting or merging the work.

   The other commands serve different purposes. /context displays context-window utilization, including token allocation and remaining context capacity; it does not show code modifications. /compact summarizes conversation history to reclaim context-window space during long-running sessions. /plan creates an implementation plan before coding and restricts normal project-file modifications while the plan is being prepared.

   Using /diff supports an essential human-in-the-loop control in agentic software development: generated code should be inspected before it crosses a merge or deployment boundary. Reviewing the diff exposes additions, deletions, and modifications so that unintended or unsafe changes can be identified before integration.

   Study Guide Reference Topics: Implement Tool Use and Environment Interaction; agent-generated code review; human-in-the-loop validation; controlled execution and change inspection.