Microsoft GH-600 Exam Syllabus Topics:

Microsoft GitHub Agentic AI Developer Sample Questions:

1. You need Copilot's coding agent to interact with an external ticketing system (e.g., Jira) so it can pull issue details as part of its workflow. What should you configure?

A) A CODEOWNERS entry
B) A .copilotignore rule
C) A branch protection ruleset
D) An MCP server

2. 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) /plan
B) /diff
C) /context
D) /compact

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?

A) In the YAML frontmatter of the Orchestrator agent, add Summarizer to the agents list.
B) In the YAML frontmatter of the Reviewer agent, add a handoffs entry that points to the Summarizer agent.
C) In the YAML frontmatter of the Orchestrator agent, add Summarizer to the tools list.
D) In the YAML frontmatter of the Reviewer agent, add Summarizer to the agents list.

4. Drag and Drop Question
You have a GitHub Enterprise Cloud Organization that uses the GitHub Copilot coding agent to resolve issues asynchronously.
When an issue is assigned to GitHub Copilot, the agent creates a draft pull request, but your team cannot always tell whether the agent is actively working, has completed its session, or is awaiting workflow approval.
Which execution context does each signal indicate? To answer, drag the appropriate context to the correct signals. Each signal may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.

5. Case Study 2
Existing Environment
GitHub Environment
The GitHub environment contains the following:
- Three repositories named product-api, billing-service, and infra-terraform.
- Branch protection on the main branch in all repositories that requires at least one pull request review before merging
- GitHub Actions runners used across all workflows
- A GitHub team named SG_Dev that contains developers
- A GitHub team named SG_Review that contains senior engineers and a security team
- A .github/copilot-instructions.md file that includes general coding conventions for all features Agent environment The product-api repository uses a GitHub Copilot coding agent named agent1 that has the following configurations:
- No custom agent profile is defined.
- A Model Context Protocol (MCP) server named MCP1 is deployed to
https://mcp.litwareinc.internal and provides access to internal ticketing and deployment APIs.
MCP1 requires an API key for authentication.
A second Copilot coding agent named agent2 handles changes in infra-terraform and runs in parallel with agent1 when both agents have open assigned issues.
Copilot memory is NOT enabled for the organization.
Problem Statements
Litware identifies the following issues:
- During two recent sessions, agent1 accessed files in billing-service, which is outside the agent's intended scope.
- agent1 makes code changes immediately after receiving a task.
- A developer named Ben, who is on the SG_Dev team, reports that agent1 completed a session with a successful status and opened a pull request, but the pull request contains no file changes.
Other developers report this intermittently as well.
- Both agent1 and agent2 modified shared/config.yaml in a parallel test run, generating conflicting outputs.
agent1 consistently uses raw try-catch blocks for error handling, which violates the defined implementation guidelines of SG_Dev.
Requirements
Planned Changes
Litware plans to make the following changes:
- Ensure that agent1 can access all the tools in the environment.
- Provide product-api with specific instructions to agent1 without affecting Copilot Chat or Copilot code review.
- Configure MCP1 as a tool for agent1 by modifying the product-api repository MCP configuration.
- Ensure that Copilot retains details that it has learned and uses that knowledge for future work.
This must be applied to all licensed members of the organization.
Implementation guidelines
The development team at Litware identifies the following implementation guidelines:
- Agent workflows must be able to run in parallel.
- Application error handling must use the repository ErrorHandler class.
- agent1 and agent2 must run on isolated branches during parallel execution. File-level conflicts must be detected before merges, and both agents must be able to run concurrently.
Security requirements
Litware identifies the following security requirements:
- Only the members of SG_Review must be able to approve agent1 plan outputs.
- All API keys must be stored and accessed securely.
- The developers must NOT be able to self-approve.
Agent configuration

You need to provide access to the API key of MCP1. The solution must meet the security requirements.
What should you do?

A) In the product-api repository settings, add the API key directly to the .mcp/server.json file by using a plaintext apiKey field.
B) Store the API key as a secret in the Copilot environment of product-api by using a name prefix of COPILOT_MCP_, and then reference the variable name in the mcp.json configuration.
C) Store the API key as a GitHub Codespaces user secret scoped to product-api.
D) In product-api, add the API key as a GitHub Actions encrypted secret and reference the secret by using ${{ secrets.KEY }} in the workflow YAML of agent1.

Solutions: