(Multiple Select)

• A.model-paths
• B.test-paths
• C.materialized: view
• D.database

Comment: *

Name: *

Email: *

Verification: *

You discover that an essential dbt macro behaves differently between your development environment and production due to a subtle database version discrepancy. Which debugging approach would be most efficient?

• A.Add verbose logging within the macro to track execution differences step by step.
• B.Temporarily introduce a conditional branch into the macro code that is environment-aware.
• C.Use database-specific functions to query the version information directly from within dbt models.
• D.Set up a CIICD test that runs the macro in isolation using both database versions.

Comment: *

Name: *

Email: *

Verification: *

You discover an intermittent issue where your models sometimes produce incorrect results. After investigation, the problem seems to occur when the source data contains a particular combination of unexpected values. How would you best address this?

• A.Add pre-processing logic within the model to clean or filter out the problematic data.
• B.Write a custom dbt test to explicitly identify the bad data scenario.
• C.Raise an issue with the team responsible for the upstream data source to fix the error at its origin.
• D.Modify the model to ignore the rows causing the issue.

Comment: *

Name: *

Email: *

Verification: *

You've built a macro to implement a common custom test pattern. When using this macro in multiple models, you realize the tests are running much slower than expected. What might be the cause?

• A.The macro's SQL logic is inefficiently querying the model or other data.
• B.Too many tests are being defined on individual models.
• C.The macro is accidentally triggering downstream model rebuilds.
• D.This is expected behavior, and custom tests always incur a performance penalty.

Comment: *

Name: *

Email: *

Verification: *

You're onboarding a new dbt project to an existing production database. You find tables that might conflict with naming conventions used by dbt. What's a proactive way to handle this?

• A.Customize the schema property in your dbt_project.yml to namespace dbt-generated objects.
• B.Add configuration settings to your database connection profile instructing dbt to use a specific schema prefix.
• C.Manually rename the conflicting tables in the database prior to running any dbt jobs.
• D.Update your dbt models to use aliases that avoid the name collisions.

Comment: *

Name: *

Email: *

Verification: *