A developer is testing a repository-level custom agent named workflow-pr-agent. The agent profile limits the agent to read, search, edit, and github/*. During troubleshooting, the developer instead starts the default Copilot CLI session and adds a broad external MCP server. Which change should you make first? Select one answer.
cd ~/work/payments-api
copilot
/mcp add
# Name: ticketing-prod
# Command: npx @example/ticketing-mcp
# Tools: *
# Saved to ~/.copilot/mcp-config.json
# Prompt:
# Review issue #184, inspect the failed PR checks, update the workflow,
# and prepare a small pull request for review.Choose an answer
Tap an option to check your answer.
Correct answer: Invoke the scoped repository custom agent.
Why this is the answer
The developer intends to use the workflow-pr-agent, a repository-level custom agent, but mistakenly started a default Copilot CLI session and added a broad external MCP server. The workflow-pr-agent is specifically designed for repository tasks and has predefined permissions (read, search, edit, github/). To leverage its capabilities and adhere to its scoped permissions, the developer must explicitly invoke this custom agent. Enabling --allow-all would grant excessive permissions, bypassing the intended scope of the custom agent. Moving MCP config into workflow YAML or adding every ticketing MCP tool are irrelevant as the immediate goal is to utilize the existing, scoped custom agent for its intended purpose.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed