Slim CI with state comparison in dbt - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable slim CI by specifying the correct flag.

dbt

dbt run --[1] slim

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

Aenable

Bstate

Cuse

Dwith

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--enable' instead of '--state' will cause an error.

Using '--use' or '--with' are not valid flags for slim CI.

The --state flag is used to enable slim CI by comparing the current state with the previous run.

2fill in blank

medium

Complete the code to specify the path to the previous run's manifest for state comparison.

dbt

dbt run --state [1]

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

Atarget

Btarget/previous

Ctarget/previous/manifest.json

Dtarget/manifest.json

Attempts:

3 left

💡 Hint

Common Mistakes

Using just 'target' or 'target/manifest.json' will not point to the previous run.

Missing the 'previous' folder in the path.

The path target/previous/manifest.json points to the previous run's manifest file used for state comparison in slim CI.

3fill in blank

hard

Fix the error in the command to run dbt with slim CI and state comparison.

dbt

dbt run --state=[1]

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

Atarget/manifest.json

Btarget/previous/manifest.json

Cprevious/manifest.json

Dtarget/previous

Attempts:

3 left

💡 Hint

Common Mistakes

Providing the full manifest file path causes an error.

Using an incomplete or wrong directory path.

The --state flag expects the directory path containing the previous run's manifest, not the manifest file itself.

4fill in blank

hard

Fill both blanks to create a command that runs dbt with slim CI using the correct state directory and selector.

dbt

dbt run --state [1] --select [2]

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

Atarget/previous

Bmodels+

Ctarget

Dsources

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'target' instead of 'target/previous' for state.

Using 'sources' instead of 'models+' for selection.

The --state target/previous flag points to the previous run's state, and --select models+ selects models and their dependencies for the run.

5fill in blank

hard

Fill all three blanks to write a dbt command that runs slim CI with state comparison, specifying the state directory, selector, and output format.

dbt

dbt run --state [1] --select [2] --output [3]

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

Atarget/previous

Bmodels+

Cjson

Dtarget

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'target' instead of 'target/previous' for state.

Using 'sources' instead of 'models+' for selection.

Using 'table' or other formats instead of 'json' for output.

This command runs dbt with slim CI using the previous state directory, selects models and their dependencies, and outputs results in JSON format.

Practice

1. What is the main purpose of using --state and --select state:modified in dbt's Slim CI?

easy

A. To delete all previous run artifacts

B. To run all models regardless of changes

C. To create a backup of the current state

D. To run only the models that have changed since the last run

Solution

1. Step 1: Understand the role of --state

   The --state flag points dbt to the previous run's artifacts, allowing comparison between runs.

2. Step 2: Understand --select state:modified

   This selects only the models that have changed compared to the previous state, skipping unchanged models.

3. Final Answer:

   To run only the models that have changed since the last run -> Option D

4. Quick Check:

   Slim CI runs changed models only [OK]

Hint: Slim CI runs changed models only, saving time [OK]

Common Mistakes:

• Thinking it runs all models every time
• Confusing state with backup or deletion
• Assuming it runs unchanged models too

2. Which of the following is the correct syntax to run dbt with Slim CI to select only modified models?

easy

A. dbt run --state path/to/previous --select all

B. dbt run --select state:modified --state path/to/previous

C. dbt run --select modified:state --state=previous_path

D. dbt run --state-modified --select path/to/previous

Solution

1. Step 1: Identify correct flag usage

   The correct flags are --state to specify previous run artifacts and --select state:modified to select changed models.

2. Step 2: Match syntax to flags

   dbt run --select state:modified --state path/to/previous correctly uses --select state:modified and --state path/to/previous in proper order and format.

3. Final Answer:

   dbt run --select state:modified --state path/to/previous -> Option B

4. Quick Check:

   Correct flags and order [OK]

Hint: Use --state then --select state:modified for Slim CI [OK]

Common Mistakes:

• Mixing up flag names or order
• Using incorrect flag syntax
• Selecting all models instead of modified

3. Given the following dbt command run twice with changes in model 'sales':

dbt run --state ./target/run1 --select state:modified
# After modifying 'sales' model
 dbt run --state ./target/run1 --select state:modified

What will the second command do?

medium

A. Run only the 'sales' model because it was modified

B. Run all models again ignoring state

C. Run no models because nothing changed

D. Throw an error due to incorrect state path

Solution

1. Step 1: Understand the first run

   The first command runs all models and saves state in ./target/run1.

2. Step 2: Analyze the second run with modification

   The second command compares current state to ./target/run1 and runs only models that changed, here 'sales'.

3. Final Answer:

   Run only the 'sales' model because it was modified -> Option A

4. Quick Check:

   Modified model runs only [OK]

Hint: Second run runs only changed models using saved state [OK]

Common Mistakes:

• Assuming all models run again
• Thinking no models run if only one changed
• Confusing state path usage

4. You run dbt run --state ./previous_run --select state:modified but get an error saying the state path is invalid. What is the most likely cause?

medium

A. The path './previous_run' does not contain valid dbt run artifacts

B. You forgot to add '--select all' flag

C. The '--state' flag must come after '--select'

D. The command requires '--full-refresh' to work

Solution

1. Step 1: Check the meaning of the error

   An invalid state path error means dbt cannot find or read previous run artifacts at the given path.

2. Step 2: Evaluate other options

   Flags order or missing '--select all' do not cause this error; '--full-refresh' is unrelated.

3. Final Answer:

   The path './previous_run' does not contain valid dbt run artifacts -> Option A

4. Quick Check:

   Invalid state path means missing artifacts [OK]

Hint: Ensure state path has valid previous run artifacts [OK]

Common Mistakes:

• Assuming flag order causes error
• Thinking '--full-refresh' fixes state errors
• Forgetting to generate previous run artifacts

5. You want to optimize your CI pipeline using Slim CI. Your previous run artifacts are stored in ./target/previous. You have models 'A', 'B', and 'C'. Only 'B' was modified. Which command will run only the modified model and also run its dependent models?

hard

A. dbt run --state ./target/previous --select state:modified

B. dbt run --state ./target/previous --select state:modified --full-refresh

C. dbt run --state ./target/previous --select state:modified+

D. dbt run --select state:modified --state ./target/previous --exclude B

Solution

1. Step 1: Understand the '+' operator in selection

   The '+' after state:modified selects modified models plus their dependents.

2. Step 2: Match command to requirement

   dbt run --state ./target/previous --select state:modified+ uses state:modified+ with correct --state path, running 'B' and its dependents.

3. Step 3: Evaluate other options

   dbt run --state ./target/previous --select state:modified runs only modified models without dependents; C adds unnecessary full-refresh; D excludes 'B' incorrectly.

4. Final Answer:

   dbt run --state ./target/previous --select state:modified+ -> Option C

5. Quick Check:

   Modified plus dependents run [OK]

Hint: Add '+' to include dependents of modified models [OK]

Common Mistakes:

• Not including dependents with '+'
• Using --full-refresh unnecessarily
• Excluding modified models by mistake