You have created a model called stg_tasks and now you need to implement tests.
You provide this in schema.yml:
version: 2
models:
- name: stg_tasks
columns:
- name: completed_at
tests:
- not_null:
- config:
where: "state = 'completed'"
You receive this compilation error:
[WARNING]: Did not find matching node for patch with name 'stg_tasks' in the 'models' section of file
'models/example/schema.yml'
How can you change the configuration on the not_null test to fix this compiler error?

• A.tests:
  - not_null:
  - config:
  where: "state = 'completed'"
• B.tests:
  - not_null:
  config:
  where: "state = 'completed'"
• C.tests:
  - not_null:
  config:
  where: "state = 'completed'"
• D.tests:
  - not_null:
  - config:
  where: "state = 'completed'"
  Choose 1 option.

Comment: *

Name: *

Email: *

Verification: *

You're setting up a dbt project with a model that generates a large intermediate result. You're concerned about performance. Which approaches could be helpful?

• A.Use a staging schema for the intermediate model and adjust the job's materialization settings.
• B.Investigate database-specific features (e.g., temporary tables ) and refactor dbt logic to leverage them.
• C.Schedule the model to run only during off-peak hours.
• D.Deploy the dbt project to a smaller development environment to reduce processing overhead

Comment: *

Name: *

Email: *

Verification: *

You need to test whether the values of a specific column have changed over time. What might be the best approach to implement this kind of test within your dbt project?

• A.Use a snapshot to preserve a point-in-time reference of the column.
• B.Use a custom 'accepted_values' test together with a dbt seed.
• C.Write a dbt macro to create a temporary table with historical data to compare against.
• D.rely on native version history features in your data warehouse (if available).

Comment: *

Name: *

Email: *

Verification: *

You want to implement a macro that displays a warning icon next to models in the DAG that haven't been tested. Which of the following would be necessary to make this work?

• A.A custom CSS class for the warning icon and a way to apply it dynamically using the macro.
• B.The ability for the macro to query the results of test executions from the dbt run-
• C.Configuration in your dbt_projectyml file to associate models with the relevant tests.
• D.All of the above.

Comment: *

Name: *

Email: *

Verification: *

You're working in a large, enterprise-level dbt deployment. Which aspect of using dbt documentation commands could become especially important in this context?

• A.Optimizing the dbt docs generate process for very large projects to minimize execution time.
• B.Version-controlling your documentation changes alongside your project code.
• C.Developing strict documentation contribution guidelines for multiple teams and collaborators.
• D.All of the above.

Comment: *

Name: *

Email: *

Verification: *