Microsoft AB-100 Grounding Pipelines and Agent Extensibility Practice Test

Practice Exams:

View All

Microsoft AB-100 Grounding Pipelines and Agent Extensibility Practice Test

Topic 07 covers Grounding Pipelines and Agent Extensibility for Microsoft AB-100, using the current skills measured as of July 22, 2026 and primary Microsoft documentation. For broader exam preparation, review the AB-100 Exam Dumps page. These are original practice questions, and every option includes a scenario-specific explanation.

Question 1

A pilot for grounding pipelines and agent extensibility reaches a decision point for the agent extensibility team. The current solution leaves chunk boundaries that preserve business meaning unresolved, and the gap is now affecting the stated business or technical requirement. What is the best design choice?

Choose chunk boundaries that preserve business meaning.
Treat tuning data separately from runtime grounding data and evaluate each with its own evidence.
Choose a tool extension over duplicating business logic in a prompt.
Define a recovery boundary for an unexpected UI layout.
Resolve tool schema drift before exposing a changed server.

Correct Answer: A

Correct Answer

Answer A is correct because This is correct because it applies the reserved architecture decision—choose chunk boundaries that preserve business meaning—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘separate tuning data from runtime grounding data’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer C is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose a tool extension over duplicating business logic in a prompt’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer D is incorrect because This is not the best choice because it addresses the adjacent decision ‘define a recovery boundary for an unexpected ui layout’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘resolve tool schema drift before exposing a changed server’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 2

A data platform group is reviewing grounding pipelines and agent extensibility. The review has identified a specific issue: normalize inconsistent units before grounding ingestion. Which approach best fits the requirement?

Define action parameters that make selection unambiguous.
Normalize inconsistent units before grounding ingestion.
Require confirmation before a UI automation submits a costly change.
Plan dependency isolation for a custom model outage.
Treat MCP integration separately from agent-to-agent delegation and evaluate each with its own evidence.

Correct Answer: B

Correct Answer

Answer B is correct because This is correct because it applies the reserved architecture decision—normalize inconsistent units before grounding ingestion—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘define action parameters that make selection unambiguous’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer C is incorrect because This is not the best choice because it addresses the adjacent decision ‘require confirmation before a ui automation submits a costly change’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer D is incorrect because This is not the best choice because it addresses the adjacent decision ‘plan dependency isolation for a custom model outage’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘separate mcp integration from agent-to-agent delegation’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 3

The enterprise integration team is preparing an architecture decision record for grounding pipelines and agent extensibility. The review has identified a specific issue: propagate deletions into a retrieval index. Which action should the team take next?

Design declarative extension with explicit knowledge and actions.
Choose computer use because a required legacy UI lacks an API is the decisive constraint.
Propagate deletions into a retrieval index.
Choose chunk boundaries that preserve business meaning.
Design a connector boundary around a reusable business capability.

Correct Answer: C

Correct Answer

Answer C is correct because This is correct because it applies the reserved architecture decision—propagate deletions into a retrieval index—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘design declarative extension with explicit knowledge and actions’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose computer use when a required legacy ui lacks an api’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer D is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose chunk boundaries that preserve business meaning’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘design a connector boundary around a reusable business capability’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 4

A data platform group is reviewing grounding pipelines and agent extensibility. The solution is changing across transformed documents, and the business requires continuity of source citations through the transition. Which approach best fits the requirement?

Prefer a stable API when both integration paths meet requirements.
Choose a custom engine where orchestration control is mandatory.
Validate source permissions, grounding quality, tool contracts, and failure behavior with representative enterprise data.
Handle a tool result that does not meet the expected contract.
Preserve source citations across transformed documents.

Correct Answer: E

Correct Answer

Answer E is correct because This is correct because it applies the reserved architecture decision—preserve source citations across transformed documents—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘prefer a stable api when both integration paths meet requirements’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose a custom engine where orchestration control is mandatory’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer C is incorrect because This is a useful verification step after the primary architecture decision, but it does not by itself resolve the decision the scenario asks for. The design choice must be made first, and this evidence can then confirm that the chosen approach behaves as intended.

Answer D is incorrect because This is not the best choice because it addresses the adjacent decision ‘handle a tool result that does not meet the expected contract’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 5

A pilot for grounding pipelines and agent extensibility reaches a decision point for the agent extensibility team. The current solution leaves refresh behavior for rapidly changing reference data unresolved, and the gap is now affecting the stated business or technical requirement. What should the architect recommend?

Design refresh behavior for rapidly changing reference data.
Define a recovery boundary for an unexpected UI layout.
Scope a Copilot extension to a supported user surface.
Propagate deletions into a retrieval index.
Choose MCP because existing tools expose a compatible service is the decisive constraint.

Correct Answer: A

Correct Answer

Answer A is correct because This is correct because it applies the reserved architecture decision—design refresh behavior for rapidly changing reference data—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘define a recovery boundary for an unexpected ui layout’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer C is incorrect because This is not the best choice because it addresses the adjacent decision ‘scope a copilot extension to a supported user surface’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer D is incorrect because This is not the best choice because it addresses the adjacent decision ‘propagate deletions into a retrieval index’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose mcp when existing tools expose a compatible service’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 6

A production-readiness review of grounding pipelines and agent extensibility gives the tool integration review new evidence. The review has identified a specific issue: integrate a custom model behind a versioned contract. Which approach best fits the requirement?

Integrate a custom model behind a versioned contract.
Integrate an existing agent without rebuilding its business logic.
Require confirmation before a UI automation submits a costly change.
Preserve source citations across transformed documents and verify continuity after the change.
Curate a minimal tool set for agent discoverability.

Correct Answer: A

Correct Answer

Answer A is correct because This is correct because it applies the reserved architecture decision—integrate a custom model behind a versioned contract—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘integrate an existing agent without rebuilding its business logic’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer D is incorrect because This is not the best choice because it addresses the adjacent decision ‘preserve source citations across transformed documents’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘curate a minimal tool set for agent discoverability’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 7

Before a wider rollout of grounding pipelines and agent extensibility, the agent extensibility team reviews the current evidence. The current solution leaves an endpoint abstraction that permits model replacement unresolved, and the gap is now affecting the stated business or technical requirement. What is the best design choice?

Choose chunk boundaries that preserve business meaning.
Choose a tool extension over duplicating business logic in a prompt.
Resolve tool schema drift before exposing a changed server.
Design refresh behavior for rapidly changing reference data.
Choose an endpoint abstraction that permits model replacement.

Correct Answer: E

Correct Answer

Answer E is correct because This is correct because it applies the reserved architecture decision—choose an endpoint abstraction that permits model replacement—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose chunk boundaries that preserve business meaning’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose a tool extension over duplicating business logic in a prompt’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer C is incorrect because This is not the best choice because it addresses the adjacent decision ‘resolve tool schema drift before exposing a changed server’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer D is incorrect because This is not the best choice because it addresses the adjacent decision ‘design refresh behavior for rapidly changing reference data’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 8

During a design workshop on grounding pipelines and agent extensibility, the enterprise integration team identifies a constraint. Stakeholders are treating tuning data and runtime grounding data as the same decision, which is obscuring the actual control boundary. Which approach best fits the requirement?

Define action parameters that make selection unambiguous.
Treat MCP integration separately from agent-to-agent delegation and evaluate each with its own evidence.
Validate source permissions, grounding quality, tool contracts, and failure behavior with representative enterprise data.
Separate tuning data from runtime grounding data.
Normalize inconsistent units before grounding ingestion.

Correct Answer: D

Correct Answer

Answer D is correct because This is correct because it applies the reserved architecture decision—separate tuning data from runtime grounding data—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘separate mcp integration from agent-to-agent delegation’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘normalize inconsistent units before grounding ingestion’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 9

During a design workshop on grounding pipelines and agent extensibility, the tool integration review identifies a constraint. The current solution leaves dependency isolation for a custom model outage unresolved, and the gap is now affecting the stated business or technical requirement. Which approach best fits the requirement?

Propagate deletions into a retrieval index.
Choose an endpoint abstraction that permits model replacement.
Choose computer use because a required legacy UI lacks an API is the decisive constraint.
Plan dependency isolation for a custom model outage.
Design a connector boundary around a reusable business capability.

Correct Answer: D

Correct Answer

Answer D is correct because This is correct because it applies the reserved architecture decision—plan dependency isolation for a custom model outage—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘propagate deletions into a retrieval index’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose an endpoint abstraction that permits model replacement’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer C is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose computer use when a required legacy ui lacks an api’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 10

The grounding pipeline program is preparing an architecture decision record for grounding pipelines and agent extensibility. The current solution leaves declarative extension with explicit knowledge and actions unresolved, and the gap is now affecting the stated business or technical requirement. Which action should the team take next?

Prefer a stable API when both integration paths meet requirements.
Preserve source citations across transformed documents and verify continuity after the change.
Handle a tool result that does not meet the expected contract.
Treat tuning data separately from runtime grounding data and evaluate each with its own evidence.
Design declarative extension with explicit knowledge and actions.

Correct Answer: E

Correct Answer

Answer E is correct because This is correct because it applies the reserved architecture decision—design declarative extension with explicit knowledge and actions—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘preserve source citations across transformed documents’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer C is incorrect because This is not the best choice because it addresses the adjacent decision ‘handle a tool result that does not meet the expected contract’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer D is incorrect because This is not the best choice because it addresses the adjacent decision ‘separate tuning data from runtime grounding data’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 11

During a design workshop on grounding pipelines and agent extensibility, the data platform group identifies a constraint. The current solution leaves a custom engine where orchestration control is mandatory unresolved, and the gap is now affecting the stated business or technical requirement. Which decision is most appropriate?

Plan dependency isolation for a custom model outage.
Choose a custom engine where orchestration control is mandatory.
Choose MCP because existing tools expose a compatible service is the decisive constraint.
Design refresh behavior for rapidly changing reference data.
Define a recovery boundary for an unexpected UI layout.

Correct Answer: B

Correct Answer

Answer B is correct because This is correct because it applies the reserved architecture decision—choose a custom engine where orchestration control is mandatory—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘plan dependency isolation for a custom model outage’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer C is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose mcp when existing tools expose a compatible service’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘define a recovery boundary for an unexpected ui layout’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 12

The agent extensibility team is preparing an architecture decision record for grounding pipelines and agent extensibility. The review has identified a specific issue: scope a Copilot extension to a supported user surface. Which action should the team take next?

Curate a minimal tool set for agent discoverability.
Scope a Copilot extension to a supported user surface.
Require confirmation before a UI automation submits a costly change.
Integrate a custom model behind a versioned contract.
Validate source permissions, grounding quality, tool contracts, and failure behavior with representative enterprise data.

Correct Answer: B

Correct Answer

Answer B is correct because This is correct because it applies the reserved architecture decision—scope a Copilot extension to a supported user surface—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘curate a minimal tool set for agent discoverability’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer D is incorrect because This is not the best choice because it addresses the adjacent decision ‘integrate a custom model behind a versioned contract’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is a useful verification step after the primary architecture decision, but it does not by itself resolve the decision the scenario asks for. The design choice must be made first, and this evidence can then confirm that the chosen approach behaves as intended.

Question 13

Before a wider rollout of grounding pipelines and agent extensibility, the data platform group reviews the current evidence. The review has identified a specific issue: integrate an existing agent without rebuilding its business logic. What is the best design choice?

Choose chunk boundaries that preserve business meaning.
Integrate an existing agent without rebuilding its business logic.
Resolve tool schema drift before exposing a changed server.
Choose a custom engine where orchestration control is mandatory.
Choose an endpoint abstraction that permits model replacement.

Correct Answer: B

Correct Answer

Answer B is correct because This is correct because it applies the reserved architecture decision—integrate an existing agent without rebuilding its business logic—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer D is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose a custom engine where orchestration control is mandatory’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose an endpoint abstraction that permits model replacement’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 14

Before a wider rollout of grounding pipelines and agent extensibility, the tool integration review reviews the current evidence. The current solution leaves a tool extension over duplicating business logic in a prompt unresolved, and the gap is now affecting the stated business or technical requirement. What should the architect recommend?

Treat MCP integration separately from agent-to-agent delegation and evaluate each with its own evidence.
Normalize inconsistent units before grounding ingestion.
Choose a tool extension over duplicating business logic in a prompt.
Treat tuning data separately from runtime grounding data and evaluate each with its own evidence.
Scope a Copilot extension to a supported user surface.

Correct Answer: C

Correct Answer

Answer C is correct because This is correct because it applies the reserved architecture decision—choose a tool extension over duplicating business logic in a prompt—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘separate mcp integration from agent-to-agent delegation’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘normalize inconsistent units before grounding ingestion’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘scope a copilot extension to a supported user surface’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 15

A production-readiness review of grounding pipelines and agent extensibility gives the tool integration review new evidence. The current solution leaves action parameters that make selection unambiguous unresolved, and the gap is now affecting the stated business or technical requirement. Which decision is most appropriate?

Integrate an existing agent without rebuilding its business logic.
Plan dependency isolation for a custom model outage.
Propagate deletions into a retrieval index.
Define action parameters that make selection unambiguous.
Choose computer use because a required legacy UI lacks an API is the decisive constraint.

Correct Answer: D

Correct Answer

Answer D is correct because This is correct because it applies the reserved architecture decision—define action parameters that make selection unambiguous—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘integrate an existing agent without rebuilding its business logic’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘plan dependency isolation for a custom model outage’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer C is incorrect because This is not the best choice because it addresses the adjacent decision ‘propagate deletions into a retrieval index’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose computer use when a required legacy ui lacks an api’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 16

The tool integration review is preparing an architecture decision record for grounding pipelines and agent extensibility. The current solution leaves a connector boundary around a reusable business capability unresolved, and the gap is now affecting the stated business or technical requirement. Which action should the team take next?

Prefer a stable API when both integration paths meet requirements.
Design declarative extension with explicit knowledge and actions.
Preserve source citations across transformed documents and verify continuity after the change.
Design a connector boundary around a reusable business capability.
Validate source permissions, grounding quality, tool contracts, and failure behavior with representative enterprise data.

Correct Answer: D

Correct Answer

Answer D is correct because This is correct because it applies the reserved architecture decision—design a connector boundary around a reusable business capability—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘design declarative extension with explicit knowledge and actions’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer C is incorrect because This is not the best choice because it addresses the adjacent decision ‘preserve source citations across transformed documents’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 17

During a design workshop on grounding pipelines and agent extensibility, the agent extensibility team identifies a constraint. The current solution leaves a tool result that does not meet the expected contract unresolved, and the gap is now affecting the stated business or technical requirement. Which approach best fits the requirement?

Design refresh behavior for rapidly changing reference data.
Choose a custom engine where orchestration control is mandatory.
Handle a tool result that does not meet the expected contract.
Define action parameters that make selection unambiguous.
Define a recovery boundary for an unexpected UI layout.

Correct Answer: C

Correct Answer

Answer C is correct because This is correct because it applies the reserved architecture decision—handle a tool result that does not meet the expected contract—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘design refresh behavior for rapidly changing reference data’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer D is incorrect because This is not the best choice because it addresses the adjacent decision ‘define action parameters that make selection unambiguous’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 18

An agent extensibility team is reviewing grounding pipelines and agent extensibility. The team has confirmed that existing tools expose a compatible service. It must now decide how to proceed. What should the architect recommend?

Design a connector boundary around a reusable business capability.
Require confirmation before a UI automation submits a costly change.
Scope a Copilot extension to a supported user surface.
Choose MCP when existing tools expose a compatible service.
Integrate a custom model behind a versioned contract.

Correct Answer: D

Correct Answer

Answer D is correct because This is correct because it applies the reserved architecture decision—choose MCP when existing tools expose a compatible service—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘design a connector boundary around a reusable business capability’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘require confirmation before a ui automation submits a costly change’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘integrate a custom model behind a versioned contract’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 19

A production-readiness review of grounding pipelines and agent extensibility gives the tool integration review new evidence. The review has identified a specific issue: curate a minimal tool set for agent discoverability. Which decision is most appropriate?

Choose an endpoint abstraction that permits model replacement.
Choose chunk boundaries that preserve business meaning.
Curate a minimal tool set for agent discoverability.
Handle a tool result that does not meet the expected contract.
Integrate an existing agent without rebuilding its business logic.

Correct Answer: C

Correct Answer

Answer C is correct because This is correct because it applies the reserved architecture decision—curate a minimal tool set for agent discoverability—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose an endpoint abstraction that permits model replacement’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose chunk boundaries that preserve business meaning’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘integrate an existing agent without rebuilding its business logic’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 20

Before a wider rollout of grounding pipelines and agent extensibility, the data platform group reviews the current evidence. The current solution leaves tool schema drift before exposing a changed server unresolved, and the gap is now affecting the stated business or technical requirement. Which approach best fits the requirement?

Normalize inconsistent units before grounding ingestion.
Do not broaden source or tool permissions merely to simplify integration; keep each extension at the least-privilege boundary.
Treat tuning data separately from runtime grounding data and evaluate each with its own evidence.
Resolve tool schema drift before exposing a changed server.
Validate source permissions, grounding quality, tool contracts, and failure behavior with representative enterprise data.

Correct Answer: D

Correct Answer

Answer D is correct because This is correct because it applies the reserved architecture decision—resolve tool schema drift before exposing a changed server—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘normalize inconsistent units before grounding ingestion’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer B is incorrect because This safeguard can be important in a broader production design, but it is a supporting control rather than the primary decision required by this scenario. Selecting it alone would leave the core architecture choice unresolved.

Answer C is incorrect because This is not the best choice because it addresses the adjacent decision ‘separate tuning data from runtime grounding data’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 21

Before a wider rollout of grounding pipelines and agent extensibility, the agent extensibility team reviews the current evidence. Stakeholders are treating mCP integration and agent-to-agent delegation as the same decision, which is obscuring the actual control boundary. What should the architect recommend?

Plan dependency isolation for a custom model outage.
Separate MCP integration from agent-to-agent delegation.
Define action parameters that make selection unambiguous.
Curate a minimal tool set for agent discoverability.
Propagate deletions into a retrieval index.

Correct Answer: B

Correct Answer

Answer B is correct because This is correct because it applies the reserved architecture decision—separate MCP integration from agent-to-agent delegation—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer C is incorrect because This is not the best choice because it addresses the adjacent decision ‘define action parameters that make selection unambiguous’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer D is incorrect because This is not the best choice because it addresses the adjacent decision ‘curate a minimal tool set for agent discoverability’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘propagate deletions into a retrieval index’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 22

The enterprise integration team is preparing an architecture decision record for grounding pipelines and agent extensibility. The team has confirmed that a required legacy UI lacks an API. It must now decide how to proceed. Which decision is most appropriate?

Design a connector boundary around a reusable business capability.
Design declarative extension with explicit knowledge and actions.
Resolve tool schema drift before exposing a changed server.
Choose computer use when a required legacy UI lacks an API.
Preserve source citations across transformed documents and verify continuity after the change.

Correct Answer: D

Correct Answer

Answer D is correct because This is correct because it applies the reserved architecture decision—choose computer use when a required legacy UI lacks an API—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘preserve source citations across transformed documents’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 23

During a design workshop on grounding pipelines and agent extensibility, the enterprise integration team identifies a constraint. The current solution leaves a stable API when both integration paths meet requirements unresolved, and the gap is now affecting the stated business or technical requirement. What should the architect recommend?

Handle a tool result that does not meet the expected contract.
Treat MCP integration separately from agent-to-agent delegation and evaluate each with its own evidence.
Prefer a stable API when both integration paths meet requirements.
Choose a custom engine where orchestration control is mandatory.
Design refresh behavior for rapidly changing reference data.

Correct Answer: C

Correct Answer

Answer C is correct because This is correct because it applies the reserved architecture decision—prefer a stable API when both integration paths meet requirements—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘handle a tool result that does not meet the expected contract’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘design refresh behavior for rapidly changing reference data’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Question 24

A pilot for grounding pipelines and agent extensibility reaches a decision point for the enterprise integration team. The current solution leaves a recovery boundary for an unexpected UI layout unresolved, and the gap is now affecting the stated business or technical requirement. Which approach best fits the requirement?

Choose MCP because existing tools expose a compatible service is the decisive constraint.
Validate source permissions, grounding quality, tool contracts, and failure behavior with representative enterprise data.
Define a recovery boundary for an unexpected UI layout.
Integrate a custom model behind a versioned contract.
Scope a Copilot extension to a supported user surface.

Correct Answer: C

Correct Answer

Answer C is correct because This is correct because it applies the reserved architecture decision—define a recovery boundary for an unexpected UI layout—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer A is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose mcp when existing tools expose a compatible service’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer B is incorrect because This is a useful verification step after the primary architecture decision, but it does not by itself resolve the decision the scenario asks for. The design choice must be made first, and this evidence can then confirm that the chosen approach behaves as intended.

Question 25

An agent extensibility team is reviewing grounding pipelines and agent extensibility. The current solution leaves confirmation before a UI automation submits a costly change unresolved, and the gap is now affecting the stated business or technical requirement. Which action should the team take next?

Require confirmation before a UI automation submits a costly change.
Curate a minimal tool set for agent discoverability.
Integrate an existing agent without rebuilding its business logic.
Choose an endpoint abstraction that permits model replacement.
Prefer a stable API when both integration paths meet requirements.

Correct Answer: A

Correct Answer

Answer A is correct because This is correct because it applies the reserved architecture decision—require confirmation before a UI automation submits a costly change—to the decisive constraint in the scenario. It keeps the action at the appropriate grounding pipelines and agent extensibility boundary and produces a result that can be verified before wider deployment.

Incorrect Answers

Answer B is incorrect because This is not the best choice because it addresses the adjacent decision ‘curate a minimal tool set for agent discoverability’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer C is incorrect because This is not the best choice because it addresses the adjacent decision ‘integrate an existing agent without rebuilding its business logic’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer D is incorrect because This is not the best choice because it addresses the adjacent decision ‘choose an endpoint abstraction that permits model replacement’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Answer E is incorrect because This is not the best choice because it addresses the adjacent decision ‘prefer a stable api when both integration paths meet requirements’ rather than the scenario’s decisive requirement. Although that action can be valid within grounding pipelines and agent extensibility, selecting it here would leave the stated constraint unresolved or move the design to the wrong stage.

Related posts: