Organizing models in directories in dbt - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding model directory structure in dbt

In dbt, how does organizing models into subdirectories affect the resulting database schema and table names?

A Models in subdirectories are flattened into the same schema as the root models folder, ignoring folder names.

B Each subdirectory creates a separate database, isolating models completely.

C Subdirectories in the models folder create nested schemas in the database, reflecting the folder structure.

D Models in subdirectories are ignored unless explicitly referenced in the dbt_project.yml file.

💡 Hint

Think about how dbt treats folder names by default when building models.

By default, dbt compiles models into the target schema without creating nested schemas for subdirectories. The folder structure helps organize code but does not affect the database schema names.

❓ Predict Output

intermediate

Output schema and table name from nested model

Given the following dbt model file path and configuration, what will be the schema and table name of the compiled model?

models/sales/2024/orders.sql

dbt_project.yml contains:

models:
  sales:
    +schema: sales_data

dbt

select * from raw.orders

A Schema: public, Table: orders

B Schema: sales, Table: orders

C Schema: sales_data, Table: orders

D Schema: sales_data, Table: sales_2024_orders

💡 Hint

Check how the +schema config applies to subdirectories.

The +schema config under 'sales' applies to all models in the sales folder and its subfolders. The table name is the model file name without folder prefixes.

❓ data_output

advanced

Resulting model names from multiple directories

Consider a dbt project with these model files:

• models/customers.sql
• models/finance/invoices.sql
• models/finance/2024/payments.sql

With no special schema or alias configurations, what are the compiled table names for these models?

A customers, finance_invoices, finance_2024_payments

B customers, invoices, payments

C customers, invoices, finance_2024_payments

D customers, finance_invoices, payments

💡 Hint

Think about how dbt names tables by default from file names.

By default, dbt uses the model file name as the table name, ignoring folder names. So all tables are named after their file names only.

🔧 Debug

advanced

Why is a model not found after moving to a subdirectory?

A model 'sales_summary.sql' was moved from models/ to models/sales/. After running dbt, a downstream model referencing it fails with 'model not found'. What is the most likely cause?

A The model was not added to the manifest because subdirectories are ignored by dbt.

B dbt requires updating the dbt_project.yml to include new subdirectories explicitly.

C The model file name must be changed to include the subdirectory name.

D The downstream model's ref() call did not update to include the subdirectory path.

💡 Hint

Check how dbt's ref() function resolves model names.

dbt's ref() function uses the model name, which is the file name without folder prefixes. Moving a model to a subdirectory does not change its ref() name, so the downstream model's ref() call should remain the same.

🚀 Application

expert

Configuring dbt to create schemas matching model directories

You want dbt to create separate schemas in the database that match your model directory names (e.g., models/sales/ creates schema 'sales'). Which configuration achieves this behavior?

A Use the <code>+schema</code> config with a Jinja expression referencing <code>this.path</code> and the model path.

B Set <code>generate_schema_name</code> in dbt_project.yml to use the directory name dynamically.

C Set <code>materialized: ephemeral</code> on all models in subdirectories.

D Rename all model files to include the directory name as a prefix.

💡 Hint

Look into how to use Jinja in model configs to customize schema names.

Using the +schema config with a Jinja expression that extracts the directory name from this.path allows dbt to create schemas matching directories dynamically.