Pass the Microsoft GitHub Administrator GH-600 Questions and answers with Dumpstech

A fine-grained PAT restricted to product-api provides an enforceable repository-level authorization boundary for agent1. GitHub fine-grained personal access tokens can be limited to selected repositories and assigned only the repository permissions required by the workload. Consequently, even if agent1 attempts to access billing-service or infra-terraform, the credential does not authorize access to those repositories. GitHub specifically recommends fine-grained PATs when repository access must be restricted to particular repositories.

This directly aligns with the GH-600 objective to configure an agent ' s scope to a specific repository and define execution boundaries through repository context and permissions. Microsoft Learn defines execution context as including the repository an agent can access and emphasizes that repository scope is the first boundary limiting agent behavior.

Option A provides behavioral guidance but is not a security authorization boundary. Option B controls the permissions available to the workflow token but does not, by itself, establish the required cross-repository credential restriction. Option D only prevents certain push operations; it does not stop agent1 from reading or otherwise accessing the other repositories.

Study Guide Reference Topics: Implement Tool Use and Environment Interaction → execution context and boundaries; repository-specific agent scope; tool permissions; least-privilege authentication.

The first statement is Yes . When an MCP server is configured for a repository, GitHub Copilot cloud agents can use the enabled MCP tools autonomously during assigned tasks. GitHub specifically notes that Copilot does not request interactive approval before invoking configured MCP tools, making careful tool allowlisting and credential protection important.

The second statement is No . For repository-level MCP integration, Copilot cloud agent currently supports MCP tools , but it does not support MCP resources or MCP prompts exposed by the server. Resources and prompts are available in other MCP-capable Copilot experiences, such as IDE chat, but they are not consumed by the cloud coding agent in this configuration.

The third statement is Yes under the planned configuration. Litware requires agent1 to access all available tools . GitHub custom-agent configuration supports this by omitting the tools property or specifying tools: [ " * " ]. Likewise, an MCP server can use " * " to expose all of its tools. Consequently, newly introduced MCP1 tools fall within that wildcard authorization and become available without individually adding each tool name.

Study Guide Reference Topics: MCP tool integration, custom-agent tool configuration, autonomous tool invocation, MCP capability boundaries, and least-privilege agent execution.

The mcp-servers property connects a custom agent to the Model Context Protocol servers required for its planned work. MCP configuration makes defined external tools and services available to the agent in a controlled, declarative manner.

Adding a broad natural-language instruction such as “Use all available tools” does not configure a server connection, authenticate a tool, or define which external capabilities are available. It is also poor least-privilege design because it encourages unrestricted tool use without establishing a technical permission boundary.

Setting tools: [] removes all configured tools and would prevent the agent from using required capabilities. Deleting the tools line could cause the agent to inherit or expose a broader default tool set than intended. Repository-wide instructions can guide behavior, but they do not replace the agent-specific configuration needed to associate MCP servers with that agent.

A well-designed configuration identifies only the MCP servers necessary for the role, supplies secrets through approved environment mechanisms, and limits the resulting tools to the agent’s defined task.

Study-guide topics: MCP integration, agent tool configuration, and least-privilege environment access.

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

The API key should be stored as a secret in the Copilot environment and referenced by name from the MCP configuration. This keeps the secret value out of repository files, agent prompts, pull requests, and ordinary workflow output while allowing the MCP server to receive the required credential at runtime.

A plaintext key in a configuration file is unacceptable because repository history, forks, logs, and code review systems can expose it. A Codespaces user secret is scoped to a user development environment and does not provide the intended runtime secret for the Copilot agent environment. A GitHub Actions secret is useful for workflow expressions, but the scenario requires the key to be available to the MCP server configuration itself.

The prefixed environment-secret approach creates a clear boundary: the configuration references an identifier, while the secret value is resolved only in the authorized execution environment. This supports rotation without changing tracked configuration content.

Study-guide topics: MCP authentication, secrets management, secure environment configuration, and credential isolation.

Separate branches isolate each agent’s proposed changes and allow the team to inspect them independently. Adding a required status check for file-level overlap detects conflicting modifications before either pull request is merged, preventing one agent’s work from silently overwriting another’s changes.

A read-only tool configuration prevents both agents from making required changes, so it avoids conflict by eliminating implementation capability rather than controlling it. CODEOWNERS approval adds review accountability for a specific file but does not automatically detect overlap between independent agent outputs. A single concurrency group serializes entire workflows and reduces throughput even where the agents work on unrelated files.

The selected solution maintains parallel development while creating a merge-time control for the actual risk: overlapping file changes. It also produces reviewable evidence of the overlap check in pull request status results.

Branch isolation does not eliminate semantic conflicts, such as incompatible API assumptions. Teams should therefore combine overlap detection with normal pull request review and integration testing.

Study-guide topics: parallel agent coordination, branch isolation, merge controls, and conflict detection.

Target

Value

tools

[ ' execute ' ]

agents

[ ' security-reviewer ' ]

The agents property identifies the custom agent profile that lead-dev is permitted to invoke. Adding security-reviewer establishes the delegated specialist relationship required by the workflow.

The source configuration uses the execute tool for the lead agent’s subagent invocation capability. Without the appropriate invocation capability, adding the target agent name alone does not permit the orchestration step to run.

The user-invocable: false value can remain. It prevents direct selection of lead-dev in the user interface while still allowing it to operate as part of an orchestrated workflow. This is useful for internal coordinator roles that should be reached only through a parent workflow.

Read, search, or edit tools do not identify the target specialist. They may be needed for other lead-dev tasks, but they do not solve the failed subagent invocation.

Study-guide topics: subagent invocation, custom agent frontmatter, delegation permissions, and orchestrated security review.

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

Statement

Answer

The agent responded with messages.

Yes

The agent can edit files in the repository.

No

The agent analyzed files in the repository.

Yes

The log contains successful message-return events, confirming that the agent responded. It also shows successful model activity associated with the agent session, which supports the conclusion that the agent processed available information.

The log does not provide evidence of an actual file-edit tool invocation or successful repository write. An editAgent panel label identifies the interaction context; it is not equivalent to proof that the agent had or used file-edit permissions. Therefore, the correct response for file-edit capability is No.

The model responses and session activity demonstrate analysis, but they do not establish every possible capability of the agent. Effective log analysis distinguishes between evidence of observed actions and assumptions based on an agent’s name, panel, or intended role.

Study-guide topics: log interpretation, evidence-based evaluation, tool-call analysis, and capability verification.

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

Target

Correct selection

Condition identifying the pull request author

github.event.pull_request.user.login == ' github-copilot[bot] '

r.user.type ===

' User '

r.user.login !==

' github-copilot[bot] '

The first target must inspect the pull request’s author rather than the account that triggered the workflow. The expression github.event.pull_request.user.login identifies that author, whereas github.actor identifies the initiating actor and can differ during subsequent workflow activity. Using the bot identity supplied in the question, the selected condition identifies pull requests that the blocking step must reject.

The review predicate then requires an approved review, an existing reviewer object, a reviewer type of User, and a login different from the specified bot. These selections implement the intended distinction between a human approval and an automated review.

For merge enforcement, the resulting check must also be required by branch protection or a repository ruleset. A failed workflow alone does not universally prevent merging. The review-querying job additionally needs appropriate pull-request read permission. A production implementation should evaluate current effective approvals and rerun when reviews change, rather than accepting any historical approval indefinitely. It should also match the actual bot login recorded in its event payload.

Relevant curriculum topics are enforcing human review, identifying accountable actors, and implementing controls outside the model’s instructions.

Target

Correct selection

apply_auto.if

${{ needs.plan.outputs.risk == ' low ' }}

The automatic execution job must explicitly require the low-risk classification. The expression ${{ needs.plan.outputs.risk == ' low ' }} reads the risk value published by the prerequisite plan job and permits automatic application only when that value matches low. Medium-risk and high-risk plans therefore cannot enter this automatic execution path.

The complementary reviewed path should handle non-low classifications and reference an environment configured with required reviewers. The condition routes work according to risk; the environment protection rule supplies the actual approval barrier. Merely naming a job “manual” or displaying an approval message does not require human authorization.

The alternatives always(), success(), and failure() describe execution status rather than the plan’s risk classification. Checking only for medium would also fail to cover high-risk changes. The plan-producing job must publish the risk as an output, and each execution job must obtain the corresponding plan artifact before applying it.

This design applies human intervention where the task’s operational impact warrants it while allowing routine low-risk work to proceed automatically.

Relevant curriculum topics are risk-based autonomy, explicit authorization, and controlled execution paths.

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 .

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