Question 180
A production Snowflake Gen AI workflow must handle the following: A sales agent combines multiple tools whose identifiers may collide across accounts. What is the strongest technically defensible design decision?
Explanation
Correct Answer
“Validate each tool response against expected schema and access scope before letting an agent synthesize a final user answer” is supported by this requirement: A sales agent combines multiple tools whose identifiers may collide across accounts. 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
“Treat an HTTP success status as proof the tool data answers the user question” would not meet the requirement that a sales agent combines multiple tools whose identifiers may collide across accounts. 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.
“Merge results from different tenants when tool output identifiers happen to match” would not meet the requirement that a sales agent combines multiple tools whose identifiers may collide across accounts. 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.
“Allow an unexpected JSON field to be treated as an executable agent instruction” would not meet the requirement that a sales agent combines multiple tools whose identifiers may collide across accounts. 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.