有名なブランドCertJukenとして、非常に成功しているにもかかわらず、Microsoft現状に満足することはなく、常にGH-600試験トレントの内容を更新する用意があります。 最も重要なことは、GH-600ガイドトレントの新しいバージョンをコンパイルしている限り、購入後1年間無料で最新バージョンのGH-600トレーニング資料をお客様に送信します。 GH-600試験に合格するのに役立つ、絶え間なく更新される試験の要求に合わせて、Developing in Agentic AI Systemsガイド急流を引き続きお届けします。
| Section | Weight | Objectives |
|---|---|---|
| Manage memory, state, and execution | 10–15% | - Implement agent memory strategies
|
| Implement guardrails and accountability | 10–15% | - Define autonomy levels
|
| Prepare agent architecture and SDLC processes | 15–20% | - Define boundaries between planning, reasoning, and action
|
| Implement tool use and environment interaction | 20–25% | - Operate agents with safe execution paths and robust error handling
|
| Perform evaluation, error analysis, and tuning | 15–20% | - Analyze agent failures and identify root causes
|
| Orchestrate multi-agent coordination | 15–20% | - Configure observability for multi-agent behavior by using logs, artifacts, and operational signals
|
我々は弊社のGH-600問題集を利用するあなたは一発で試験に合格できると信じています。我々はIT業界の権威で専門家たちは数年以来の努力を通して、GH-600問題集の開発に就職しています。我々のGH-600問題集を利用してから、あなたは短い時間でリラクスで試験に合格することができるだけでなく、試験に必要な技能を身につけることもできます。
質問 # 89
You assigned an issue to the Copilot coding agent, and it opened a pull request. You want to inspect exactly what code changes were made before merging. Which CLI slash command lets you view the change set directly in the terminal?
正解：C
解説：
/diff shows the file-level changes the agent has made during the session, letting you review modifications before committing or merging, without leaving the terminal.
質問 # 90
You have a GitHub repository that uses the GitHub Copilot coding agent.
The agent is assigned to a long-running issue and has already opened a draft pull request linked to the issue. The pull request timeline shows Copilot started work and the pull request description shows periodic status updates.
After 70 minutes, the pull request stops receiving new commits, and the agent session log indicates that the session has timed out. In a pull request comment thread, the agent then proposes changes that no longer match the latest repository guidance.
You need to resume execution in a way that reestablishes the correct context and produces new commits in the existing draft pull request.
What should you do?
正解：D
解説：
A comment mentioning @copilot on the existing pull request provides the direct continuation mechanism. GitHub documents that this can start a new agent session and, by default, push additional commits to the pull request's branch. The comment should explicitly identify the latest repository guidance and the work that remains, correcting the context that produced the outdated proposal.
This approach preserves the existing branch, accumulated changes, review discussion, and relationship to the original issue. It also gives the agent a clear instruction tied to the artifact that must be updated. The commenter must have the required repository write access.
Creating another issue would establish a separate assignment and could duplicate work. Approve and run workflows authorizes GitHub Actions validation; it does not itself resume the coding agent's implementation session. Closing and reopening the issue is likewise not the direct pull-request continuation control.
The useful recovery action therefore combines a new execution trigger with an explicit statement of current intent. Restarting without correcting the outdated requirement could reproduce the same drift.
Relevant curriculum topics are resuming execution, restoring task context, and maintaining continuity without discarding prior work.
Reference:
質問 # 91
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
質問 # 92
Your team wants Copilot's suggestions to reflect knowledge of internal library APIs that are not publicly documented and not present in the codebase being edited. What is the most appropriate solution?
正解：C
解説：
An MCP server exposing the internal documentation is the appropriate solution because Model Context Protocol extends Copilot with information and capabilities located outside the repository's native context. GitHub describes MCP as a mechanism for integrating Copilot with external systems, enabling it to obtain context or invoke functionality that would otherwise be unavailable from the codebase alone.
This architecture is appropriate for proprietary library documentation because the internal API knowledge can remain centrally maintained rather than being duplicated into every repository. The MCP integration can expose a controlled documentation lookup/search capability, allowing Copilot to retrieve relevant definitions, usage patterns, or internal API information when required.
Option A is inferior because copilot-instructions.md is designed for concise repository-specific instructions and conventions, not as a substitute for a potentially large external documentation corpus. GitHub recommends it for persistent guidance such as building, testing, and repository conventions. Option C would remove context rather than add proprietary knowledge. Plan mode affects workflow sequencing and does not provide new external information.
Study Guide Reference Topics: Implement Tool Use and Environment Interaction; MCP-based context augmentation; external knowledge integration; tool-mediated retrieval.
質問 # 93
You assigned an issue to the Copilot coding agent, and it opened a pull request. You want to inspect exactly what code changes were made before merging. Which CLI slash command lets you view the change set directly in the terminal?
正解：C
解説：
The correct command is /diff. GitHub Copilot CLI provides /diff specifically for reviewing code changes directly from the terminal. GitHub's current CLI command reference defines /diff as a command that reviews changes in the current directory and can automatically switch to a branch comparison when the working tree is clean. This makes it the appropriate command when validating an agent-generated change set before accepting or merging the work.
The other commands serve different purposes. /context displays context-window utilization, including token allocation and remaining context capacity; it does not show code modifications. /compact summarizes conversation history to reclaim context-window space during long-running sessions. /plan creates an implementation plan before coding and restricts normal project-file modifications while the plan is being prepared.
Using /diff supports an essential human-in-the-loop control in agentic software development: generated code should be inspected before it crosses a merge or deployment boundary. Reviewing the diff exposes additions, deletions, and modifications so that unintended or unsafe changes can be identified before integration.
Study Guide Reference Topics: Implement Tool Use and Environment Interaction; agent-generated code review; human-in-the-loop validation; controlled execution and change inspection.
質問 # 94
......
あなたは進歩を遂げたいですか。あなたはどのようにして勉強するのかわかりますか。この時、おそらく私たちのGH-600試験準備資料の助けが必要でしょう。私たちのGH-600試験準備資料を使用している人の99％がすでに望む証明書を持っていました。私たちのGH-600試験準備資料を買う限り、あなたも成功できます！
GH-600キャリアパス: https://www.certjuken.com/GH-600-exam.html