Die Schulungsunterlagen zur Microsoft GH-600 Zertifizierungsprüfung von unserem ZertSoft finden bei Kandidaten große Resonanz und somit genießen einen guten Ruf, das heißt, solange Sie die Schulungsunterlagen zur Microsoft GH-600 Zertifizierungsprüfung von unserem ZertSoft wählen, werden Sie erfolgreich sein. Wir werden Ihnen alle Ihren bezahlten Summe zurückgeben, entweder Sie die GH-600 Prüfung nicht bestehen, oder die Testaufgaben von Microsoft GH-600 irgend ein Qualitätsproblem haben. Darüber hinaus können Sie einjährige Aktualisierung kostenlos genießen, nachdem Sie unsere Produkte gekauft haben.
| Section | Weight | Objectives |
|---|---|---|
| Manage memory, state, and execution | 10-15% | - Implement agent memory strategies
|
| Implement guardrails and accountability | 10-15% | - Implement guardrails and human-in-the-loop workflows
|
| Implement tool use and environment interaction | 20-25% | - Select and configure agent tools
|
| Orchestrate multi-agent coordination | 15-20% | - Configure observability for multi-agent behavior by using logs, artifacts, and operational signals
|
| Prepare agent architecture and SDLC processes | 15-20% | - Integrate agents into the software development lifecycle (SDLC)
|
| Perform evaluation, error analysis, and tuning | 15-20% | - Define success criteria and evaluation signals for agent tasks
|
Wir ZertSoft bieten Ihnen verschiede Unterlagensversionen, die Ihre Nutzung erleichtern können. Die PDF-Versionen können das Lesen erleichtern und Ihnen die aktuellen Microsoft GH-600 Prüfungsfragen zeigen, Die Software-Versionen sind die Simulationssoftwaren, die Ihre Vorbereitungssituation auf jeden Fall testen. Wenn Sie wissen wollen, ob Sie sich für Microsoft GH-600 Prüfung gut bereit sind, können Sie helfen, Ihre Stärke und Schwäche ganz schnell finden, um Ihren nächsten Lernplan zu erstellen.
46. Frage
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
Hotspot Question
You are evaluating how agent1 will behave after you implement the planned changes.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Antwort:
Begründung:
Explanation:
Scenario:
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.
Box 1: Yes
Box 2: Yes
Box 3: Yes
-[Related to another question in this scenario]
The correct action to take is to delete the line with tools: ['read','cearch','edit'] from the agent configuration.
Enabling All Tools: In GitHub Copilot Agent configuration specifications, omitting the tools key entirely or deleting it allows the agent to automatically inherit and utilize all available tools in the runtime environment. Explicitly hardcoding a restricted array limits its capabilities.
Targeted Instructions: Modifying the repository's configuration for the agent ensures that the specific product-api guidelines apply strictly to that custom agent without bleeding into general Copilot Chat or standard Copilot code reviews.
Reference:
https://docs.github.com/en/copilot/how-tos/copilot-sdk/features/mcp
47. Frage
You have a GitHub repository that uses the GitHub Copilot coding agent.
Developers need the Copilot coding agent to call an internal dependency-scanning API during its run. The API requires an access token.
You need to ensure that the Copilot coding agent can use the token during execution without accessing the repository's Actions secrets and variables. The solution must prevent exposing the token in plaintext.
What should you do?
Antwort: B
Begründung:
Option D places the token in the secret store intended for the coding agent's execution environment. This gives the agent's tools access to the credential without committing the credential to an agent profile or repository instruction file. The application can consume the injected environment variable when authenticating to the internal scanning API.
GitHub's current interface calls this dedicated category Agents secrets and variables . Its documentation states that secrets previously configured in the repository's copilot environment were automatically migrated to that category. Therefore, D represents the correct agent-specific mechanism using the terminology in the question.
Option A uses the separate Actions secret category, which is not automatically exposed to the cloud agent.
Options B and C place sensitive material in repository content, making the token accessible through file access and potentially retained in version history.
Current documentation also confirms that agent secrets are made available as environment variables and their values are masked in session logs. The integration should still avoid deliberately printing credentials or returning them in tool output.
Relevant curriculum topics are secure environment configuration, authenticated tool access, and separation of credential scopes.
Reference: Configure secrets and variables for Copilot cloud agent .
48. Frage
You have a GitHub Enterprise Cloud repository that uses the GitHub Copilot coding agent to resolve backlog issues by creating draft pull requests. The repository uses a GitHub Actions workflow for deployments to the production environment.
You discover that the workflow is being triggered before human review.
You need to configure GitHub controls to meet the following requirements:
* The workflow for the agent's draft pull requests must NOT run until a user that has write access approves the pull requests.
* Production deployment jobs must start only after a user with write access explicitly approves the jobs.
Which controls should you configure? To answer, drag the appropriate controls to the correct requirements.
Antwort:
Begründung:
Explanation:
Requirement
Control
Agent's draft pull request workflow control
Approve and run the workflows from the pull request merge box.
Production deployment job control
In the deployment job, configure the required reviewers for the production environment.
Approving and running workflows from the pull request interface controls whether workflows associated with the agent's draft pull request are allowed to begin. This provides the required human authorization before CI executes in that context.
Required reviewers on the production environment protect the deployment job itself. When the workflow reaches that environment, GitHub pauses the job until an authorized reviewer explicitly approves it. The approval is therefore applied at the production boundary, independently from the earlier pull-request workflow authorization.
A concurrency group controls overlap but does not require human approval. A custom deployment protection rule may be useful for specialized external validation, but it is not required by the stated scenario. Commit signing and run-summary inspection do not control the requested execution gates.
Study-guide topics: approval gates, protected environments, draft pull-request workflows, and production accountability.
49. Frage
You have a GitHub Actions workflow that starts multiple agent jobs in parallel.
You need to prevent two runs in the same job from executing simultaneously on the same branch. The solution must ensure, at most, one running instance and one pending instance per branch.
What should you add to the job?
Antwort: C
Begründung:
A job-level concurrency group coordinates executions that share the same group value across workflow runs.
The expression ci-${{ github.ref }} places executions for the same ref into the same group while allowing other refs to use independent groups.
Under the default concurrency behavior, a group permits at most one running execution and one pending execution. When another execution enters an occupied group, it becomes pending; an existing pending execution can be replaced by the newer one. This is a concurrency limit rather than a guarantee that every queued execution will eventually run.
The strategy.max-parallel setting controls simultaneous jobs generated by a matrix within a workflow run. It does not establish the required coordination between separate workflow runs. A matrix definition also does not create a shared concurrency lock. The cancel-in-progress property controls whether an active execution is cancelled, but a cancellation expression alone does not define the necessary group.
Group names should be chosen carefully when multiple jobs or workflows share a repository, because identical names can coordinate those executions too.
Study-guide topics: job synchronization, concurrency groups, and bounded execution. Reference: GitHub Actions-Workflow syntax: job concurrency.
50. Frage
You have a GitHub Enterprise Cloud organization that uses GitHub Actions for CI/CD.
You plan to enable an agent to update and deploy workflows that access production environment secrets.
You need to select an autonomy level for a compliance-sensitive workflow.
Which autonomy level should you select?
Antwort: D
Begründung:
Human-in-the-loop execution provides the appropriate autonomy level because the agent's actions affect production deployment and access to production secrets. The agent can prepare changes and perform permitted validation, while an authorized person approves the production transition. This retains useful automation while placing human judgment at the consequential execution boundary.
GitHub Actions environments support required reviewers. A job referencing a protected environment must satisfy its protection rules before proceeding. GitHub explicitly documents that when approval is required, the job cannot access environment secrets until a required reviewer approves it. The approval gate therefore controls an operational capability, rather than merely asking the model to behave cautiously.
Option A removes the oversight required by the scenario. Option B prevents the agent from performing the requested deployment work. Option D restricts execution to non-production environments and consequently does not provide a controlled route to production.
The workflow should bind deployment to the protected production environment and align reviewer permissions with organizational policy. Relevant curriculum topics are risk-based autonomy levels, explicit authorization for compliance-sensitive changes, and least-privilege execution.
References: Deployments and environments , Reviewing deployments .
51. Frage
......
Die Microsoft GH-600 Prüfungsfragen von ZertSoft sind in Übereinstimmung mit dem neuesten Lehrplan und der echten Microsoft GH-600 Zertifizierungsprüfung. Wir aktualisieren auch ständig unsere Schulungsunterlagen. Alle Produkte erhalten Sie mit einjährigen kostenlosen Updates. Sie können auch das Abozeit verlängern, so dass Sie mehr Zeit bekommen, um sich besser auf die Prüfung vorzubereiten. Wenn Sie zögert sind oder nicht dafür entscheiden können, ob Sie die Microsoft GH-600 Schulungsunterlagen von ZertSoft kaufen oder nicht. Dann können Sie die Demo umsonst auf der ZertSoft website herunterladen. Wenn es Ihnen passt, dann gehen Sie zum Kaufen ohne Bereuung.
GH-600 Online Prüfungen: https://www.zertsoft.com/GH-600-pruefungsfragen.html