| 1.1 Design a prompt that elicits a specifically formatted response | When code reads the model's answer, you must make the answer arrive in a set shape, such as JSON with named fields. You do this either by setting a request option that enforces the shape, or, if you can only edit the prompt, by showing the exact format and the allowed values. | A support tool parses the model reply into a ticket record and breaks whenever a field is renamed. The team controls the request sent to a Foundation Model API chat endpoint. | Send the schema in the response_format request field with type json_schema and strict set, because the platform then holds the model to your field names and types. Use json_object only when the structure is not known in advance, since it promises valid JSON and nothing more. Keep the schema flat; the documented limit is 64 keys, and pattern, anyOf, oneOf and $ref are not supported. Try it: Call a pay-per-token chat endpoint twice, once with a plain instruction and once with a json_schema response format, and compare the replies. | Writing 'reply in JSON' in the system prompt looks fine but only asks politely, so fields still drift. json_object is also tempting, but it does not enforce your fields. Runner-up wins when: A prompt with a filled example and the allowed labels wins when the stem says you cannot change request fields, for example a UI where only the prompt text is editable. |
| 1.2 Select model tasks to accomplish a given business requirement | Name the language task first (classify, extract, summarize, translate, generate), then pick the tool built for that task. Databricks offers ready-made AI Functions you call from SQL for the common tasks. | A retailer wants each incoming email put into one of five fixed queues, directly from a SQL table of emails, with no prompt writing. | A fixed label set is classification, and the matching function is ai_classify. Pulling named fields is extraction (ai_extract), a shorter version of the same text is summarization (ai_summarize). Use the general ai_query only when no task-specific function fits and you need your own prompt or model. AI Functions do not run on Classic SQL warehouses. Try it: Run ai_classify on three short sentences in a SQL notebook with a list of two labels. | Choosing ai_query with a hand-written prompt works but adds prompt and model decisions the stem did not ask for. Another slip is calling invoice-total extraction 'classification'. Runner-up wins when: ai_query wins when the stem needs a custom prompt, a specific served model, or output the task-specific functions cannot produce. |
| 1.3 Select chain components for a desired model input and output | Before choosing any model, write down exactly what the system receives, what it must hand back, in what shape, how fast, and how often. That description is the spec every later choice is checked against. | A bank asks for an assistant that helps relationship managers. The question asks which description of the pipeline is the most useful starting point. | The best description names the real inputs (fields, documents, user text), the exact output a person or system consumes (fields, allowed values, length) and constraints such as latency and whether work is batch or per request. Batch versus real time already separates an ai_query job from a serving endpoint. If an input does not exist in any data source, prompting cannot create it; you need a source or a tool. | An option that names a model or vendor but no inputs and outputs is a technology choice, not a description. A vague output such as 'a helpful answer' loses to explicit fields. |
| 1.4 Translate business use case goals into a description of the desired inputs and outputs for the AI pipeline | A chain is a fixed sequence of parts: a prompt template, optionally a retriever that fetches documents, the language model, and an output parser. You add a part only when the input or output needs it. | Answers must come from the company's private policy documents and must cite which document was used. The flow is the same on every request. | Add a retriever over a search index for the private documents, pass the chunk text and its source id into the prompt template, and let the model answer. The flow never changes between requests, so a chain is the right shape. Add an output parser or structured outputs if code consumes the result. | Fine-tuning the model on the policies looks like a way to teach it facts, but it cannot cite sources and goes stale when a policy changes. Runner-up wins when: A single prompt template plus the model wins when the behaviour is static and needs no private data. |
| 1.5 Define and order tools that gather knowledge or take actions for multi-stage reasoning | A tool is a function the model can call to get knowledge or take an action. For work that needs several steps, you define the tools and decide the order in which they must run, because a later step often needs the result of an earlier one. | A request to refund an order needs the order looked up, the refund policy checked, and only then the refund issued. | Order the tools by dependency: look up the order, retrieve the policy, then run the refund action. Tools that read data come before tools that change it, so a wrong refund is not issued on missing facts. Each tool needs a clear name, description and input schema so the model picks it correctly. Unity Catalog functions and retriever tools are the usual ways to register them. | Putting the action tool first, or giving the model one big tool that does everything, hides the order and makes errors hard to trace. Runner-up wins when: A fixed chain wins when the steps never vary; the model choosing tools only earns its cost when the path depends on the request. |
| 1.6 Determine how and when to use Agent Bricks (Knowledge Assistant, Multiagent Supervisor, Information Extraction) to solve problems | Agent Bricks is the Databricks service for building agents with little code. The Knowledge Assistant answers questions from your documents with citations, the Multiagent Supervisor coordinates several agents or Genie spaces, and Information Extraction turns text into structured fields. | A team wants a chat assistant over a folder of manuals, with sources shown, built without writing a retrieval pipeline. | That is the Knowledge Assistant: point it at the documents and it builds the retrieval and answers with citations. Choose Information Extraction when the output is structured fields from text. Choose the Multiagent Supervisor when one request must be routed across several specialist agents or Genie spaces. | Choosing the Multiagent Supervisor because it sounds the most powerful. With one document source and no routing need, it adds a layer nothing asked for. Runner-up wins when: A hand-built chain wins when you need custom retrieval logic or code-level control that the managed builders do not expose. |