Study plan

Start hereStudy noteDeveloping and optimizing dbt models

Tracing and confirming a model's upstream raw sources

Objective 1 of 14 in Developing and optimizing dbt models, the first section in the guide. Not tried yet. See all 7 exam sections

What this note covers

Raw object dependencies are references to source tables/views in the underlying data platform (not other dbt models) that a dbt project relies on. Before building or optimizing models, analytics engineers must identify these upstream raw dependencies and verify they exist, are accessible, and are correctly declared so the DAG builds accurately and lineage stays trustworthy.

The facts the exam tests

• 1Raw dependencies should be declared using source() functions in models, pointing to tables/views defined in a sources.yml file rather than hardcoded schema.table references.
• 2Running dbt source freshness checks whether raw source tables are being loaded on the expected schedule, helping surface stale or broken upstream dependencies.
• 3The dbt docs generate command combined with dbt docs serve lets you inspect the DAG and confirm which raw sources feed into which models, making it easier to spot missing or unused dependencies.
• 4Using source() instead of direct table references ensures raw dependencies appear correctly in the DAG and enables features like source freshness and lineage graphs.
• 5A model that references a raw table directly (e.g., via a raw SQL FROM clause) bypasses dbt's dependency tracking, which can break run order and make impact analysis unreliable.
• 6The dbt list (or ls) command with selectors like source:* can be used to verify which sources exist in the project and confirm they are referenced as expected before development or refactoring begins.