Question 47 — AB-650 Practice Exam 4
For each ongoing Agent Registry curation action, drag it to the appropriate box in the Correct Match column to match it with its governance effect.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
| Brings an internally built agent package into the Registry so that it can be governed | [Gap 1] |
| Transfers responsibility for a supported shared agent to another person in the organization | [Gap 2] |
| Permanently removes an agent and its associated files | [Gap 3] |
| Allocates or deallocates the Azure compute resources used by a Microsoft Foundry agent | [Gap 4] |
- Assign new owner
- Block a tool
- Upload a custom agent
- Delete an agent
- Approve a tool request
- Start or stop a Microsoft Foundry agent
Correct answers
- Gap 1: Upload a custom agent
- Gap 2: Assign new owner
- Gap 3: Delete an agent
- Gap 4: Start or stop a Microsoft Foundry agent
Explanations
Correct Matches
Upload a custom agent – Uploading places an internally created agent into the Microsoft 365 Agent Registry so that administrators can manage its publication, deployment, and ongoing governance.
Assign new owner – This action transfers ownership of a supported shared agent to another member of the organization.
Delete an agent – Deletion permanently removes the selected agent and its associated files rather than merely disabling access to it.
Start or stop a Microsoft Foundry agent – These actions provision or deallocate the Azure compute resources supporting a Microsoft Foundry agent deployment.
Unused Items
Block a tool – Tool blocking controls whether agents and workflows can invoke a registered tool. It is not one of the actions used to maintain ownership, inventory, or compute state for an individual agent.
Approve a tool request – Approval belongs to the review process for requested tools or servers. It does not perform one of the ongoing agent-curation operations represented by these mappings.