You have a GitHub repository that uses GitHub Copilot code review on pull requests.
You plan to add repository-wide code review guidance that will apply to all files.
You need Copilot code review to consistently apply the guidance during pull request reviews.
What should you do?

• A. Modify the .github/pull_request_template.md file.
• B. Update the instructions in the .github/agents/*.agent.md files.
• C. Create a .github/copilot-instructions.md file.
• D. Create a .github/instructions/copilot.instructions.md file.

설명: (Fast2test 회원만 볼 수 있음)

A team assigns an issue to the GitHub Copilot coding agent by using the following one-line description: Fix the login bug.
Copilot creates a pull request, but the pull request is missing changes and has an incorrect scope.
How should you resolve the issue?

• A. Update the Model Context Protocol (MCP) server rate limits.
• B. Enable Copilot memory.
• C. Allocate more resources to copilot-setup-steps.yml.
• D. Add a clear description of the problem to the issue.

설명: (Fast2test 회원만 볼 수 있음)

Hotspot Question
You have a GitHub repository that uses the GitHub Copilot coding agent to resolve issues and create draft pull requests.
You assign an issue to Copilot. Copilot creates a draft pull request. The pull request timeline shows Copilot started work, followed by status updates. The most recent status update is 55 minutes old.
You discover that the agent is no longer making progress.
You need to ensure that the work resumes without redoing the completed steps or changing the previously chosen approach.
What should you do? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Explanation:
Box 1: Select View session from the pull request
To best confirm the agent's progress, troubleshoot the stagnation, and ensure the work resumes seamlessly from where it left off, you should interact directly with the agent's active workspace.
Open the Session View: Navigate to the pull request on GitHub and click the View session button.
This opens the step-by-step agent workflow and reasoning interface.
Inspect the Logs: Review the detailed execution log in the session timeline to identify exactly where the background task (running in GitHub Actions) stalled or encountered an error.
Steer or Prompt to Resume: Instead of unassigning and reassigning the issue (which completely restarts the task from scratch), use the chat input or steering tools directly inside the View session page or Agents panel to nudge Copilot. Providing a clarification prompt allows the agent to continue its current approach without losing completed steps.
Box 2: Post a pull request comment that mentions @copilot
You can resume the work by commenting on the pull request and mentioning @copilot, along with a prompt instructing it to continue.When a GitHub Copilot coding agent stalls or pauses on a draft pull request, posting a comment mentioning @copilot wakes the agent back up. Because the agent evaluates the entire conversation history, code changes, and task checklists within that pull request lifecycle, it will resume from its last saved state. It maintains the previously chosen approach and carries on with the remaining items without repeating already completed steps.
Reference:
https://docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent/troubleshoot-cloud-agent

An agentic coding session in the terminal has grown too long, and you want to discard all prior conversation history and start clean, without summarization. Which slash command should you run?

• A. /usage
• B. /compact
• C. /reset-context
• D. /clear

설명: (Fast2test 회원만 볼 수 있음)

Your organization wants to ensure the Copilot coding agent cannot push directly to main, and all its changes must go through a pull request review process like any other contributor. What enforces this?

• A. /context
• B. copilot-instructions.md
• C. Standard branch protection rules on the main branch
• D. .copilotignore

설명: (Fast2test 회원만 볼 수 있음)