Independent: not affiliated with GitHub. Free to try; the study bundle adds a study guide and two practice exams.
5 original questions, none of them in the practice exams.
Pick an answer. Show answer explains every option and links its GitHub source.
5 questions / Explanations link GitHub sources / Last updated Oct 26, 2026
Question 1
Multiple choice
Domain 1 / Task 1.1 Integrate agents into the SDLC
A team wants Copilot cloud agent to rename a field in a service's public API and update the client library that calls it. The service and the client library are in separate repositories, and the team expects each repository's part of the change to need two to three hours of agent work. Which plan fits the cloud agent's documented limits?
Show answerHide answer
Answer: B
Why
GitHub Docs lists the cloud agent's workflow limits: Copilot can only make changes in the repository specified when the task starts, works on one branch at a time and opens one pull request per task, and each session has a maximum execution time of 59 minutes that cannot be extended or bypassed. The same page advises breaking complex tasks into smaller, focused tasks, so this change has to be split by repository and by size.
Why not the others
ACopilot can only make changes in the repository specified when the task starts and cannot make changes across multiple repositories in one run; linking another issue does not change that.
CAn instruction in the task does not lift the repository scope: a session makes changes only in the repository specified when the task starts.
DSplitting by repository is needed but not enough: a session stops at its 59-minute limit, so two to three hours of work per repository has to be broken into smaller tasks.
Domain 2 / Task 2.3 Integrate agents within development environments
A repository's .github/agents folder holds a release-notes custom agent that developers select in Visual Studio Code. It depends on files that exist only on a developer's machine, so the team wants Copilot cloud agent on GitHub.com never to use it, while developers keep selecting it in the editor. Which change to the agent profile does that?
Show answerHide answer
Answer: C
Why
The custom agents configuration reference defines target as the environment or context for the custom agent, vscode or github-copilot, and says that when it is unset the agent defaults to both environments. Setting it to vscode keeps the agent out of the GitHub.com environment while leaving it available in the editor.
Why not the others
AThe Markdown body below the front matter defines the agent's behavior and instructions; where the agent is available is set by the target property.
BIt only stops Copilot cloud agent from choosing the agent automatically based on task context; the agent can still be selected manually on GitHub.com.
DIt removes manual selection in every environment, including the editor, and leaves the agent reachable programmatically.
Domain 4 / Task 4.2 Analyze failures and root causes
A platform team wants every failed tool call in Copilot cloud agent sessions sent to its analytics service so it can classify failure patterns across repositories. The service's host is already on the organization custom allowlist for the cloud agent firewall. Which setup follows the hooks reference?
Show answerHide answer
Answer: D
Why
In a cloud agent job the only hook configuration that exists by default is .github/hooks/*.json in the cloned repository. postToolUseFailure fires after a tool completes with a failure, and its payload carries the tool name, the tool arguments and the error. An http entry posts that payload as JSON to its url, which in the cloud agent must be an allow-listed host, and the reference names an http hook entry as the way to keep hook output, because files written in the sandbox are discarded when the job ends.
Why not the others
AThe cloud agent sandbox does not ship with user-level hook files; its hook configuration is loaded from .github/hooks/*.json in the cloned repository, not from a developer's machine.
BpostToolUse fires only after a tool completes successfully; a failed tool call fires postToolUseFailure.
CFiles written by hooks in the cloud agent sandbox are discarded when the job ends; the reference says to send hook output through an http hook entry to keep it.
An orchestrator built with the Copilot SDK delegates API reviews to an api-reviewer custom agent. The session sets skillDirectories to ./skills, which holds an api-style-guide skill. The api-reviewer definition has a name, description, prompt and tools, and its reviews ignore the style guide. What is the fix?
Show answerHide answer
Answer: A
Why
The SDK's custom agents guide says skills are opt-in: agents receive no skills by default, sub-agents do not inherit skills from the parent, and an agent without a skills field receives no skill content. Listing the skill in the agent's skills property injects its full content into the agent's context at startup, with the name resolved from the session's skillDirectories.
Why not the others
BThe agent property only pre-selects which custom agent is active when the session starts; it gives the agent no skill content.
Cinfer only controls whether the runtime can select the agent automatically; a sub-agent runs in an isolated context either way.
DEach sub-agent runs with its own prompt in an isolated context, so text in the main agent's prompt does not reach it.
Domain 6 / Task 6.2 Implement guardrails and human-in-the-loop workflows
An organization's security policy says Copilot cloud agent's firewall must stay on in every repository, approved external hosts are kept in one list the organization manages, and no repository administrator may turn the firewall off or add hosts. The organization's Recommended allowlist setting is already Disabled. Which two organization settings under Internet access implement the rest of the policy? Choose two.
Show answerHide answer
Answers: A and C
Why
By default Copilot's internet access is limited by a firewall, but the organization's Enable firewall setting defaults to Let repositories decide, which lets each repository turn it off; Enabled removes that choice. Allow repository custom rules defaults to Enabled, which lets repository administrators add their own allowlist entries; Disabled stops that, so the organization custom allowlist, which applies to all repositories and cannot be deleted at the repository level, holds the approved hosts.
Why not the others
BDisabling the firewall allows Copilot to connect to any host, so allowlist entries have no effect; they matter only while the firewall is on.
DOrganization and repository rules are combined, so while custom rules stay enabled each repository can still add hosts of its own.
EWith Let repositories decide, repository administrators can turn the firewall off for their repository; a request is not an enforced control.
The study bundle has two practice exams with 120 original questions, an answer key and an explanation for every answer, plus the 60-page study guide. Practice exam explanations are shorter than the ones on this page: a short paragraph per question, with no source links.
Study bundle
$19
120 practice questions / Study guide / Answer keys
Every bundle includes 6 months of access: download the PDFs, and any new editions, until 6 months after your purchase date. Your receipt has a license key. Enter it at overqual.com/download for the three PDFs, stamped with your email and order number. They are yours to keep.