Courseiva

Databricks-DA-Assoc Executing Queries with Databricks SQL Practice Question

A data analyst has a Databricks SQL query that joins a large fact table to a small dimension table. The query is slow because the dimension table is being shuffled across the cluster. The analyst wants to avoid this shuffle and improve performance. Which SQL hint should they use?

⚠ Common exam trap

Many exam-takers confuse join strategy hints with other SQL operations like MERGE or REPARTITION, which do not address broadcast joins.

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

✓

BROADCAST

The BROADCAST hint tells the optimizer to send the smaller table to all worker nodes, allowing the join to occur locally without shuffling the larger table. This reduces network overhead and speeds up the query. The other options are either not hints or would increase shuffling.

Answer analysis

Option-by-option breakdown

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

  • ✗

    REPARTITION

    Why it's wrong here

    REPARTITION is a hint that repartitions the data by a specified number of partitions or columns, which can introduce additional shuffling. It is used to control partitioning, not to broadcast a small table. It would not eliminate the shuffle of the dimension table.

  • ✗

    SHUFFLEMERGE

    Why it's wrong here

    SHUFFLEMERGE is a join strategy hint that forces a shuffle merge join, which would actually increase shuffling rather than avoid it. It is not appropriate when you want to eliminate shuffle for a small table. Using it would likely worsen performance in this scenario.

  • ✓

    BROADCAST

    Why this is correct

    BROADCAST is a Databricks SQL hint that instructs the optimizer to broadcast the smaller table to all nodes, eliminating the shuffle of the larger table. In this scenario, the dimension table is small, so broadcasting it avoids the expensive shuffle and speeds up the join. This is the correct hint to use.

  • ✗

    MERGE

    Why it's wrong here

    MERGE is a SQL statement for performing upserts, not a join hint. It is used to conditionally insert, update, or delete rows in a target table based on a source table. It does not control join strategies or prevent shuffles, so it would not help here.

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 →

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.