Which two configuration items can be defined under models: in your dbt_project.yml file?
Choose 2 options.

• A.schema
• B.source
• C.tags
• D.test
• E.target

Comment: *

Name: *

Email: *

Verification: *

You maintain a large dbt project with various reporting models that source data from a set of core business tables. These core tables often include columns with sensitive information. What technique could ensure compliance and maintainability when restricting access to this data?

• A.Use views to create different projections of the core tables, exposing only the necessary columns.
• B.Create incremental models that directly remove the sensitive columns before reporting models utilize them.
• C.Write complex WHERE clauses in each reporting model to exclude rows containing sensitive data.
• D.Apply row-level security within the data warehouse itself for fine-grained control.

Comment: *

Name: *

Email: *

Verification: *

You want to experiment with a new column in an existing model without risking production changes. Which configuration strategy in your dbt_project.yml would support this safely?

• A.Add a -select flag when using dbt run to execute only the modified model.
• B.Define separate configurations for the column under the model and use the enabled property.
• C.Modify the model SQL using the config.get() macro to dynamically control the column's behavior
• D.Utilize git branches and have different dbt_project.yml files for your production and experimental branches.

Comment: *

Name: *

Email: *

Verification: *

Your data warehouse is undergoing a migration to a different vendor (e.g., Snowflake to BigQuery). Which category of tools might play a critical role in ensuring a smooth transition of your dbt project?

• A.Data virtualization tools
• B.Cloud infrastructure management tools
• C.SQL dialect translation tools
• D.dbt adapters

Comment: *

Name: *

Email: *

Verification: *

You've merged a pull request but later discover it introduced a regression (unexpectedly broke existing functionality). What's the most common initial step to address this?

• A.Run git revert on the merge commit to undo the changes.
• B.Open a new pull request with a fix for the regression.
• C.Use git blame or git log to pinpoint the commit that caused the issue.
• D.Coordinate with the original author of the merged pull request.

Comment: *

Name: *

Email: *

Verification: *