Materializations strategy in dbt - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the materialization to table in a dbt model.

dbt

{{ config(materialized = '[1]') }}

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

Aview

Btable

Cincremental

Dephemeral

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'view' instead of 'table' creates a virtual table, not a physical one.

Using 'incremental' requires additional configuration.

Setting materialized = 'table' tells dbt to create a physical table for the model.

2fill in blank

medium

Complete the code to define an incremental materialization with a unique key.

dbt

{{ config(
  materialized = 'incremental',
  unique_key = '[1]'
) }}

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

Aid

Bdate

Cname

Dvalue

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-unique column like 'name' can cause incorrect incremental updates.

Leaving unique_key undefined for incremental models causes errors.

The unique_key is usually the primary key column like id to identify new or updated rows.

3fill in blank

hard

Fix the error in the materialization config to use the correct keyword for ephemeral models.

dbt

{{ config(materialized = '[1]') }}

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

Atransient

Btemporary

Cephemeral

Dvirtual

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'temporary' or 'transient' which are not valid dbt materializations.

Confusing ephemeral with view materialization.

The correct materialization keyword for ephemeral models is ephemeral. Other options are invalid in dbt.

4fill in blank

hard

Fill both blanks to create a model materialized as incremental with a filter on updated_at column.

dbt

{{ config(materialized = '[1]') }}

select * from events
where updated_at > '[2]'

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

Aincremental

Btable

C2023-01-01

D2022-12-31

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'table' instead of 'incremental' for incremental loading.

Using an incorrect date format or older date.

Incremental materialization with a filter on updated_at after 2023-01-01 helps load only recent data.

5fill in blank

hard

Fill all three blanks to define a materialization strategy with table, unique_key, and incremental filter.

dbt

{{ config(
  materialized = '[1]',
  unique_key = '[2]'
) }}

select * from events
where created_at > '[3]'

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

Aincremental

Bid

C2023-06-01

Dtable

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing incremental materialization with table without proper config.

Using wrong date format or missing unique_key.

This sets a table materialization with a unique key id and filters rows created after 2023-06-01.