Scenario practice questions

Which TWO scenarios require the use of the depends_on argument?

Trap 1: When a resource uses the output of another resource in its…

Attribute references create implicit dependencies.

Trap 2: When a resource uses the output of a data source in its arguments.

Data source references create implicit dependencies.

Trap 3: When a resource uses a module output as an input.

Module output references create implicit dependencies.

A
When a resource uses the output of another resource in its arguments.
Why wrong: Attribute references create implicit dependencies.
B
When a provisioner creates resources that other resources depend on.
Terraform cannot track provisioner-side effects.
C
When Terraform cannot automatically infer an implicit dependency.
Explicit depends_on is needed when implicit detection fails.
D
When a resource uses the output of a data source in its arguments.
Why wrong: Data source references create implicit dependencies.
E
When a resource uses a module output as an input.
Why wrong: Module output references create implicit dependencies.

Question 2easymultiple choice

A team uses an S3 backend for Terraform state. During a `terraform apply`, another team member accidentally runs a plan that also modifies the same state. Which feature prevents state corruption in this scenario?

Trap 1: The `-lock=false` flag

This disables locking, which is the opposite of protection.

Trap 2: Terraform Cloud remote operations

Remote operations can help but are not the specific feature for locking.

Trap 3: State versioning in S3

Versioning retains older versions but doesn't prevent concurrent writes.

A
The `-lock=false` flag
Why wrong: This disables locking, which is the opposite of protection.
B
Terraform Cloud remote operations
Why wrong: Remote operations can help but are not the specific feature for locking.
C
State locking via DynamoDB
State locking uses DynamoDB to acquire a lock, preventing multiple operations.
D
State versioning in S3
Why wrong: Versioning retains older versions but doesn't prevent concurrent writes.

Question 3mediummultiple choice

During 'terraform apply', a user receives an error: 'Error: Error creating resource: Resource already exists'. The resource does not appear in the Terraform state. What is the most likely cause?

Trap 1: The state file was migrated from a different backend and the…

State migration would import resources; duplication would cause different errors.

Trap 2: The resource was removed from the configuration but not from state.

That would cause the resource to be destroyed, not created.

Trap 3: The user forgot to run terraform refresh before apply.

Refresh updates state but does not prevent creation of already existing resources.

A
The state file was migrated from a different backend and the resource is duplicated.
Why wrong: State migration would import resources; duplication would cause different errors.
B
The resource was removed from the configuration but not from state.
Why wrong: That would cause the resource to be destroyed, not created.
C
The user forgot to run terraform refresh before apply.
Why wrong: Refresh updates state but does not prevent creation of already existing resources.
D
The resource was manually created outside of Terraform before the apply.
If the resource already exists in the cloud provider but not in state, Terraform will try to create it and fail.

Question 4mediummultiple choice

A company wants to manage its infrastructure as code using Terraform. The team has a mix of on-premises servers and cloud resources in AWS and Azure. Which of the following best describes Terraform's purpose in this scenario?

Trap 1: Terraform is a configuration management tool for installing…

This describes tools like Ansible or Chef, not Terraform.

Trap 2: Terraform is a cloud-specific orchestration tool that only works…

Terraform is multi-cloud, not limited to AWS.

Trap 3: Terraform is a monitoring and logging tool for cloud resources.

Monitoring is handled by other tools like CloudWatch.

A
Terraform is a configuration management tool for installing software on existing servers.
Why wrong: This describes tools like Ansible or Chef, not Terraform.
B
Terraform is a cloud-specific orchestration tool that only works with AWS.
Why wrong: Terraform is multi-cloud, not limited to AWS.
C
Terraform is a monitoring and logging tool for cloud resources.
Why wrong: Monitoring is handled by other tools like CloudWatch.
D
Terraform is an infrastructure-as-code tool for provisioning and managing any infrastructure across multiple providers.
Correctly defines Terraform's purpose.

Question 5mediummulti select

Which TWO scenarios could cause 'terraform plan' to show 'No changes' even though the configuration file was recently modified? (Choose two.)

Trap 1: The resource was manually updated in the cloud provider console.

Manual changes would be detected as drift unless refresh is suppressed.

Trap 2: A new resource block was added.

That would show a change (new resource).

Trap 3: The provider version was changed in the required_providers block.

Provider changes might cause update, not no changes.

A
The user ran 'terraform plan' from a different directory that does not contain the modified configuration.
Plan only reads .tf files from the current directory.
B
A lifecycle block with ignore_changes was applied to the modified attribute.
If the changed attribute is ignored, Terraform will not detect the change.
C
The resource was manually updated in the cloud provider console.
Why wrong: Manual changes would be detected as drift unless refresh is suppressed.
D
A new resource block was added.
Why wrong: That would show a change (new resource).
E
The provider version was changed in the required_providers block.
Why wrong: Provider changes might cause update, not no changes.

Question 6hardmulti select

Which THREE are valid methods to manage Terraform state files? (Choose three.)

Trap 1: terraform state push

This is a command to push state, not a management method.

Trap 2: terraform state mv

This is a command to move items within state, not a method to store state.

A
terraform state push
Why wrong: This is a command to push state, not a management method.
B
Local state file
Store state locally in terraform.tfstate.
C
Terraform Cloud state storage
Terraform Cloud provides managed state storage.
D
terraform state mv
Why wrong: This is a command to move items within state, not a method to store state.
E
Remote backends (e.g., S3, AzureRM, GCS)
Remote backends store state in a shared location.

Question 7hardmultiple choice

A team using a remote S3 backend with DynamoDB locking is experiencing frequent 'Error acquiring the state lock' messages in their CI/CD pipeline. The pipeline runs multiple concurrent jobs for different workspaces. What is the most likely cause and solution?

Trap 1: The DynamoDB table lacks sufficient read/write capacity; increase…

Capacity is rarely the issue for lock timeouts.

Trap 2: The pipeline is running too many jobs; increase the lock wait time.

This only delays failure, not solves contention.

Trap 3: The S3 bucket is not versioned; enable versioning.

Versioning helps with state history, not locking.

A
The DynamoDB table lacks sufficient read/write capacity; increase it.
Why wrong: Capacity is rarely the issue for lock timeouts.
B
The same workspace is being used for concurrent runs; use separate workspaces per environment.
Different workspaces have independent state locks.
C
The pipeline is running too many jobs; increase the lock wait time.
Why wrong: This only delays failure, not solves contention.
D
The S3 bucket is not versioned; enable versioning.
Why wrong: Versioning helps with state history, not locking.

Read the full NAT/PAT explanation →

Question 8hardmultiple choice

Your team is developing a custom module for creating EC2 instances with attached EBS volumes. The module variables are: instance_type (default "t2.micro"), ami (required), volume_size (default 8), volume_type (default "gp2"). Another team uses this module to create a web server. In their root module, they call the module without any explicit instance_type override, but they do set other variables. After applying, the web server is created with instance_type "t2.nano" instead of the expected "t2.micro". They confirm that the module still has the default "t2.micro". What is the most likely explanation?

Trap 1: The module's instance_type variable uses a default that is…

This contradicts the given fact that the module's default is "t2.micro".

Trap 2: The instance_type variable is not defined in the module's…

If the variable is not defined, Terraform would return an error, not silently use a different value.

Trap 3: The module's variable default was changed to "t2.nano" in a new…

The scenario states the module's default is still "t2.micro".

A
The module's instance_type variable uses a default that is "t2.nano" but the root module overrode it with a variable from its own context.
Why wrong: This contradicts the given fact that the module's default is "t2.micro".
B
The instance_type variable is not defined in the module's variables.tf, so it uses a default from the AWS provider.
Why wrong: If the variable is not defined, Terraform would return an error, not silently use a different value.
C
The root module has a variable called instance_type set to "t2.nano" that is being passed to the module.
If the root module defines or inherits an instance_type variable with value "t2.nano", and the module block passes it (e.g., instance_type = var.instance_type), that overrides the module's default.
D
The module's variable default was changed to "t2.nano" in a new version.
Why wrong: The scenario states the module's default is still "t2.micro".