Passing exam with GH-600 latest training materials

You have a GitHub repository that contains the following custom agent files:
A file named planner.agent.md that includes YAML frontmatter with a handoffs entry that has label: Start Implementation, agent: implementer, and prompt: Now implement the plan outlined above.
A file named implementer.agent.md that is in the same directory as planner.agent.md and includes YAML frontmatter that has name: IMPLEMENTER.
You add a third agent file named review.agent.md that includes name: code-review in the YAML frontmatter.
You make the following changes to planner.agent.md:
Update the existing handoff to include send: true and model: GPT-5.2 (copilot).
Add a second handoff that has label: Run Review, agent: code-review, and prompt: Review the code changes made in the previous step.

You need to resolve the scoping issue associated to agent1.
What should you do?

• A. Add a permissions block to the agent1 workflow in product-api.
• B. Create a ruleset for billing-service and infra-terraform that blocks push access from the github-actions bot account.
• C. Create a fine-grained personal access token (PAT) scoped to product-api and store the PAT as a GitHub Actions secret for agent1 to use.
• D. To the profile of agent1, add a custom instruction specifying that the agent must NOT access billing-service or infra-terraform.

You have a GitHub repository that uses GitHub Actions for CI on pull requests. The repository contains a Node.js app.
You have a GitHub Copilot coding agent that opens pull requests for backlog items, and your company requires automated checks for agent-generated changes.
You plan to standardize success criteria so that pull requests created by agents only succeed when unit tests pass and CodeQL analysis completes.
You need to configure a GitHub Actions workflow that runs on pull requests, executes unit tests, and performs CodeQL analysis.
How should you complete the workflow? To answer, drag the appropriate values to the correct targets.

You have a GitHub repository that uses the GitHub Copilot coding agent. The repository uses strict branch protections on the main branch.
You maintain a long-lived branch named release/1.4 that has different dependencies and CI checks.
You need the agent to create a hotfix that is implemented and validated against the release/1.4 branch. The solution must prevent the agent from basing its work on main.
What should you do?

• A. In .github/copilot-instructions.md, instruct the agent to always check out release/1.4 instead of main when creating hotfixes.
• B. Require human reviews on changes to main.
• C. Add concurrency: release/1.4 to .github/workflows/copilot-setup-steps.yml.
• D. Select the repository and the release/1.4 branch in the Copilot agents UI before you run the agent task.

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?

• A. Create a new issue and assign the issue to Copilot.
• B. Close and reopen the issue.
• C. Select Approve and run workflows in the pull request merge box.
• D. Post a pull request comment that mentions @copilot.