Question 34 — AB-620 Practice Exam 5
For each Agent2Agent (A2A) protocol concept, drag it to the appropriate box in the Correct Match column to match it with its function.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
Provides a JSON discovery document, commonly published at /.well-known/agent.json, that identifies an agent and describes its capabilities and communication endpoint |
[Gap 1] |
| Represents the unit of work delegated by an orchestrator to an external agent for independent processing | [Gap 2] |
| Associates delegated work with an ongoing conversation so an external agent can maintain continuity across multiple turns | [Gap 3] |
| Carries structured message data such as text, tool results, metadata, and conversation history | [Gap 4] |
- Agent card
- HTTP connector response
- MCP tool invocation
- Context ID
- Message content parts
- Task
Correct answers
- Gap 1: Agent card
- Gap 2: Task
- Gap 3: Context ID
- Gap 4: Message content parts
Explanations
Correct Matches
Agent card – An agent card is the A2A discovery document that identifies an agent, describes its purpose and supported capabilities, and provides its communication endpoint. Copilot Studio can retrieve this document automatically from the agent endpoint during connection setup.
Task – A task is the work request sent to an A2A agent. The receiving agent processes the request independently by using its own reasoning and available capabilities.
Context ID – A context ID links delegated tasks to the same continuing conversation. It enables an A2A agent to preserve conversational continuity across multiple interactions.
Message content parts – Message content parts provide the structured payload exchanged through A2A, including text, tool call results, metadata, and conversation history.
Unused Items
HTTP connector response – A connector response contains data returned by an API or service and is not one of the core A2A structures used for agent discovery, delegated work, conversation continuity, or structured A2A messaging.
MCP tool invocation – An MCP tool invocation represents an orchestrator calling a tool exposed through Model Context Protocol rather than an A2A construct for agent discovery or task delegation.