Model contracts and access controls in dbt - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a model contract in dbt.

dbt

version: 2
models:
  - name: my_model
    [1]:
      - name: id
        data_type: integer

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

Acolumns

Btests

Csources

Dseeds

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'tests' instead of 'columns' to define the contract.

Confusing 'sources' with model contract definitions.

The columns key defines the model contract by specifying expected columns and their data types.

2fill in blank

medium

Complete the code to add an access control tag to a model in dbt.

dbt

models:
  - name: sensitive_data
    tags: [[1]]

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

A"finance"

B"access_control"

C"restricted"

D"public"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'public' tag for sensitive data models.

Using unrelated tags like 'finance' without access meaning.

The tag "restricted" is commonly used to indicate access control on sensitive models.

3fill in blank

hard

Fix the error in the model contract by completing the missing key.

dbt

models:
  - name: user_data
    columns:
      - name: user_id
        [1]: string

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

Adata_type

Bdatatype

Ctype

Ddtype

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'type' instead of 'data_type'.

Using 'dtype' which is not recognized by dbt.

The correct key to specify the data type in dbt model contracts is data_type.

4fill in blank

hard

Fill both blanks to create a test for a model contract that checks for uniqueness and non-null values.

dbt

models:
  - name: orders
    columns:
      - name: order_id
        data_type: integer
        tests: [[1], [2]]

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

Aunique

Bnot_null

Caccepted_values

Drelationships

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'accepted_values' instead of uniqueness test.

Omitting the 'not_null' test.

The tests unique and not_null ensure the column has unique and non-null values respectively.

5fill in blank

hard

Fill all three blanks to define a model contract with columns, data types, and a test for accepted values.

dbt

models:
  - name: products
    columns:
      - name: category
        data_type: string
        tests: [[1]]
      - name: price
        data_type: float
        tests: [[2]]
      - name: stock
        data_type: integer
        tests: [[3]]

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

Aaccepted_values

Bnot_null

Cunique

Drelationships

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up tests between columns.

Using 'relationships' test where not applicable.

The 'category' column uses accepted_values to restrict allowed categories. The 'price' column uses not_null to ensure prices exist. The 'stock' column uses unique to ensure unique stock entries.