if/else logic in models in dbt - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of conditional logic in a dbt model

Consider this dbt model SQL snippet using a CASE statement. What will be the value of category for a row where sales_amount is 150?

dbt

SELECT
  sales_amount,
  CASE
    WHEN sales_amount > 200 THEN 'High'
    WHEN sales_amount > 100 THEN 'Medium'
    ELSE 'Low'
  END AS category
FROM sales_data

A NULL

B 'High'

C 'Low'

D 'Medium'

💡 Hint

Think about the order of conditions in the CASE statement and which condition matches 150.

The CASE statement checks conditions in order. Since 150 is not greater than 200, the first WHEN is false. The second WHEN checks if 150 is greater than 100, which is true, so the category is 'Medium'.

❓ data_output

intermediate

Resulting rows after applying if/else logic in a dbt model

Given this dbt model SQL, how many rows will have status = 'Active'?

dbt

SELECT
  user_id,
  CASE
    WHEN last_login > CURRENT_DATE - INTERVAL '30 days' THEN 'Active'
    ELSE 'Inactive'
  END AS status
FROM user_logins

A No users, because of syntax error

B All users who logged in within the last 30 days

C All users regardless of login date

D All users who logged in more than 30 days ago

💡 Hint

Look at the condition comparing last_login date with current date minus 30 days.

The CASE checks if last_login is within the last 30 days. Those users get 'Active'. Others get 'Inactive'. So only users with recent logins are 'Active'.

🔧 Debug

advanced

Identify the error in if/else logic in a dbt model

This dbt model SQL snippet is intended to assign a label based on score. What error will it raise?

dbt

SELECT
  user_id,
  CASE
    WHEN score > 90 THEN 'Excellent'
    WHEN score > 75 THEN 'Good'
    ELSE 'Average'
  END AS performance
FROM user_scores
WHERE score >= 0

A No error, runs correctly

B SyntaxError due to missing END keyword

C Runtime error because score can be NULL

D TypeError because score is compared to string

💡 Hint

Check if the CASE statement syntax is complete and if the WHERE clause handles NULLs.

The CASE statement is correctly formed with END. The WHERE clause filters out negative scores but does not exclude NULLs, which may or may not cause issues depending on the database. However, no syntax or type errors exist here.

🚀 Application

advanced

Applying if/else logic to create a new column in a dbt model

You want to create a new column risk_level in your dbt model based on credit_score: scores above 700 are 'Low', between 500 and 700 are 'Medium', and below 500 are 'High'. Which SQL snippet correctly implements this?

A CASE WHEN credit_score > 700 THEN 'Low' WHEN credit_score >= 500 THEN 'Medium' ELSE 'High' END AS risk_level

B CASE WHEN credit_score >= 700 THEN 'Low' WHEN credit_score > 500 THEN 'Medium' ELSE 'High' END AS risk_level

C CASE WHEN credit_score > 700 THEN 'Low' WHEN credit_score > 500 THEN 'Medium' ELSE 'High' END AS risk_level

D CASE WHEN credit_score >= 700 THEN 'Low' WHEN credit_score >= 500 THEN 'Medium' ELSE 'High' END AS risk_level

💡 Hint

Pay attention to the boundary conditions and whether to use > or >=.

Option A correctly assigns 'Low' for scores strictly greater than 700, 'Medium' for scores from 500 up to and including 700, and 'High' otherwise. This matches the requirement.

🧠 Conceptual

expert

Understanding nested if/else logic in dbt models

In dbt models, what is the main difference between using nested CASE statements versus multiple WHEN conditions in a single CASE statement?

A Multiple WHEN conditions execute faster than nested CASE statements in all databases.

B Nested CASE statements are invalid syntax in dbt models.

C Nested CASE statements allow more complex, multi-level decision trees, while multiple WHEN conditions in one CASE are flat and evaluated in order.

D Multiple WHEN conditions can only handle numeric comparisons, nested CASE can handle strings.

💡 Hint

Think about how CASE statements evaluate conditions and how nesting affects logic structure.

Nested CASE statements let you build multi-level decisions, like if/else inside if/else, while multiple WHENs in one CASE are checked sequentially in a flat structure.