Drift detection in CI/CD in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is drift detection in Terraform CI/CD pipelines?

In a Terraform-based CI/CD pipeline, what does drift detection mean?

A Detecting changes in infrastructure that were made outside of Terraform management

B Automatically applying all pending Terraform changes without review

C Running Terraform plan only when code changes are pushed

D Backing up Terraform state files to a remote location

💡 Hint

Think about what happens if someone changes the cloud setup manually, not through Terraform.

Drift detection means identifying when the real infrastructure differs from what Terraform expects, usually because of manual changes outside Terraform.

💻 Command Output

intermediate

Output of Terraform plan detecting drift

What output will Terraform show if the actual infrastructure has drifted from the last applied state?

Terraform

terraform plan

A Shows 'No changes. Infrastructure is up-to-date.'

B Shows a list of changes Terraform will apply to fix the drift

C Throws an error about missing state file

D Automatically applies changes without confirmation

💡 Hint

Terraform plan shows what it will do to match the real infrastructure to the code.

If drift exists, terraform plan will show the changes needed to bring infrastructure back in sync with the code.

🔀 Workflow

advanced

Best place to add drift detection in CI/CD pipeline

Where in a CI/CD pipeline should you add drift detection to catch manual changes early?

A Before applying changes, run 'terraform plan' to detect drift

B Only after applying changes, run 'terraform apply' without plan

C Skip drift detection and rely on manual audits

D Run drift detection only on production environment after deployment

💡 Hint

Think about catching problems before making new changes.

Running 'terraform plan' before applying changes helps detect drift early and prevents applying unexpected changes.

❓ Troubleshoot

advanced

Why does Terraform plan show no changes despite drift?

You suspect drift in your infrastructure, but running terraform plan shows no changes. What could cause this?

A Terraform does not support drift detection

B Terraform automatically fixed the drift before plan

C Terraform state file is outdated or corrupted

D The cloud provider API is down

💡 Hint

Think about what Terraform uses to compare infrastructure state.

If the state file is outdated or corrupted, Terraform cannot detect drift correctly and may show no changes.

✅ Best Practice

expert

Automating drift detection in multi-environment CI/CD

In a multi-environment setup (dev, staging, prod), what is the best practice to automate drift detection?

A Ignore drift detection in non-production environments

B Only run drift detection manually when issues are reported

C Run 'terraform apply' daily to force sync all environments

D Schedule regular 'terraform plan' runs with state refresh for each environment and alert on drift

💡 Hint

Think about proactive monitoring and alerting.

Regular automated 'terraform plan' runs with state refresh help detect drift early and alert teams to fix it before problems grow.

Practice

1. What is the main purpose of drift detection in a Terraform CI/CD pipeline?

easy

A. To find differences between the Terraform code and the actual infrastructure

B. To speed up the deployment process by skipping validation

C. To automatically delete unused resources without approval

D. To generate documentation for the infrastructure

Solution

1. Step 1: Understand drift detection concept

   Drift detection compares the current real infrastructure state with the Terraform code to find differences.

2. Step 2: Identify the purpose in CI/CD

   In CI/CD, drift detection helps catch unexpected changes before applying new updates.

3. Final Answer:

   To find differences between the Terraform code and the actual infrastructure -> Option A

4. Quick Check:

   Drift detection = find differences [OK]

Hint: Drift detection = spot differences before apply [OK]

Common Mistakes:

• Thinking drift detection speeds deployment
• Assuming it deletes resources automatically
• Confusing it with documentation generation

2. Which Terraform command is commonly used in CI/CD pipelines to detect drift before applying changes?

easy

A. terraform plan

B. terraform apply

C. terraform init

D. terraform destroy

Solution

1. Step 1: Recall Terraform commands

   terraform plan shows the changes Terraform will make without applying them.

2. Step 2: Identify drift detection command

   terraform plan detects differences (drift) between code and real infrastructure before apply.

3. Final Answer:

   terraform plan -> Option A

4. Quick Check:

   Detect drift = terraform plan [OK]

Hint: Use terraform plan to preview changes [OK]

Common Mistakes:

• Using terraform apply which changes infrastructure
• Confusing terraform init with drift detection
• Using terraform destroy which deletes resources

3. Given the following Terraform plan output snippet in a CI/CD pipeline:

  # aws_instance.example will be updated in-place
  ~ tags = {
      - "Environment" = "dev"
      + "Environment" = "prod"
    }

What does this output indicate about drift?

medium

A. Terraform will ignore the tag change

B. The instance will be destroyed and recreated

C. No drift is detected; tags remain unchanged

D. The tag "Environment" has drifted from "dev" to "prod" and will be updated

Solution

1. Step 1: Analyze the plan output

   The '~' symbol means in-place update. The tag "Environment" changes from "dev" to "prod".

2. Step 2: Understand drift implication

   This shows drift: the real infrastructure tag differs from code and will be updated.

3. Final Answer:

   The tag "Environment" has drifted from "dev" to "prod" and will be updated -> Option D

4. Quick Check:

   ~ means update tag from dev to prod [OK]

Hint: Look for ~ symbol to spot in-place updates [OK]

Common Mistakes:

• Thinking resource will be destroyed instead of updated
• Ignoring tag changes as no drift
• Assuming Terraform ignores tag differences

4. You run terraform plan in your CI/CD pipeline but it does not detect drift even though manual changes were made outside Terraform. What is the most likely cause?

medium

A. Terraform automatically ignores manual changes

B. You forgot to run terraform apply first

C. Terraform state file is outdated or corrupted

D. The provider plugin is missing

Solution

1. Step 1: Understand drift detection dependency

   Terraform relies on the state file to compare real infrastructure with code.

2. Step 2: Identify cause of missed drift

   If the state file is outdated or corrupted, Terraform cannot detect manual changes (drift).

3. Final Answer:

   Terraform state file is outdated or corrupted -> Option C

4. Quick Check:

   State file outdated = missed drift detection [OK]

Hint: Check state file freshness if drift not detected [OK]

Common Mistakes:

• Assuming terraform apply affects drift detection
• Believing Terraform ignores manual changes by design
• Thinking missing provider causes drift detection failure

5. In a CI/CD pipeline, you want to automatically detect drift and fail the pipeline if any drift is found before applying changes. Which approach best achieves this?

hard

A. Run terraform apply directly and rely on errors to detect drift

B. Run terraform plan and parse its output to detect changes, then fail if changes exist

C. Skip drift detection and always apply changes

D. Manually check infrastructure outside the pipeline

Solution

1. Step 1: Understand CI/CD drift detection goal

   The goal is to detect drift and fail early before applying changes.

2. Step 2: Choose correct command and method

   terraform plan shows drift without applying; parsing its output allows pipeline to fail if drift exists.

3. Step 3: Evaluate other options

   Applying directly risks unwanted changes; manual checks are slow; skipping detection is unsafe.

4. Final Answer:

   Run terraform plan and parse its output to detect changes, then fail if changes exist -> Option B

5. Quick Check:

   Plan + parse output = fail on drift [OK]

Hint: Use terraform plan output to gate pipeline success [OK]

Common Mistakes:

• Applying without checking drift first
• Relying on manual checks in automated pipelines
• Ignoring drift detection to speed up deploys