You've defined a model as follows:SQL

• A.A pure SQL issue: The count() function isn't supported for the data type of a column in the 'cust_orders' source.
• B.A Jinja templating error: Misusing the source() function within the count() function.
• C.A data type mismatch between a column in 'stg_customers' and how the query is using it for the join.
• D.An incorrect materialization strategy causing the wrong data to be populated in a downstream source.

Comment: *

Name: *

Email: *

Verification: *

A new stakeholder needs to receive an email report generated from the results of a specific dbt model. Unfortunately, your Bl tool doesn't directly integrate with dbt. How could you address this?

• A.Write a post-hook that queries the model, formats the results, and sends the email.
• B.Develop a separate script, triggered after the dbt job, to handle report generation and emailing-
• C.Within the model's SQLi write logic to insert the output data into a dedicated reporting table-
• D.Modify the model to output a CSV file and schedule a task to email the file as an attachment

Comment: *

Name: *

Email: *

Verification: *

You've defined development, staging, and production targets in your dbt project. You want to prevent accidental execution of destructive model materialization strategies (like drop or truncate) on the production target. How could you achieve this?

• A.Write a custom macro that only executes such operations on non-production targets.
• B.Create a separate profiles.yml file for production that disables dangerous materialization strategies.
• C.Implement a CI/CD process that includes checks to prevent specific dbt commands from running in the production environment
• D.Rely purely on thorough code reviews to prevent execution of these commands in production.

Comment: *

Name: *

Email: *

Verification: *

You run the command:
dbt test --select 'test_type:singular'
What will the command run?
Options shown:

• A.furniture_customers_test
• B.furniture_customers_test
  macro_stg_tpch_orders_assert_pos_price
  macro_stg_tpch_suppliers_assert_pos_acct_bal
  stg_tpch_orders_assert_positive_price
• C.macro_stg_tpch_orders_assert_pos_price
  macro_stg_tpch_suppliers_assert_pos_acct_bal
  stg_tpch_orders_assert_positive_price
• D.furniture_customers_test
  stg_tpch_orders_assert_positive_price
  Choose 1 option.

Comment: *

Name: *

Email: *

Verification: *

During a code review, a collaborator suggests modifying a small portion of code you had already committed to your feature branch. What's the most efficient way to address this without creating a completely new commit?

• A.Create a new branch extending from your feature branch, make the change, and open a separate pull request.
• B.Use git revert to undo your previous commit, make the change, and then re-commit.
• C.Use git commit -amend to modify your most recent commit.
• D.Explain to your collaborator that modifying committed code is not recommended, and the change should wait for a future update.

Comment: *

Name: *

Email: *

Verification: *