Your team follows a convention where commit messages include a relevant issue tracker reference (e.g., JIRA- 123). You've been working on multiple features and fixes. Which of the following best promotes clean commits?

• A. Break down your changes into smaller, atomic commits, each referencing the issue it addresses.
• B. Don't worry about commit messages, as the pull request title and description are more important.
• C. Include all relevant issue references in a single commit message when you're ready to create a pull request.
• D. Commit all your changes at once with a generic message like "Project updates."

You're setting up CI/CD for your dbt project to automate deployments. Which aspects of your testing strategy might need adaptation for a production-focused CI/CD workflow?

• A. Disabling all tests that rely on creating new tables, to avoid impacting the production database.
• B. Including smoke tests that run in production to verify core functionality after a deployment.
• C. Emphasizing tests with longer run times for thorough checks before deployment.
• D. Prioritizing tests with strict thresholds to avoid false positives from minor data variations in production.

You notice a pattern where warnings are generated for several models due to missing descriptions. How could you configure dbt_project.yml to fail these models instead when descriptions are absent?

• A. Add on-run-start and on-run-end hooks to perform custom checks
• B. Set a project-level severity setting under the tests: section.
• C. Introduce a custom macro to validate model descriptions_
• D. Globally change the default warning behavior using the warn-if: configuration

Several of your users report that dashboards built on top of your dbt models are intermittently displaying stale dat a. Which of the following might be a potential cause?

• A. Some models have incorrect materializations, causing them to not update when expected
• B. All of the above.
• C. There are dependency issues in your DAG affecting execution order.
• D. Source freshness checks are configured incorrectly, allowing older data to be processed

You want to trigger a dbt job immediately upon successful completion of an upstream ETL process. Which methods could achieve this?

• A. Using dbt Cloud's webhooks to create an endpoint that your ETL process can call.
• B. Using the dbt build command to run all dependent models after a successful dbt run.
• C. Configuring the ETL process to send a completion notification to your CIICD tool, triggering the dbt job.
• D. Scheduling a dbt job with a very frequent interval (e.g., every 5 minutes) to poll for changes in a metadata table.