An organization intends to deploy an AI-driven conversational agent to support its sales department. This agent must address diverse user inquiries falling into three main types: (1) analytical queries (e.g., 'What was the number of deals finalized in EMEA last quarter?') by interacting with Delta Lake sales data, (2) informational requests (e.g., 'Could you outline our official pricing strategy for enterprise-level agreements?') by searching internal policy documentation, and (3) complex task directives (e.g., 'Provide a summary of the top three competitive threats identified in the latest market study.'). Crucially, a single user input might involve any combination of these functions. The goal is a seamless, single point of interaction for users, requiring minimal bespoke development. Considering these requirements, which Agent Bricks configuration offers the optimal solution?
Answer & explanation
Correct answer: A
WHY A is correct: The Supervisor Agent (Multiagent Supervisor) is the Databricks Agent Brick designed to 'bring Genie spaces and agents together' under a unified coordinator. When a use case spans multiple distinct capabilities — structured data querying (Genie), document search (Knowledge Assistant), and custom agents — a Supervisor coordinates the specialists and presents a single conversational interface to the user. The Supervisor analyzes each user message, determines which agent(s) can fulfill it, routes sub-tasks appropriately, and merges the results into a coherent response. This is the purpose of the Multiagent Supervisor pattern.
WHY NOT C: Providing three separate chatbot URLs to the sales team creates a poor user experience — salespeople must decide which tool to use before asking their question, and multi-part questions that require capabilities from two or three assistants cannot be handled at all without manually copying answers between tools. A unified interface is explicitly required.
WHY NOT B: AI/BI Genie is designed specifically for structured tabular data (SQL generation). It does not search unstructured documents or summarize PDF market research reports. Claiming Genie handles all three modalities from a single interface misrepresents Genie's designed scope.
WHY NOT D: Information Extraction pre-processes documents into structured tables. This works for extracting specific fields (prices, names, dates) but cannot answer open-ended data questions with unknown aggregation logic, cannot answer free-form policy questions requiring semantic understanding, and cannot summarize competitive analysis narratives. Pre-extracting all possible information from live dynamic sales tables and varied documents into one master table is both technically infeasible and semantically reductive.
WHY NOT E: Exporting live Delta Lake sales data to PDFs and indexing those PDFs in a Knowledge Assistant is a severe anti-pattern. The sales data becomes stale immediately, PDF exports of tabular data create enormous documents, and vector similarity search over tabular data is far less precise than SQL execution. Knowledge Assistant is not designed to reason over numerical tabular data — AI/BI Genie uses SQL for that purpose.