Skip to content

Choosing among Agent Bricks (Knowledge Assistant, Multi-agent Supervisor, Information Extraction) for a problem

Agent Bricks provides pre-built, auto-optimized agent templates—Knowledge Assistant, Multi-Agent Supervisor, and Information Extraction—so engineers can assemble production-quality GenAI apps without hand-tuning prompts or writing custom evaluation harnesses. Choosing the right Agent Bricks type depends on whether the task is grounded Q&A, orchestration across multiple specialized agents, or structured data extraction from unstructured content.

1 · Learn the must-know

  • Agent Bricks auto-optimizes each agent's quality, cost, and latency using built-in LLM-judge evaluation against a task description and optional labeled examples, minimizing manual prompt engineering.
  • Knowledge Assistant is designed for RAG-style question answering grounded in a curated unstructured corpus (e.g., documents in Unity Catalog volumes) and automatically handles chunking, retrieval, and grounding.
  • Information Extraction is the right choice when the goal is converting unstructured text or documents into structured fields/JSON output at scale, not for open-ended conversation.
  • Multi-Agent Supervisor is used when a single agent can't cover the needed scope—it routes requests and orchestrates multiple specialized agents, tools, or Genie spaces to answer complex, multi-domain queries.
  • Pick Agent Bricks over a fully custom agent build when you want a managed, evaluation-driven path to production; drop to the custom Mosaic AI Agent Framework when requirements exceed what a template supports.
  • All Agent Bricks agents are deployed via Model Serving, governed through Unity Catalog, and integrate with MLflow for tracing and ongoing evaluation.

2 · Check your understanding

Check this objectiveFree · always available

An engineer initially built a Knowledge Assistant over legal contract documents for Q&A, but stakeholders now also want the system to extract key contract terms such as party names, effective dates, and renewal clauses into a structured Delta table for quarterly reporting. The engineer must add this capability without duplicating the existing document ingestion pipeline. Which approach should the engineer take to meet both requirements with minimal custom code?

Your objective map0 tried · 0 answered correctly · 56 untouched

What you have tried across Databricks GenAI Engineer's objectives, not a readiness score.

Design Applications10.71% of the exam*0 of 6 tried
Data Preparation14.29% of the exam*0 of 8 tried
Application Development23.21% of the exam*0 of 13 tried
Assembling and Deploying Applications26.79% of the exam*0 of 15 tried
Governance7.14% of the exam*0 of 4 tried
Evaluation and Monitoring17.86% of the exam*0 of 10 tried

* Our estimate. Databricks publishes no section weights.

3 · Keep going