Import block syntax (Terraform 1.5+) - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the purpose of the import block in Terraform 1.5+

What is the main purpose of the import block introduced in Terraform 1.5+?

A To automatically create new resources in the cloud provider without any configuration.

B To declare resources that Terraform should import into the state during <code>terraform apply</code> without manual CLI commands.

C To remove resources from the Terraform state without deleting them from the cloud provider.

D To define variables that are imported from external files during plan execution.

💡 Hint

Think about how Terraform manages existing resources that were created outside Terraform.

The import block allows Terraform to bring existing infrastructure into its state automatically during terraform apply, avoiding manual import commands.

❓ Configuration

intermediate

Identifying correct import block syntax

Which of the following Terraform snippets correctly uses the import block syntax introduced in Terraform 1.5+ to import an AWS S3 bucket with ID my-bucket?

A

import {
  to = aws_s3_bucket.example
  id = "my-bucket"
}

B

import {
  id = aws_s3_bucket.example
  to = "my-bucket"
}

C

import {
  resource = aws_s3_bucket.example
  id = "my-bucket"
}

D

import {
  id = "my-bucket"
  to = aws_s3_bucket.example
}

💡 Hint

The import block requires id and to attributes. The order matters for clarity.

The correct syntax uses id to specify the resource ID and to to specify the resource address. Option D follows this correctly.

❓ Architecture

advanced

Behavior of import block during terraform apply

What happens when Terraform runs terraform apply with a configuration that includes an import block for a resource that already exists in the cloud provider but is not yet in the Terraform state?

A Terraform imports the resource into the state automatically before applying any changes.

B Terraform ignores the import block and creates a new resource instead.

C Terraform throws an error and stops the apply process.

D Terraform deletes the existing resource and creates a new one.

💡 Hint

Consider how Terraform handles existing resources declared in the import block during apply.

Terraform automatically imports the existing resource into its state during apply, so it can manage it going forward without manual import commands.

❓ security

advanced

Security considerations when using import blocks

Which security risk is most relevant when using Terraform's import block to bring existing cloud resources into state?

A Accidentally importing sensitive resources without proper access controls in Terraform state files.

B Terraform automatically encrypts all imported resource data, so no risks exist.

C Import blocks expose cloud provider credentials in the Terraform configuration files.

D Import blocks delete existing resources during import, causing data loss.

💡 Hint

Think about what information is stored in Terraform state files after import.

Imported resources' details, including sensitive data, are stored in the Terraform state file. If this file is not secured, it can expose sensitive information.

❓ service_behavior

expert

Effect of multiple import blocks for the same resource

Given a Terraform configuration with two import blocks referencing the same resource address but different IDs, what will happen during terraform apply?

A Terraform will ignore the second import block and only import the first resource ID.

B Terraform will import the resource twice, causing duplicate state entries.

C Terraform will raise an error about conflicting import declarations and stop the apply.

D Terraform will merge both IDs and create a new resource combining them.

💡 Hint

Consider how Terraform handles conflicting state imports for the same resource address.

Terraform does not allow multiple import blocks for the same resource address with different IDs. It raises an error to prevent state conflicts.