Bird
0
0

A user sets store_failures = true but the failure table contains unexpected columns. What is a likely reason?

medium📝 Debug Q7 of 15
dbt - Advanced Testing
A user sets store_failures = true but the failure table contains unexpected columns. What is a likely reason?
AFailure tables always contain only the tested column.
BThe test was customized with additional columns in the failure output.
CThe failure table is corrupted and should be deleted.
Ddbt automatically adds audit columns to failure tables.
Step-by-Step Solution
Solution:

  1. Step 1: Understand default failure table columns

    By default, failure tables include all columns from the model.

  2. Step 2: Consider customization

    Tests can be customized to add or remove columns in failure output.

  3. Final Answer:

    The test was customized with additional columns in the failure output. -> Option B

  4. Quick Check:

    Custom test changes failure table columns [OK]
Quick Trick: Custom tests can change failure table columns [OK]
Common Mistakes:
MISTAKES
  • Assuming failure tables have fixed columns
  • Thinking dbt adds audit columns automatically
  • Believing corruption causes extra columns

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More dbt Quizzes
Advanced Testing - dbt-utils package tests - Quiz 3easy Advanced Testing - Unit testing dbt models - Quiz 1easy Incremental Models - Why incremental models save time and cost - Quiz 2easy Jinja in dbt - Built-in Jinja context variables - Quiz 8hard Jinja in dbt - For loops for dynamic SQL - Quiz 6medium Jinja in dbt - Why Jinja makes SQL dynamic - Quiz 11easy Jinja in dbt - Why Jinja makes SQL dynamic - Quiz 13medium Packages and Reusability - Installing packages with packages.yml - Quiz 5medium Packages and Reusability - dbt-utils (surrogate_key, pivot, unpivot) - Quiz 2easy Project Organization - Staging, intermediate, and marts pattern - Quiz 14medium