Why governance ensures data trust in dbt - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a source in dbt that includes a description for governance.

dbt

sources:
  - name: my_source
    description: [1]

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

ANone

B12345

CTrue

D"Source for sales data with governance details"

Attempts:

3 left

💡 Hint

Common Mistakes

Using a number instead of a string for description.

Leaving description empty or None.

The description field should be a clear text explaining the source, which helps in governance by documenting data origins.

2fill in blank

medium

Complete the code to add a freshness check to ensure data trust.

dbt

sources:
  - name: my_source
    freshness:
      [1]: {count: 24, period: hour}

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

Afail_after

Bwarn_after

Crefresh_interval

Dcheck_frequency

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'fail_after' which causes errors instead of warnings.

Using non-existent keys like 'refresh_interval'.

The warn_after key sets the threshold in hours after which dbt warns if data is stale, supporting data trust.

3fill in blank

hard

Fix the error in the dbt model config to enable governance tags.

dbt

models:
  - name: my_model
    [1]:
      tags: ['governance', 'trusted']

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

Aconfig

Bconfiguration

Csettings

Doptions

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'configuration' or 'settings' which are invalid keys.

Omitting the config block entirely.

The correct key to configure model properties like tags is config.

4fill in blank

hard

Fill both blanks to create a test that ensures no nulls in a critical column for data trust.

dbt

tests:
  - [1]:
      column_name: [2]

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

Anot_null

Bunique

Ccustomer_id

Dorder_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'unique' test which checks uniqueness, not nulls.

Choosing a non-key column.

The not_null test checks that the specified column has no null values, which is important for data trust.

5fill in blank

hard

Fill all three blanks to define a schema test with severity and tags for governance.

dbt

tests:
  - name: [1]
    severity: [2]
    tags: [[3]]

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

Aunique_customer_id

Berror

C'governance'

Dwarn

Attempts:

3 left

💡 Hint

Common Mistakes

Using severity 'warn' which only warns but does not fail.

Omitting governance tag.

The test name is 'unique_customer_id', severity is set to 'error' to fail on issues, and the tag 'governance' marks it for governance tracking.