TopexamのMicrosoftのGH-600試験トレーニング資料は豊富な経験を持っているIT専門家が研究したもので、問題と解答が緊密に結んでいるものです。それと比べるものがありません。専門的な団体と正確性の高いMicrosoftのGH-600問題集があるこそ、Topexamのサイトは世界的でGH-600試験トレーニングによっての試験合格率が一番高いです。Topexamを選んび、成功を選びます。
| Section | Weight | Objectives |
|---|---|---|
| Topic 1: Implement tool use and environment interaction | 20-25% | - Select and configure agent tools
|
| Topic 2: Perform evaluation, error analysis, and tuning | 15-20% | - Tune agent behavior based on evaluation results
|
| Topic 3: Prepare agent architecture and SDLC processes | 15-20% | - Define boundaries between planning, reasoning, and action
|
| Topic 4: Implement guardrails and accountability | 10-15% | - Implement guardrails and human-in-the-loop workflows
|
| Topic 5: Manage memory, state, and execution | 10-15% | - Persist agent state and manage context drift
|
| Topic 6: Orchestrate multi-agent coordination | 15-20% | - Manage the lifecycle of agents within multi-agent workflows
|
GH-600問題集はオンライン版、ソフト版、とPDF版がありますので、とても便利です。GH-600問題集を購入すれば、あなたはいつでもどこでも勉強することができます。GH-600問題集はIT専門家が長年の研究したことです。従って、高品質で、GH-600試験の合格率が高いです。毎年、たくさんの人がGH-600試験に参加し、合格しました。あなたはGH-600問題集を利用すれば、GH-600試験に合格できますよ。もし、将来に、IT専門家になります。
質問 # 19
You need to make changes to repo1 to support the planned changes for the agents.
What should you modify?
正解：D
解説：
Repository custom agent profiles belong in .github/agents/ and use Markdown files with agent configuration and instructions. When the intended changes concern the agents' roles, available tools, or operating guidance, these profiles are the appropriate implementation point.
An agent profile provides a durable definition that can be shared with other repository contributors. Keeping that definition under version control makes changes reviewable and enables the team to associate a particular agent configuration with the code revision used during evaluation. This is useful when diagnosing why an agent's behavior changed after its instructions or capabilities were modified.
Editor settings and MCP connection settings address different concerns. They can affect the environment in which an agent operates, but they do not replace the agent's own profile. Changing a server connection is appropriate for transport or authentication requirements; changing an agent profile is appropriate for agent behavior and capability selection.
The source selects C. Its applicability depends on the omitted planned changes actually concerning custom agent configuration.
Study-guide topics: agent profiles, configuration management, and SDLC traceability. Reference: GitHub-Creating custom agents.
質問 # 20
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
解説：
Scenario:
Agent environment: 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.
Security requirement: All API keys must be stored and accessed securely.
The correct solution is to store the API key as an Agents secret in the Copilot environment of the repository using the COPILOT_MCP_ name prefix, and then reference it in your MCP configuration.
Strict Prefix Enforcement: GitHub Copilot cloud agent isolates execution for security. It will only expose secrets and variables that explicitly begin with the COPILOT_MCP_ prefix to the MCP server configuration.
Environment Alignment: Storing it as a native Copilot agent secret ensures that when the remote Copilot agent spins up to execute your JSON configuration, it can securely bind and decrypt the secret directly into the server's runtime environment variables.
Config Separation: This practice keeps your sensitive production tokens entirely out of version- controlled mcp.json or .vscode/mcp.json tracking files.
Reference:
https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers
質問 # 21
You have multiple GitHub Copilot coding agents that run tasks concurrently.
You are monitoring the agents from the terminal by using the GitHub CLI.
An agent appears stalled.
You need to live stream the session log output.
What should you do?
正解：C
解説：
The gh agent-task view command supports inspecting an individual agent task. Combining --log with --follow selects session log output and continues following that output as the session progresses. The official CLI reference describes these flags as "Show agent session logs" and "Follow agent session logs," respectively.
This combination is appropriate when an agent appears stalled because a task-level status alone cannot explain what the agent is currently doing. Following the log allows the operator to observe additional activity, identify the last reported operation, and distinguish ongoing execution from a task awaiting intervention.
The list command is useful for discovering tasks and obtaining an overview of concurrent activity. It does not replace following the detailed output of the relevant session. The --jq parameter filters structured JSON output; it does not provide the continuous log-following behavior requested here. Opening a browser with a web option also fails the terminal streaming requirement.
Viewing logs is an observational action. It does not itself restart, cancel, or unblock the agent.
Study-guide topics: monitoring concurrent agents, execution visibility, and troubleshooting. Reference: GitHub CLI-gh agent-task view.
質問 # 22
You have a repository that uses the GitHub Copilot coding agent and supports hooks stored under .github/hooks.
You need a Shell command to run automatically whenever an agent execution fails.
Which type of hook should you use?
正解：B
解説：
To automatically run a Shell command whenever a GitHub Copilot coding agent execution fails, you should use the errorOccurred (also referred to as onErrorOccurred) hook.
Hook Mechanics & ConfigurationGitHub Copilot agent hooks are defined using JSON configuration files placed in the .github/hooks/ directory.
Event Type: errorOccurred (or onErrorOccurred depending on your specific environment and version).
Execution Behavior: When an execution fails, the agent stops, triggers this hook, and passes detailed error metrics and session context as a JSON payload to the script's standard input (stdin).
Incorrect:
[Not B]
sessionEnd - Agent session completes or is terminated.
Reference:
https://awesome-copilot.github.com/learning-hub/automating-with-hooks/
質問 # 23
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.
正解：
解説：
Explanation:
Box 1: The agent acknowledges the assignment and will create the draft pull request.
When an issue is assigned to the GitHub Copilot coding agent, the eyes emoji reaction indicates that the agent has acknowledged the task and is actively starting work in the background.
Box 2: The agent session is actively running and generating live logs.
The signal indicating that "the pull request timeline shows Copilot started work" means that the agent session is actively running and generating live logs.
When a pull request timeline shows that Copilot started work, it indicates that the execution context is actively working.
Actively working: Indicated when the pull request timeline explicitly logs that Copilot started work or updates the PR body with a list of in-progress sub-tasks.
Box 3: A human must manually approve and run the workflow.
When a draft pull request exists but GitHub Actions checks are not running, it indicates that the execution context is awaiting workflow approval.
Reference:
https://docs.github.com/en/copilot/how-tos/copilot-on-github/use-copilot-agents/kick-off-a-task
質問 # 24
......
銀行市場の急速な変化に合わせて、最新のGH-600学習教材を提供し、より多くの知識を確実に習得できるようにしています。また、GH-600トレーニングクイズが市場に登場して以来、プロの作業チームは長年の教育的背景と職業トレーニングの経験を積んでいるため、GH-600準備資料は優れた信頼性、完璧な機能、強力な実用性を備えています。私たちが提供できる多くの利点があるので、動かして、GH-600トレーニング資料を試してみませんか？
GH-600技術問題: https://www.topexam.jp/GH-600_shiken.html