Bird
0
0

Why is it recommended to have one dbt model per source table when building data pipelines?

easy📝 Conceptual Q2 of 15
dbt - Project Organization
Why is it recommended to have one dbt model per source table when building data pipelines?
ATo reduce the number of SQL queries executed.
BTo simplify debugging and improve model reusability.
CTo avoid using source tables directly in transformations.
DTo combine all data into a single large table.
Step-by-Step Solution
Solution:

  1. Step 1: Identify benefits of one model per source table

    This approach makes it easier to find and fix errors and reuse models in other transformations.

  2. Step 2: Match benefits to options

    To simplify debugging and improve model reusability. correctly states simplification of debugging and reusability, unlike other options.

  3. Final Answer:

    To simplify debugging and improve model reusability. -> Option B

  4. Quick Check:

    One model per source table = easier debugging and reuse [OK]
Quick Trick: One model per table helps debug and reuse code [OK]
Common Mistakes:
MISTAKES
  • Thinking it reduces SQL queries
  • Believing source tables shouldn't be used directly
  • Assuming all data should be combined early

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More dbt Quizzes
Advanced Testing - dbt-utils package tests - Quiz 4medium Incremental Models - Unique key for merge behavior - Quiz 10hard Jinja in dbt - Built-in Jinja context variables - Quiz 11easy Jinja in dbt - For loops for dynamic SQL - Quiz 9hard Jinja in dbt - Variables and control flow - Quiz 2easy Packages and Reusability - Version pinning and updates - Quiz 12easy Packages and Reusability - Why packages accelerate dbt development - Quiz 15hard Project Organization - Staging, intermediate, and marts pattern - Quiz 6medium Project Organization - Naming conventions at scale - Quiz 10hard Project Organization - Why project structure scales with team size - Quiz 12easy