Databricks-DA-Assoc Developing AI/BI Genie Spaces Practice Question
A Data Analyst is configuring an AI/BI Genie Space to allow business users to query sales data. The analyst needs to ensure the model understands specific business logic, such as how to calculate 'Net Revenue' from raw columns. Where should the analyst define this logic to ensure Genie consistently applies these business rules across all user queries?
⚠ Common exam trap
Candidates often mistakenly believe business logic should be hardcoded directly into the Genie user interface prompt rather than structured within Unity Catalog metadata or table comments.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Define the logic in the SQL view metadata or table comments within Unity Catalog.
Defining business logic in the underlying Databricks SQL Warehouse or Unity Catalog perspective is the most reliable way to guide Genie. By providing clear descriptions and semantic definitions within the catalog or view metadata, the LLM-driven engine can correctly interpret business terminology. This ensures that non-technical users receive consistent, accurate results without needing to write complex SQL, directly impacting the trust and adoption of the AI/BI solution within the organization.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add the logic as a comment in the user's prompt history.
Why it's wrong here
Prompt history is transient and specific to individual sessions, making it unsuitable for enforcing organizational business logic. Relying on user prompts leads to inconsistencies, as different users may phrase their requests differently, causing the Genie to interpret the same business metric in conflicting ways across various analyst sessions.
- ✗
Hardcode the business logic into the Genie Space configuration UI.
Why it's wrong here
Genie configuration settings prioritize data access and model selection rather than arbitrary code injection. Hardcoding logic in the interface limits maintainability and scalability, as any changes to the underlying business definitions would require manual updates to the UI, which is not a standard architectural pattern for Databricks AI/BI.
- ✓
Define the logic in the SQL view metadata or table comments within Unity Catalog.
Why this is correct
AI/BI Genie leverages metadata defined in Unity Catalog to understand data semantics. By properly commenting tables and views with detailed business descriptions, you provide the context needed for the model to generate accurate SQL. This approach ensures consistent interpretation of metrics across all users accessing the Genie Space.
- ✗
Require users to provide the formula in every natural language query.
Why it's wrong here
Requiring users to define formulas manually defeats the purpose of an AI-driven interface. It introduces high cognitive load and increases the likelihood of human error, leading to inaccurate reporting. An effective Genie implementation abstracts complexity away from the user, allowing them to focus on business outcomes, not syntax.
About these practice questions
Courseiva writes every Databricks-DA-Assoc question from scratch — 291 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DA-Assoc practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DA-Assoc exam.