A repository administrator customizes MCP access for Copilot cloud agent. They want broader GitHub access than the default current-repository token provides, but they also want to limit which GitHub MCP tools the agent can use. Evaluate the following statements. 1. The configuration uses a remote HTTP MCP server entry. 2. A remote OAuth-only MCP server is supported for Copilot cloud agent. 3. The token reference uses the required COPILOT_MCP_ secret prefix.
{
"mcpServers": {
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/",
"headers": {
"Authorization": "Bearer ${COPILOT_MCP_GITHUB_PAT}"
},
"tools": [
"get_issue",
"list_pull_requests",
"create_issue"
]
}
}
}Choose an answer
Tap an option to check your answer.
Correct answer: 1=Yes 2=No 3=Yes.
Why this is the answer
Statement 1 is Yes because the configuration explicitly defines an mcpServers entry named "github" with "type": "http", indicating a remote HTTP MCP server. Statement 2 is No because Copilot cloud agents do not support OAuth-only MCP servers; they typically rely on Personal Access Tokens (PATs) or similar token-based authentication for remote server access, as shown in the example. Statement 3 is Yes because the Authorization header references "${COPILOTMCPGITHUBPAT}", which correctly uses the COPILOTMCP secret prefix required for Copilot to identify and inject the appropriate secret for MCP server authentication.
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