Creating your own dbt package - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the package name in the dbt project file.

dbt

name: [1]

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

Adbt_project

Bproject

Cpackage_name

Dmy_dbt_package

Attempts:

3 left

💡 Hint

Common Mistakes

Using reserved words like 'project' or 'package_name' as the package name.

Leaving the name field empty.

The 'name' field in the dbt_project.yml file specifies the package name. Here, 'my_dbt_package' is a valid package name.

2fill in blank

medium

Complete the code to add a model file in your dbt package.

dbt

models/[1].sql

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

Apackage

Bdbt_model

Cmy_model

Dmodel_file

Attempts:

3 left

💡 Hint

Common Mistakes

Using spaces in file names.

Placing model files outside the models directory.

Model files in dbt are SQL files placed inside the models directory. 'my_model.sql' is a valid model file name.

3fill in blank

hard

Fix the error in the dbt package dependency declaration.

dbt

packages:
  - package: [1]
    version: 0.1.0

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

Adbt-labs/dbt utils

Bdbt-labs/dbt-utils

Cdbt-labs/dbt_utils

Ddbt_utils

Attempts:

3 left

💡 Hint

Common Mistakes

Using spaces instead of slashes.

Mixing dashes and underscores incorrectly.

The correct package format is 'namespace/package_name' with a slash and no spaces. 'dbt-labs/dbt-utils' is correct.

4fill in blank

hard

Fill both blanks to create a simple model SQL that selects all from a source table.

dbt

select * from [1].[2]

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

Araw

Bstaging

Ccustomers

Dorders

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping schema and table names.

Using non-existent schema or table names.

In dbt, 'raw.customers' refers to the 'customers' table in the 'raw' schema, a common pattern for source data.

5fill in blank

hard

Fill all three blanks to define a dbt model with a config block and a select statement.

dbt

[1](
    materialized='[2]'
)

select * from [3]

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

Aconfig

Btable

Craw.customers

Dmodel

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'model' instead of 'config' for the first blank.

Using invalid materialization types.

Incorrect table references.

The 'config' function sets model properties like materialization. 'table' is a materialization type. The select statement reads from 'raw.customers'.

Practice

1. What is the main purpose of creating your own dbt package?

easy

A. To reuse and share data models easily across projects

B. To write SQL queries faster

C. To create dashboards automatically

D. To store raw data files

Solution

1. Step 1: Understand the role of dbt packages

   dbt packages are designed to bundle data models and logic for reuse.

2. Step 2: Identify the main benefit

   Sharing and reusing models saves time and keeps projects consistent.

3. Final Answer:

   To reuse and share data models easily across projects -> Option A

4. Quick Check:

   dbt package purpose = reuse/share models [OK]

Hint: Think: Why share code? To reuse it easily [OK]

Common Mistakes:

• Confusing packages with dashboards
• Thinking packages store raw data
• Believing packages speed up SQL writing only

2. Which file do you edit to add a new dbt package to your main project?

easy

A. models.sql

B. dbt_project.yml

C. profiles.yml

D. packages.yml

Solution

1. Step 1: Recall where packages are declared

   dbt uses packages.yml to list external or local packages.

2. Step 2: Differentiate from other config files

   dbt_project.yml configures the project itself, not packages.

3. Final Answer:

   packages.yml -> Option D

4. Quick Check:

   Package list file = packages.yml [OK]

Hint: Add packages in packages.yml, not dbt_project.yml [OK]

Common Mistakes:

• Adding packages in dbt_project.yml
• Confusing profiles.yml with packages.yml
• Trying to add packages in SQL files

3. Given this packages.yml snippet:

packages:
  - local: ../my_dbt_package

What command installs this package into your project?

easy

A. dbt install

B. dbt build

C. dbt deps

D. dbt run

Solution

1. Step 1: Identify the command for package installation

   dbt uses dbt deps to download and install packages listed in packages.yml.

2. Step 2: Differentiate from other commands

   dbt run runs models, dbt install is not a valid command.

3. Final Answer:

   dbt deps -> Option C

4. Quick Check:

   Install packages with dbt deps [OK]

Hint: Use dbt deps to install packages listed in packages.yml [OK]

Common Mistakes:

• Using dbt install (not a valid command)
• Confusing dbt run with package install
• Trying dbt build instead of dbt deps

4. You created a package but when running dbt deps, you get an error: "Could not find package at path '../my_package'". What is the likely cause?

medium

A. The relative path in packages.yml is incorrect or folder missing

B. You forgot to run dbt run first

C. The package name is missing in dbt_project.yml

D. You need to delete the profiles.yml file

Solution

1. Step 1: Understand the error message

   "Could not find package at path" means dbt cannot locate the folder specified.

2. Step 2: Check the path in packages.yml

   Relative paths must be correct and folder must exist for local packages.

3. Final Answer:

   The relative path in packages.yml is incorrect or folder missing -> Option A

4. Quick Check:

   Path error = wrong folder path [OK]

Hint: Check folder path in packages.yml matches actual location [OK]

Common Mistakes:

• Running dbt run before dbt deps
• Editing dbt_project.yml instead of packages.yml
• Deleting unrelated config files

5. You want to use a model named customer_summary from your custom package my_package. Which is the correct way to reference it in your SQL model?

hard

A. select * from {{ ref('my_package', 'customer_summary') }}

B. select * from {{ ref('my_package.customer_summary') }}

C. select * from {{ ref('customer_summary') }}

D. select * from {{ ref('my_package__customer_summary') }}

Solution

1. Step 1: Recall how to reference models from packages

   Use ref('package_name.model_name') to refer to models in packages.

2. Step 2: Check each option's syntax

   select * from {{ ref('my_package.customer_summary') }} uses the correct single-argument ref syntax with dot notation for packages.

3. Final Answer:

   select * from {{ ref('my_package.customer_summary') }} -> Option B

4. Quick Check:

   Package model ref = ref('package.model') [OK]

Hint: Use ref('package.model') to access package models [OK]

Common Mistakes:

• Using ref('package', 'model') syntax (that's for sources)
• Forgetting the package name in ref
• Using double underscore instead of dot