AWS provider Resource Lifecycle Management — Timed 15 Questions

Question 1

You need to ensure that an AWS Auto Scaling Group maintains capacity during a configuration change that requires a new launch template. Which lifecycle meta-argument should you use?

Accepted Answer

create_before_destroy = true. The create_before_destroy meta-argument ensures that the new resource is created before the old one is destroyed, preventing downtime during replacement.

Answer

replace_triggered_by

Answer

ignore_changes

Answer

prevent_destroy

Question 2

When using 'create_before_destroy', what is a common side effect that may cause the plan to fail?

Accepted Answer

Resource naming collisions.. If the resource has a unique name or specific constraints (like an S3 bucket name), creating a new instance before destroying the old one will cause a naming collision.

Answer

Terraform will delete the state file.

Answer

Provider credentials will expire.

Answer

All other resources will be destroyed.

Question 3

You are managing a production database instance. You want to ensure that if a developer accidentally removes the resource block from the Terraform configuration, Terraform will refuse to destroy the database. How do you implement this?

Accepted Answer

Set prevent_destroy = true in the lifecycle block.. The prevent_destroy lifecycle meta-argument is a safety measure that causes a plan to fail if a resource is marked for deletion.

Answer

Set create_before_destroy = false.

Answer

Use the ignore_changes meta-argument for the lifecycle block.

Answer

Configure a provider-level block to disable deletions.

Question 4

Which command is used to move a resource from one state file to another, commonly used when refactoring modules?

Accepted Answer

terraform state mv. terraform state mv is the standard tool for moving resources between states or renaming them in the state file.

Answer

terraform migrate

Answer

terraform plan -refactor

Answer

terraform refresh

Question 5

You have an AWS Lambda function that should be replaced whenever the source code S3 object changes. How do you trigger this replacement specifically based on the S3 object key change?

Accepted Answer

Use replace_triggered_by = [aws_s3_object.lambda_code.key]. The replace_triggered_by meta-argument allows forcing a resource to be replaced when another specified resource or attribute changes.

Answer

Use lifecycle { force_replace = true }

Answer

Use create_before_destroy.

Answer

Use ignore_changes = [source_code_hash]

Question 6

A resource has an attribute 'tags' that is managed by an external script. You want Terraform to ignore any changes made to 'tags' after the initial creation. How should you configure the 'lifecycle' block?

Accepted Answer

ignore_changes = [tags]. The ignore_changes meta-argument allows you to specify a list of attributes that Terraform should skip during the refresh and plan phases.

Answer

lifecycle { tags = ignore }

Answer

prevent_destroy = [tags]

Answer

ignore_changes = [all]

Question 7

You have defined a resource and set 'prevent_destroy = true'. If you perform a 'terraform destroy', what will happen?

Accepted Answer

Terraform will return an error and abort the destroy operation.. Terraform will return an error stating that the resource cannot be destroyed due to the lifecycle rule, and the operation will be aborted.

Answer

Terraform will destroy all resources except the one with the rule.

Answer

Terraform will ignore the rule and destroy the resource anyway.

Answer

Terraform will prompt for confirmation twice.

Question 8

You want to remove a resource from Terraform management without destroying the actual AWS resource. Which command accomplishes this?

Accepted Answer

terraform state rm. terraform state rm removes the resource from the state file, effectively 'unmanaging' it so it will not be destroyed on the next apply.

Answer

terraform destroy -target

Answer

terraform untrack

Answer

terraform apply -ignore

Question 9

Where are lifecycle meta-arguments placed within a Terraform configuration?

Accepted Answer

Inside the resource block, within a 'lifecycle' block.. Lifecycle meta-arguments must be placed inside a 'lifecycle' block within the resource block.

Answer

At the root of the configuration file.

Answer

Inside the module block.

Answer

Inside the provider block.

Question 10

Which of the following is a valid lifecycle meta-argument in Terraform?

Accepted Answer

create_before_destroy. create_before_destroy is a standard, widely used lifecycle meta-argument.

Answer

delete_on_success

Answer

wait_for_completion

Answer

create_after_update

Question 11

What is the purpose of the 'terraform state refresh' command?

Accepted Answer

To update the state file with current real-world resource attributes.. This command reconciles the state file with the actual infrastructure in the real world to detect drift.

Answer

To delete orphaned resources.

Answer

To apply changes to the cloud provider.

Answer

To upgrade the Terraform version.

Question 12

If you use 'ignore_changes = [tags]', and you manually change the tags in the AWS Console, what will happen during the next 'terraform plan'?

Accepted Answer

Terraform will ignore the difference and perform no action on the tags.. Terraform will see the difference, but because 'tags' is in the ignore list, it will not propose a plan to revert those changes.

Answer

Terraform will plan to revert the tags to the configuration state.

Answer

Terraform will fail with an attribute mismatch error.

Answer

Terraform will update the state file to match the console tags.

Question 13

You need to ensure that a resource is always recreated if an associated data source value changes. Which meta-argument supports this?

Accepted Answer

replace_triggered_by. The replace_triggered_by meta-argument is specifically designed to force replacement when other resources or data sources change.

Answer

create_before_destroy

Answer

lifecycle_hooks

Answer

prevent_destroy

Question 14

What happens if you set 'ignore_changes = all' in a resource lifecycle block?

Accepted Answer

It causes Terraform to ignore all changes to the resource attributes.. 'all' is a special keyword in ignore_changes that instructs Terraform to ignore all attribute changes for that resource.

Answer

It disables the prevent_destroy rule.

Answer

It ignores the resource existence entirely.

Answer

It causes a syntax error.

Question 15

You have two resources, A and B. You want B to be replaced whenever A is updated. How do you configure B?

Accepted Answer

In resource B, set lifecycle { replace_triggered_by = [resource_a] }. Using replace_triggered_by in B's lifecycle block, referencing resource A, forces the replacement of B when A changes.

Answer

In resource B, set lifecycle { create_before_destroy = [resource_a] }

Answer

In resource A, set lifecycle { triggers = [resource_b] }

Answer

In resource B, set depends_on = [resource_a]