MicrosoftのGH-600ソフトを使用するすべての人を有効にするために最も快適なレビュープロセスを得ることができ、我々は、MicrosoftのGH-600の資料を提供し、PDF、オンラインバージョン、およびソフトバージョンを含んでいます。あなたの愛用する版を利用して、あなたは簡単に最短時間を使用してMicrosoftのGH-600試験に合格することができ、あなたのIT機能を最も権威の国際的な認識を得ます！
| Section | Weight | Objectives |
|---|---|---|
| Topic 1: Implement agents and multi-agent systems | 30% | - Orchestrate multi-agent collaboration
|
| Topic 2: Integrate tools, data, and services | 25% | - Incorporate external tools and APIs
|
| Topic 3: Test, deploy, and monitor agentic AI systems | 20% | - Deploy and monitor agents at scale
|
| Topic 4: Design agentic AI solutions | 25% | - Define requirements for agentic systems
|
当社のソフトウェアをダウンロードして30時間以内に練習する場合のみ、自信を持ってテストに参加できます。 GH-600試験トレントは期間限定の試験とオンラインエラー修正をシミュレートできるため、GH-600試験の準備にかかる時間と労力は他の学習教材よりも少なくて済みます。 20時間または30時間を費やすだけでGH-600証明書を手に入れることは非常に経済的です。これは通常、将来のキャリアにとって有益です。したがって、テストを準備するには、GH-600ガイドトレントを購入するのが最善かつ賢明な選択です。
質問 # 45
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
Drag and Drop Question
You need to implement the security requirements for agent1.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
正解：
解説：
Explanation:
Scenario:
Security requirements, Litware identifies the following security requirements: Only the members of SG_Review must be able to approve agent1 plan outputs.
Agent environment: The product-api repository uses a GitHub Copilot coding agent named agent1 Step 1: In the product-api repositary settings,..
Create a new environment and add SG_review as the required reviewers.
Step 2: To the agent1 workflow,..
Create a new workflow related to the plan outoput.
Step 3: Add an execute job...
Create a job referencing the plan and the environment.
質問 # 46
You are about to start a complex refactoring task in the GitHub Copilot CLI.
Before Copilot makes any changes, you need to review and agree on the approach.
What should you do first?
正解：B
解説：
GitHub Copilot CLI plan mode is specifically designed for situations in which an implementation strategy must be developed and reviewed before code modifications begin. In plan mode, Copilot can inspect and analyze the repository, ask clarifying questions, and construct a structured implementation plan while protecting project files from normal editing operations. The resulting plan can then be reviewed and approved before Copilot proceeds with implementation. GitHub explicitly describes plan mode as a mechanism for identifying misunderstandings before code is written and maintaining human control over complex, multi-step work.
Option A is incorrect because --agent=AGENT selects a custom agent; it does not establish a planning-and-approval phase. Option B is the opposite of the requirement: --allow-all grants Copilot broad permission to use tools, paths, and URLs without individual approval. Option D is also incorrect because /compact relates to managing conversation/context size rather than establishing an implementation plan.
Therefore, switching to plan mode is the appropriate first action when the development process requires human review and agreement before changes are applied.
Study Guide Reference Topics: Prepare agent architecture and SDLC processes; human-in-the-loop development; planning before implementation; controlled agent execution.
質問 # 47
You have a GitHub Copilot coding agent named Orchestrator that runs a multi-phase workflow by using the following subagents:
Explorer gathers context by using read-only tools.
Modifier applies focused edits.
You are adding a new agent named Summarizer that generates a concise summary after modifications are complete. Summarizer includes the following YAML frontmatter:
---
name: Summarizer
description: Produce a concise summary of recent changes
tools: ['fetch']
user-invocable: false
disable-model-invocation: true
---
The Orchestrator agent lists all three agents in its agents property.
After adding the Summarizer agent, Orchestrator successfully runs Explorer and Modifier but fails to run Summarizer.
What is a possible cause of the failure?
正解：A
解説：
D is the best answer among the available choices. The key detail is that Summarizer is explicitly listed in Orchestrator's agents property. Current VS Code agent orchestration behavior states that explicitly listing a custom agent in the parent's agents array overrides disable-model-invocation: true for that coordinator. Therefore, option A does not explain the failure in this scenario.
Likewise, user-invocable: false does not prohibit programmatic or subagent invocation. It merely prevents users from manually selecting that agent from the agent picker; this setting is commonly used specifically for worker agents that should only operate as subagents.
Option C is also incorrect because Summarizer's function is to produce a summary, not modify repository content. It therefore does not inherently require editing tools.
The agents property establishes which subagents the coordinator is permitted to invoke; it does not itself define the sequence of workflow transitions. Handoffs are the mechanism for defining explicit guided transitions between agents. If the workflow expects Summarizer to run as the next defined phase but no corresponding transition/invocation exists, the missing handoff can explain why execution stops after Modifier.
Study Guide Reference Topics: Orchestrate Multi-Agent Coordination; custom subagents; agents restrictions; agent invocation controls; sequential handoffs and workflow transitions.
質問 # 48
You have a GitHub Copilot coding agent that has completed a pull request for a security fix in your repository.
Before merging, you need to evaluate the quality of the agent's work by using both automated evaluation signals and human review.
You review the session log and the pull request.
What are two automated security scanning signals available for the pull request? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
正解：A、B
解説：
CodeQL findings and secret-detection results are the intended selections. CodeQL analyzes code for patterns associated with vulnerabilities and programming errors. Secret scanning identifies sensitive material, including supported credential and token patterns, that may have been introduced into the generated changes. Both provide concrete security evidence that a reviewer can evaluate alongside the proposed fix.
Linting generally evaluates coding conventions and selected correctness rules; a generic linting failure is not necessarily a security finding. Median time to merge measures delivery performance rather than the security of a particular change.
The wording of option D creates an important technical distinction. Dependency vulnerability detection is also a genuine automated security signal. GitHub explicitly documents dependency analysis alongside CodeQL and secret scanning in the coding agent's security checks. Repository-level dependency alerts, however, may concern existing vulnerabilities rather than changes introduced by this pull request. B and C are the clearest intended pair, but D cannot be dismissed as unrelated to security.
Reviewers should determine whether each finding applies to the proposed changes and whether the underlying vulnerability has actually been resolved.
Relevant curriculum topics are automated evaluation signals, security scanning, and evidence-based assessment of agent outputs.
Reference:
質問 # 49
You have a GitHub repository that stores custom GitHub Copilot agents in the .github/agents/ folder.
You have an agent named lead-dev.agent.md that must invoke a specialist subagent named security-reviewer.
Evaluation results show that lead-dev attempts to invoke security-reviewer, but the subagent call fails to run.
You need to ensure that lead-dev can invoke security-reviewer.
How should you complete the YAML frontmatter of the agent profile? To answer, drag the appropriate values to the correct targets.
正解：
解説：
質問 # 50
......
ShikenPASSは生徒を常に惹きつけ、Microsoft熱心な顧客からの世界的なフィードバックの進歩に情熱を移します。GH-600試験で彼らが夢をかなえるためにこの分野でナンバーワンであることを証明します。 GH-600試験問題の質の高さを保証しているため、GH-600練習教材はより優れた教育効果をもたらします。 また、学習の後方情報の蓄積が生徒に大きな負担を感じさせる代わりに、最新のGH-600のDeveloping in Agentic AI Systems試験ガイドは、あらゆる種類の生徒の有効性または正確性のニーズを満たすことができます。
GH-600出題内容: https://www.shikenpass.com/GH-600-shiken.html