Question 440
A Cortex implementation engineer receives the following request: A policy agent gets a plausible response from an unauthorized dataset and must preserve access boundaries. Which observation most directly tests whether the proposed solution worked?
Explanation
Correct Answer
“Correct tool-to-task mapping, schema validation, blocked cross-scope results and accurate final synthesis” is supported by this requirement: A policy agent gets a plausible response from an unauthorized dataset and must preserve access boundaries. Agents need explicit contracts and checked evidence at tool boundaries, not just successful tool calls. Verify it using correct tool-to-task mapping, schema validation, blocked cross-scope results and accurate final synthesis.
Incorrect Answers
“Total cross-tenant records combined in one response” would not meet the requirement that a policy agent gets a plausible response from an unauthorized dataset and must preserve access boundaries. Agents need explicit contracts and checked evidence at tool boundaries, not just successful tool calls. The more reliable approach is to validate each tool response against expected schema and access scope before letting an agent synthesize a final user answer.
“HTTP 200 frequency regardless of semantic correctness” would not meet the requirement that a policy agent gets a plausible response from an unauthorized dataset and must preserve access boundaries. Agents need explicit contracts and checked evidence at tool boundaries, not just successful tool calls. The more reliable approach is to validate each tool response against expected schema and access scope before letting an agent synthesize a final user answer.
“Tool execution count without answer verification” would not meet the requirement that a policy agent gets a plausible response from an unauthorized dataset and must preserve access boundaries. Agents need explicit contracts and checked evidence at tool boundaries, not just successful tool calls. The more reliable approach is to validate each tool response against expected schema and access scope before letting an agent synthesize a final user answer.