Which two configurations can be applied to a dbt test?
Choose 2 options.

• A.on_schema_change
• B.tags
• C.enabled
• D.materialized
• E.persist_docs

Comment: *

Name: *

Email: *

Verification: *

While onboarding new data sources to your dbt project, you discover some have unexpectedly high null rates in key columns. How would you integrate tests for this into your dbt workflow?

• A.Create not_null tests on the raw source tables in a separate dbt project dedicated to source validation.
• B.Write tests within the initial staging models that calculate and check the null percentage.
• C.Include a data quality monitoring step in your upstream ETL process before data reaches dbt
• D.Designate some nulls as acceptable by extending the not_null test with the OR condition.

Comment: *

Name: *

Email: *

Verification: *

A source table is updated with a full overwrite every night. Your dbt job fails due to freshness checks. What's a likely cause and solution?

• A.The freshness check is misconfigured- Adjust the count and period settings.
• B.The loaded_at field is absent Add the corresponding column or remove the check-
• C.The source uses an incremental materialization. Change it to a 'table'
• D.You need to schedule the dbt job to run after the nightly update.

Comment: *

Name: *

Email: *

Verification: *

You need to grant readonly access to a new stakeholder on a specific dbt model's output. What factors should influence your approach?

• A.The database technology and its permissions model.
• B.Whether you wish to provide direct table access or a view-based interface.
• C.If this is a one-time need, or something requiring scalable permission management.
• D.The default materialized setting defined for models in your dbt_project_yml file.

Comment: *

Name: *

Email: *

Verification: *

You've updated a model's description in a YAML file to reflect a new business requirement. You've also added additional context to the column descriptions. After regenerating the documentation, you notice the model description has updated, but the column descriptions have not. What could be the most likely reasons?

• A.The documentation was not configured correctly to display column descriptions.
• B.You forgot to run dbt docs generate after modifying the YAML file.
• C.The model's YAML file has incorrect syntax preventing column descriptions from rendering.
• D.You are viewing an older cached version of the documentatiom

Comment: *

Name: *

Email: *

Verification: *