dbt_project.yml configuration - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the project name in dbt_project.yml.

dbt

name: [1]

Drag options to blanks, or click blank then click option'

Aversion

Bprofile

Cmy_dbt_project

Dmodels

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'version' or 'models' instead of the project name.

Leaving the name blank.

The name key in dbt_project.yml sets the project name.

2fill in blank

medium

Complete the code to specify the version of the dbt project.

dbt

version: [1]

Drag options to blanks, or click blank then click option'

A1.0

B'1.0'

Cone

Dv1

Attempts:

3 left

💡 Hint

Common Mistakes

Not using quotes around the version number.

Using words instead of numbers.

The version should be a string, so it needs quotes.

3fill in blank

hard

Fix the error in the code to correctly define the profile name.

dbt

profile: [1]

Drag options to blanks, or click blank then click option'

Aprofile

Bdefault_profile

Cprofile_name

D'default_profile'

Attempts:

3 left

💡 Hint

Common Mistakes

Leaving the profile name unquoted.

Using an incorrect profile name.

The profile name must be a string, so it needs quotes.

4fill in blank

hard

Fill both blanks to define the models directory and the materialization strategy.

dbt

models:
  [1]:
    [2]: table

Drag options to blanks, or click blank then click option'

Amy_dbt_project

Bmaterialized

Cdefault

Dschema

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'schema' instead of 'materialized'.

Using 'default' instead of the project name.

The first blank is the project name under models. The second blank is the key for materialization strategy.

5fill in blank

hard

Fill all three blanks to configure the seeds directory, file format, and quoting.

dbt

seeds:
  [1]:
    [2]: csv
    [3]:
      identifier: true

Drag options to blanks, or click blank then click option'

Amy_dbt_project

Bfile_format

Cquote_columns

Dquoting

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up quote_columns and quoting.

Using wrong keys for file format.

The first blank is the project name under seeds. The second blank sets the file format. The third blank sets quoting options for identifiers.

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