Courseiva

Databricks-DA-Assoc Developing AI/BI Genie Spaces Practice Question

Which of the following is the best strategy for refining Genie space performance when the model consistently struggles with complex joins?

⚠ Common exam trap

Candidates often try to solve join issues by rewriting the user's natural language question rather than addressing the root cause: the lack of explicit metadata regarding table relationships.

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

✓

Add primary/foreign key definitions and clarify join logic in instructions

When a Genie space fails on multi-table joins, the underlying issue is often a lack of clear relationship definitions. By updating the table metadata in Unity Catalog (such as primary and foreign key constraints) and using the Genie instructions to explicitly define how tables should be joined, the developer provides the model with the necessary 'map' to build complex queries accurately.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Flatten all tables into a single wide table

    Why it's wrong here

    Flattening tables is a reactive measure that can lead to data duplication and massive storage overhead. While it simplifies joining, it defeats the purpose of a normalized data warehouse. It is better to guide the AI with clear instructions and metadata than to compromise the data model.

  • ✗

    Increase the number of allowed tables

    Why it's wrong here

    Increasing the number of tables actually increases the complexity for the LLM. If the model is already struggling with joins, adding more tables will likely introduce more ambiguity and confusion, causing further degradation in query generation performance rather than solving the existing join logic issues.

  • ✓

    Add primary/foreign key definitions and clarify join logic in instructions

    Why this is correct

    Defining relationships in Unity Catalog and providing explicit join guidance in the instructions is the industry-standard way to assist LLMs. This provides the 'source of truth' that the AI needs to navigate the relationships between tables, ensuring it can perform complex joins reliably and consistently.

  • ✗

    Switch to a larger, more expensive SQL Warehouse

    Why it's wrong here

    Hardware resources do not influence the intelligence or reasoning capabilities of the underlying LLM. If the model does not understand the relationship between tables, no amount of compute power will fix the logic. The solution must be addressed at the semantic layer (instructions/metadata).

About these practice questions

This Databricks-DA-Assoc question is part of Courseiva's 291-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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.