Select the dbt materialization that typically DOES NOT persist its results to disk:

• A.Table
• B.Snapshot
• C.Incremental
• D.Ephemeral

Comment: *

Name: *

Email: *

Verification: *

A marketing team needs a model to calculate the 30-day rolling average of new customer signups. The raw signups table is very large and updated hourly. Which approach strikes the best balance between accuracy and computational efficiency?

• A.A view materialization that recalculates the 30-day rolling average for each query.
• B.A table materialization that completely rebuilds the rolling average daily.
• C.An incremental model that updates the rolling average calculations only for new signup records.
• D.An ephemeral model that calculates the rolling average within a series of complex CTEs.

Comment: *

Name: *

Email: *

Verification: *

(Multiple Select)

• A.Instruct dbt to rename columns rather than dropping and recreating them during updates.
• B.Create views on top of dbt model tables, providing a stable abstraction layer for the Bl tools.
• C.Establish a naming convention in dbt that external tools can rely upon.
• D.Avoid refactoring dbt models that are directly queried by external tools.

Comment: *

Name: *

Email: *

Verification: *

A user reports a critical security issue discovered in a third-party dbt package you use. Where could you most likely find updated information about potential vulnerabilities or fixes?

• A.The packages.yml file in your dbt project.
• B.Directly from the maintainer of the dbt package, often in a GitHub repository or similar
• C.Within dbt Cloud's central package documentation and release notes.
• D.The locally generated dbt documentation for the installed packages.

Comment: *

Name: *

Email: *

Verification: *

A large dimension table is joined frequently in your dbt models. Due to its size, these joins significantly impact performance. Which strategy might offer improvement?

• A.Add a WHERE clause to the model to filter out unnecessary rows during the join.
• B.If the dimension data rarely changes, convert it to an incremental model.
• C.Rewrite the join logic by nesting conditions within a CTE.
• D.Investigate database-specific techniques like hash joins or distribution keys for optimizing the join.

Comment: *

Name: *

Email: *

Verification: *