Practise the standard verbs for testing and documenting dbt models.
0 / 5 completed
1 / 5
Fill in: 'We ___ a not-null and uniqueness test on every primary key column so a broken upstream join surfaces in CI, not in a stakeholder's dashboard.'
We 'write a test' — the standard, simple collocation for authoring a data-quality assertion. The other options are less idiomatic here.
2 / 5
Fill in: 'Skipping schema tests on staging models can ___ a duplicate row silently propagating all the way into a finance report.'
We say skipped tests will 'leave' a duplicate propagating — the standard, natural collocation for the resulting risk. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ dbt test in CI on every pull request so a failing assertion blocks the merge instead of landing quietly in production.'
We 'run' a test command — the standard, simple collocation for executing a suite of assertions. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every model's assumptions in its schema.yml file so a new analyst understands what a column actually means before querying it.'
We 'document' an assumption — the standard, simple collocation for recording a model's intended meaning. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ slow-running models with a dedicated tag so a nightly build can skip them without touching the models that need to run hourly.'
We 'tag a model' — the standard, established dbt collocation for attaching a label used to select or exclude models in a run. The other options aren't the recognised term here.