Hands-on experience with coding agents
RecommendedWorking with GitHub Copilot agents, MCP servers, custom instructions and custom agents, tools and Copilot setup steps.

Validates knowledge of running AI coding agents in GitHub workflows, including tool use, state, evaluation, orchestration and guardrails.
GH-600 tests practical agent operations on GitHub: where agents fit in the development lifecycle, how they use tools and MCP servers, how they keep state, how you evaluate and tune them, how several agents work together, and which guardrails keep them accountable. Expect to read real configuration and logs. Start with the three official modules, then build agent workflows yourself using the docs the study guide links for each domain.
Example scenario: Your team wants an agent to pick up labelled issues and open pull requests. How would you make it produce a plan that someone approves before it changes code?
Example scenario: An MCP server that reaches a production database should only be available to agents in one repository. Where would you configure that, and how would you check it?
Example scenario: An agent's pull requests keep failing the same code scanning check. Which artifacts would you read, and is the root cause more likely its instructions, its tools or its context?
Example scenario: Two agents are assigned related issues that both touch the same configuration file. How would you stop them colliding?
Official GH-600 study guide · Developing in Agentic AI Systems
Choose one answer, or select every correct option when the question says how many to pick.
A team wants an agent to explain its intended changes and wait for a reviewer to approve them before it edits any files. What should they configure?
A. Separating planning from action and requiring approval in between keeps the agent from changing code before a person has reviewed the plan.
Move items into the right places on screen, such as matching a situation to the control that fits it.
Match each situation to the guardrail that fits it.
Delete production data → require explicit human approval; Reads documentation → allow without approval; Two agents edit the same file → isolate them on separate branches; Growing tool list → enforce an MCP allow list.
Sign in to Microsoft Learn with a personal Microsoft account, then schedule through Pearson VUE. Exams booked with a work or school account are lost if you leave that organization.
Read the study guide and its linked docs first, then build small agent workflows so you can read their configuration and logs fluently.
Most candidates spend 35–65 hours. Plan for the low end if you already run Copilot agents, MCP servers and Actions workflows; add time if multi-agent work, guardrails or Actions YAML are new to you.
Microsoft Learn has three official modules for the first domains. For the rest, the study guide links GitHub Docs pages for each skill; work through them with a test repository open.
Read real artifacts A beta candidate found the exam far more about reading agent files, MCP configuration, logs and Actions snippets than the modules suggest. Practise with real files.
Use the free community study guide for flashcards, labs and a mock exam, and add a paid question set if you want timed practice.
Use the checklist for your delivery route.
A detailed beta write-up says most questions asked you to read YAML, JSON, CLI and session logs, agent files, MCP configuration or Actions snippets and pick the right field or reading. A commenter called it much harder than GH-300.
A candidate who scored 805 after the beta said the exam leaned heavily on Actions and YAML configuration, and a beta candidate reported many questions on Actions workflows and Copilot CLI. Brush up on workflow syntax first if it is not part of your job.