Handling late-arriving data in dbt - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to select all records from the source table.

dbt

SELECT * FROM [1]

Drag options to blanks, or click blank then click option'

Alate_data

Bfinal_table

Cstaging_table

Dsource_table

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing the final or staging table instead of the source table.

Using a table name that does not exist.

The source table contains the raw incoming data including late arrivals.

2fill in blank

medium

Complete the code to filter records where the event date is after the last processed date.

dbt

WHERE event_date > [1]

Drag options to blanks, or click blank then click option'

Alast_processed_date

Bcurrent_date

Cstart_date

Dmax_date

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'current_date' which filters out late data.

Using 'start_date' which might exclude some late arrivals.

Filtering with 'last_processed_date' ensures only new or late-arriving data is processed.

3fill in blank

hard

Fix the error in the merge statement to update existing records with late-arriving data.

dbt

MERGE INTO final_table AS target USING staging_table AS source ON target.id = source.id WHEN MATCHED THEN [1]

Drag options to blanks, or click blank then click option'

AINSERT

BUPDATE SET target.value = source.value

CDELETE

DSELECT *

Attempts:

3 left

💡 Hint

Common Mistakes

Using DELETE which removes records instead of updating.

Using INSERT which is for new records, not matches.

The 'UPDATE SET' clause updates existing records with new values from late-arriving data.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that filters late-arriving data by date and updates values.

dbt

late_data = {record['id']: record[1] for record in data if record['date'] [2] last_processed_date}

Drag options to blanks, or click blank then click option'

A.update({'value': new_value})

B>

C>=

D.copy()

Attempts:

3 left

💡 Hint

Common Mistakes

Using '.update()' which returns None and breaks comprehension.

Using '>=' which includes already processed data.

We copy each record to avoid modifying original data and filter records with date greater than last processed date.

5fill in blank

hard

Fill all three blanks to create a SQL query that merges late-arriving data, updating existing records and inserting new ones.

dbt

MERGE INTO final_table AS target USING [1] AS source ON target.id = source.id WHEN MATCHED THEN [2] WHEN NOT MATCHED THEN [3]

Drag options to blanks, or click blank then click option'

Astaging_table

BUPDATE SET target.value = source.value

CINSERT (id, value) VALUES (source.id, source.value)

Dsource_table

Attempts:

3 left

💡 Hint

Common Mistakes

Using source_table instead of staging_table as source.

Using DELETE instead of UPDATE for matched records.

Omitting the INSERT clause for new records.

The staging table holds late-arriving data. Matched records are updated, unmatched are inserted.

Practice

1. What does late-arriving data mean in data processing?

easy

A. Data that is generated by a different system

B. Data that arrives after the expected time window

C. Data that is duplicated in the dataset

D. Data that is corrupted or incomplete

Solution

1. Step 1: Understand the timing of data arrival

   Late-arriving data refers to data that comes in after the time it was expected to be available for processing.

2. Step 2: Differentiate from other data issues

   It is not about corruption, duplication, or source system differences, but purely about timing.

3. Final Answer:

   Data that arrives after the expected time window -> Option B

4. Quick Check:

   Late-arriving data = late arrival [OK]

Hint: Late-arriving means data comes late, not corrupted or duplicated [OK]

Common Mistakes:

• Confusing late data with corrupted data
• Thinking late data means duplicate records
• Assuming late data is from a different system

2. Which of the following is the correct way to filter late-arriving data in a dbt SQL model?

easy

A. WHERE event_date < current_date - interval '1 day'

B. WHERE event_date > current_date + interval '1 day'

C. WHERE event_date = current_date

D. WHERE event_date IS NULL

Solution

1. Step 1: Understand filtering late data by date

   Late-arriving data is usually older than the current date minus a buffer (like 1 day), so we filter for dates less than that.

2. Step 2: Check each option's logic

   WHERE event_date < current_date - interval '1 day' filters for event_date before yesterday, which captures late data. WHERE event_date > current_date + interval '1 day' filters future dates, which is incorrect. WHERE event_date = current_date filters only today's data, ignoring late data. WHERE event_date IS NULL filters nulls, unrelated to late data.

3. Final Answer:

   WHERE event_date < current_date - interval '1 day' -> Option A

4. Quick Check:

   Filter dates before yesterday = WHERE event_date < current_date - interval '1 day' [OK]

Hint: Late data usually has older dates than today minus buffer [OK]

Common Mistakes:

• Filtering future dates instead of past dates
• Filtering only current date data
• Filtering null dates instead of late data

3. Given this dbt incremental model SQL snippet:

SELECT
  id,
  event_date,
  data_value
FROM source_table
WHERE event_date >= (SELECT MAX(event_date) FROM {{ this }})

What is the main purpose of this WHERE clause?

medium

A. To select only new or updated data since last run

B. To select all data including duplicates

C. To exclude all late-arriving data

D. To select data with null event_date

Solution

1. Step 1: Analyze the WHERE clause logic

   The clause filters rows where event_date is greater or equal to the max event_date already in the target table, meaning it picks new or updated data since last run.

2. Step 2: Understand incremental model behavior

   This is a common pattern in dbt incremental models to avoid reprocessing old data and only add new or changed rows.

3. Final Answer:

   To select only new or updated data since last run -> Option A

4. Quick Check:

   Incremental filter = new or updated data [OK]

Hint: Incremental models filter data newer than max existing date [OK]

Common Mistakes:

• Thinking it excludes late-arriving data
• Assuming it selects duplicates
• Confusing null filtering with this clause

4. You wrote this dbt incremental model filter:

WHERE event_date > (SELECT MAX(event_date) FROM {{ this }})

But your model misses some late-arriving data. What is the likely problem?

medium

A. The subquery syntax is invalid in dbt

B. You should filter with event_date < instead

C. Using > instead of >= excludes data with event_date equal to max date

D. Late-arriving data always has null event_date

Solution

1. Step 1: Understand the difference between > and >=

   Using > excludes rows where event_date equals the max date already processed, which can miss late-arriving data with that date.

2. Step 2: Correct the filter to include equal dates

   Changing to >= includes those rows, capturing late-arriving data that arrived late but has the same event_date.

3. Final Answer:

   Using > instead of >= excludes data with event_date equal to max date -> Option C

4. Quick Check:

   Use >= to include late data on max date [OK]

Hint: Use >= not > to include late data on max date [OK]

Common Mistakes:

• Using > excludes late data with max date
• Thinking subquery is invalid in dbt
• Filtering with < instead of >
• Assuming late data has null dates

5. You want to handle late-arriving data in a dbt incremental model. Which approach best ensures late data is included without duplicating existing rows?

hard

A. Filter only event_date = current_date to avoid duplicates

B. Delete all data and reload full dataset every run

C. Ignore late-arriving data to keep model simple

D. Use a merge strategy with unique keys and filter event_date >= max date

Solution

1. Step 1: Understand the goal of including late-arriving data

   Late data can have event_dates already processed, so we must update or insert without duplicates.

2. Step 2: Use merge strategy with unique keys and proper filtering

   Using a merge (upsert) with unique keys and filtering event_date >= max date ensures late data is added or updated correctly.

3. Step 3: Evaluate other options

   Deleting all data every run is costly. Ignoring late data loses accuracy. Filtering only current_date misses late data.

4. Final Answer:

   Use a merge strategy with unique keys and filter event_date >= max date -> Option D

5. Quick Check:

   Merge + unique keys + >= max date = best late data handling [OK]

Hint: Merge with unique keys and >= max date handles late data well [OK]

Common Mistakes:

• Reloading full data every run is inefficient
• Ignoring late data causes incomplete analysis
• Filtering only current date misses late data