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

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.

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 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.

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

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.

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.

Repository memory is supported by citations to the code that establishes the remembered fact. When a fact appears relevant to a new task, Copilot checks its supporting citations against the current branch before relying on it. This validation prevents an observation from an earlier repository state from being treated automatically as current truth.

The branch check is particularly important when work spans release branches, experimental changes, or pull requests that were never merged. A memory may have been accurate when created but no longer describe the code now being edited. If its supporting code is absent or no longer supports the claim, the remembered fact should not influence the task.

Option A incorrectly describes memory as permanently retained information requiring only manual intervention. Option B substitutes pull-request disposition for validation of the underlying evidence. Option C incorrectly treats repository knowledge as usable only by its original contributor.

The governing mechanism is evidence validation at the point of use, not an assumption that all previously stored information remains authoritative.

Relevant curriculum topics are task-relevant memory, stale-context prevention, and maintaining state consistency across branches and sessions.

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.

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

The primary failure is insufficient task definition. “Fix the login bug” does not identify the observed behavior, expected behavior, reproduction conditions, affected component, or completion criteria. The agent must infer these details, creating a substantial risk of incomplete changes or work outside the intended scope. A clear issue description supplies the information needed to construct and implement an appropriate plan.

For this scenario, the description should identify how the login failure occurs, which authentication path is affected, what successful behavior looks like, and which existing behavior must remain intact. Relevant error messages, reproduction steps, and expected tests make the task independently verifiable. These details turn an ambiguous request into a bounded engineering assignment.

Enabling memory does not supply missing requirements reliably. MCP rate limits govern service interaction rather than task clarity. Additional setup resources address environmental capacity or dependency preparation, not uncertainty about what must change.

The corrective action therefore belongs at task intake, where developers define the agent’s inputs and success conditions. The relevant curriculum topics are defining agent inputs, outputs, and success criteria and mitigating poorly scoped task assignments.

The filter action:artifact.destroy selects the audit event associated with manual deletion of a workflow artifact. It directly targets the activity described in the scenario, allowing the investigator to examine the recorded actor and associated event details.

A repository filter narrows the search to a particular repository but does not distinguish artifact deletion from other recorded operations. It can usefully accompany the action filter when investigating a specific project. A workflow-run action concerns workflow execution rather than the manual removal of its stored artifacts. The generic operation:remove option does not select the documented artifact deletion event.

The investigation should correlate the deletion event with its timestamp and repository information, then inspect the actor recorded for that event. This identifies the account associated with the action; additional context may be needed when an application or automated identity performed it.

Artifact retention and audit logging serve separate purposes. Retention controls how long outputs are normally preserved, while the audit log records relevant administrative and user activity. Searching the audit log does not restore deleted content.

Study-guide topics: accountability, evidence preservation, actor attribution, and audit trails. Reference: GitHub—Organization audit log events .

Target

Correct selection

Checkout ref

${{ github.sha }}

File checked by test -f

github/agents/rollout-bot.agent.md

Profile passed to the deployment script

github/agents/rollout-bot.agent.md

The workflow must deploy an agent profile from a specific repository snapshot. Setting the checkout reference to ${{ github.sha }} identifies the commit associated with the workflow event, rather than following a branch reference that might move as new commits arrive. The checkout action supports selecting a commit SHA through its ref input.

Both subsequent operations must use .github/agents/rollout-bot.agent.md. The existence check confirms that the expected profile is present in the checked-out revision, and the deployment script receives that same version-controlled file. Using a different path would break the relationship between the validated profile and the deployed profile.

Rollback requires one additional operational distinction: reverting a change creates a new commit containing the restored content. The deployment must run against that revert commit. Re-running the original failed workflow run retains its original SHA and does not automatically deploy the later revert.

This approach keeps agent behavior, repository history, and deployment provenance aligned, making the profile’s effective version identifiable and recoverable.

Relevant curriculum topics are durable state, controlled rollback, and continuity of agent configuration across executions.