dbt_project.yml configuration - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the dbt_project.yml file?

It is the main configuration file for a dbt project. It tells dbt how to build models, where to find files, and sets project-level settings.

beginner

Name two key sections you can find in dbt_project.yml.

Common sections include name (the project name) and models (settings for model folders and configurations).

intermediate

How do you specify the folder where your models live in dbt_project.yml?

Inside the models section, you set the path relative to the project root, for example: models: my_project: +materialized: view.

intermediate

What does the materialized config in dbt_project.yml control?

It controls how dbt builds models in the database, such as creating tables, views, or incremental models.

beginner

True or False: You can override model configurations for specific subfolders in dbt_project.yml.

True. You can set different configurations for subfolders by nesting them under the models section.

What is the main role of dbt_project.yml?

A Configure how dbt runs and builds models

B Store raw data files

C Write SQL queries

D Manage database users

dbt_project.yml tells dbt how to build your project and models.

Where do you define the materialization type for models in dbt_project.yml?

A Under the <code>models</code> section

B In the <code>seeds</code> section

C In the <code>snapshots</code> section

D In the <code>profiles.yml</code> file

Materialization is set inside the models section to control how models are built.

Can you set different configurations for different model folders in dbt_project.yml?

A Only by editing SQL files

B No, all models share the same config

C Yes, by nesting folder names under <code>models</code>

D Only in the database

You can customize configs per folder by nesting them under models.

Which of these is NOT a valid materialization type in dbt?

A table

B view

C incremental

D function

Valid materializations include table, view, and incremental. function is not valid.

What file do you edit to change project-level settings like the project name?

A schema.yml

B dbt_project.yml

C packages.yml

D profiles.yml

The project name and settings are in dbt_project.yml.

Explain the role of the dbt_project.yml file in a dbt project.

Think about what dbt needs to know to build your project.

Describe how you would configure different materializations for models in separate folders using dbt_project.yml.

Look at how nesting works in YAML for folder-specific settings.

Practice

1. What is the primary purpose of the dbt_project.yml file in a dbt project?

easy

A. To configure project settings like name, version, and model paths

B. To write SQL queries for data transformation

C. To store raw data files for analysis

D. To define user access permissions for the project

Solution

1. Step 1: Understand the role of dbt_project.yml

   This file tells dbt how to run the project by setting configurations.

2. Step 2: Identify what configurations it includes

   It sets project name, version, file paths, and model build settings, not SQL or data files.

3. Final Answer:

   To configure project settings like name, version, and model paths -> Option A

4. Quick Check:

   Project configuration = To configure project settings like name, version, and model paths [OK]

Hint: Remember: dbt_project.yml sets project-wide settings [OK]

Common Mistakes:

• Confusing dbt_project.yml with SQL model files
• Thinking it stores data instead of configurations
• Assuming it manages user permissions

2. Which of the following is the correct YAML syntax to set the project name to "my_dbt_project" in dbt_project.yml?

easy

A. project_name: my_dbt_project

B. project: "my_dbt_project"

C. project-name: my_dbt_project

D. name: my_dbt_project

Solution

1. Step 1: Recall the correct key for project name in dbt_project.yml

   The key to set the project name is name, not project_name or others.

2. Step 2: Check YAML syntax

   YAML uses key: value pairs, so name: my_dbt_project is correct syntax.

3. Final Answer:

   name: my_dbt_project -> Option D

4. Quick Check:

   Project name key = name [OK]

Hint: Use name: to set project name in YAML [OK]

Common Mistakes:

• Using underscores or hyphens incorrectly in key names
• Putting project name under wrong key
• Using quotes unnecessarily or missing them when needed

3. Given this snippet in dbt_project.yml:

models:
  my_project:
    materialized: table
    schema: analytics

What will be the materialization type and schema for models in the my_project namespace?

medium

A. Materialized as views, schema is default

B. Materialized as tables, schema is analytics

C. Materialized as incremental, schema is analytics

D. Materialized as tables, schema is default

Solution

1. Step 1: Read the materialized setting under models.my_project

   The setting materialized: table means models will be built as tables.

2. Step 2: Check the schema setting

   The schema is explicitly set to analytics, so models will be created in that schema.

3. Final Answer:

   Materialized as tables, schema is analytics -> Option B

4. Quick Check:

   Materialized = table, schema = analytics [OK]

Hint: Look for materialized and schema keys under models [OK]

Common Mistakes:

• Assuming default schema when schema is set
• Confusing materialized types like view vs table
• Ignoring indentation that defines scope

4. Identify the error in this dbt_project.yml snippet:

name: my_project
version: 1.0
models:
  my_project:
    materialized: table
    schema analytics

medium

A. Version should be a string, not a number

B. Incorrect indentation for 'models' key

C. Missing colon after 'schema' key

D. Project name should be under 'project' key

Solution

1. Step 1: Check YAML syntax for key-value pairs

   Each key must be followed by a colon and a space before the value. Here, schema analytics misses the colon.

2. Step 2: Verify other parts

   Indentation and version format are correct; project name uses correct key name.

3. Final Answer:

   Missing colon after 'schema' key -> Option C

4. Quick Check:

   YAML key-value needs colon [OK]

Hint: Check every key has a colon and space before value [OK]

Common Mistakes:

• Forgetting colon after keys
• Wrong indentation levels
• Using wrong keys for project name

5. You want to configure your dbt project so that all models in the sales folder are materialized as incremental and use the schema sales_data. Which dbt_project.yml snippet correctly achieves this?

hard

A. models:
sales:
+materialized: incremental
+schema: sales_data

B. models:
sales:
materialized: incremental
schema: sales_data

C. models:
sales:
materialized: incremental
+schema: sales_data

D. models:
sales:
+materialized: incremental
schema: sales_data

Solution

1. Step 1: Understand dbt config syntax for folder-level overrides

   To set configs for all models in a folder, use the '+' prefix before keys.

2. Step 2: Check which options use '+' for both keys

   Both materialized and schema need '+' prefix to apply to all models in sales folder.

3. Final Answer:

   models: sales: +materialized: incremental +schema: sales_data -> Option A

4. Quick Check:

   Folder configs use '+' prefix [OK]

Hint: Use '+' before keys to apply configs to all models in a folder [OK]

Common Mistakes:

• Missing '+' prefix for folder-level configs
• Using '+' on only one key instead of both
• Confusing folder name with project name