AWS provider Resource Lifecycle Management Practice Test 3 — 15 Questions

Question 1

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 moves a resource from one state address to another, and when used with different state files (via -state and -state-out), it can move resources between state files. This is the standard command for refactoring modules without destroying and recreating resources. It updates the state mapping so Terraform associates the existing resource with the new address.

Answer

terraform migrate

Answer

terraform plan -refactor

Answer

terraform refresh

Question 2

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' argument within a lifecycle block tells Terraform to ignore changes to the specified attributes after resource creation. Setting 'ignore_changes = [tags]' ensures that any external modifications to the tags attribute are not detected as drift, preventing Terraform from reverting them. This is the correct way to handle attributes managed outside of Terraform.

Answer

lifecycle { tags = ignore }

Answer

prevent_destroy = [tags]

Answer

ignore_changes = [all]

Question 3

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.. When a resource has `prevent_destroy = true` in its lifecycle block, Terraform treats any plan that would destroy that resource as invalid. During `terraform destroy`, Terraform first generates a destroy plan; because that plan includes deleting the protected resource, Terraform immediately returns an error and aborts the entire operation before any resource is destroyed. This is a safety mechanism to prevent accidental deletion of critical infrastructure.

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 4

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

Accepted Answer

terraform state rm. The `terraform state rm` command removes a resource from the Terraform state file without touching the actual infrastructure. This is the correct way to 'orphan' a resource so Terraform no longer manages it, while the real AWS resource continues to exist. It is commonly used when migrating resources to another state file or handing them off to manual management.

Answer

terraform destroy -target

Answer

terraform untrack

Answer

terraform apply -ignore

Question 5

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

Accepted Answer

Inside the resource block, within a 'lifecycle' block.. Lifecycle meta-arguments are used to customize the behavior of a specific resource, such as preventing its destruction or ignoring changes to certain attributes. They are defined within a nested 'lifecycle' block inside the resource block, as they directly modify that resource's lifecycle. This placement ensures the arguments apply only to that resource, not globally or to modules/providers.

Answer

At the root of the configuration file.

Answer

Inside the module block.

Answer

Inside the provider block.

Question 6

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

Accepted Answer

create_before_destroy. create_before_destroy is a valid lifecycle meta-argument in Terraform, used to ensure that a new resource is created before the old one is destroyed during replacement. This is one of the four supported lifecycle meta-arguments: create_before_destroy, prevent_destroy, ignore_changes, and replace_triggered_by. The other options are not valid Terraform lifecycle meta-arguments.

Answer

delete_on_success

Answer

wait_for_completion

Answer

create_after_update

Question 7

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.. The `ignore_changes` lifecycle meta-argument tells Terraform to disregard differences between the desired configuration and the actual remote state for the specified attributes. When `ignore_changes = [tags]` is set, Terraform will not plan any changes to the `tags` attribute even if the real-world resource has been modified outside of Terraform. Therefore, during the next `terraform plan`, Terraform will ignore the tag differences and perform no action on the tags.

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 8

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 forces Terraform to destroy and recreate the resource whenever any of the referenced attributes or resources change, including data source values. It is designed exactly for the scenario where a resource must be replaced based on an external or computed value rather than a direct attribute reference. When the referenced value changes between plans, Terraform marks the resource for replacement.

Answer

create_before_destroy

Answer

lifecycle_hooks

Answer

prevent_destroy

Question 9

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.. Setting ignore_changes = all in a lifecycle block tells Terraform to ignore all attribute changes for that resource, so drift or configuration changes to attributes will not trigger updates. Terraform still manages the resource's existence, creating or destroying it as needed, but it will not modify attributes. This is useful for resources managed partly outside Terraform.

Answer

It disables the prevent_destroy rule.

Answer

It ignores the resource existence entirely.

Answer

It causes a syntax error.

Question 10

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] }. The replace_triggered_by meta-argument in resource B's lifecycle block specifies that B should be replaced when resource A changes. This directly ties B's replacement to A's updates, ensuring B is recreated whenever A is updated.

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]

Question 11

Why might someone use 'prevent_destroy = true' on a database resource while allowing it on smaller web server instances?

Accepted Answer

To protect critical data from accidental deletion.. prevent_destroy = true is used to protect resources whose loss would be catastrophic or unrecoverable, such as databases containing critical data. Web server instances are typically stateless and easily recreated, so the protection is unnecessary there — making option B correct.

Answer

To increase the speed of the destroy process.

Answer

To ensure create_before_destroy works.

Answer

To satisfy the AWS provider requirements.

Question 12

When refactoring code, you rename a resource in your configuration. What happens if you run 'terraform plan' without updating the state?

Accepted Answer

Terraform will propose destroying the old resource and creating a new one.. Renaming a resource in configuration changes its address, so Terraform sees the old address as removed and the new address as added, resulting in a plan to destroy the old resource and create a new one. State still maps the old address to the real resource, so Terraform cannot associate the new name with the existing object. This is why terraform state mv is used to rename without destruction.

Answer

Terraform will do nothing.

Answer

Terraform will automatically rename it in the state.

Answer

Terraform will throw an error and stop.

Question 13

Which file stores the mapping between your Terraform configuration and the real-world infrastructure?

Accepted Answer

terraform.tfstate. The `terraform.tfstate` file is Terraform's state file, which stores the mapping between resources declared in configuration and the real-world infrastructure objects, including their attributes and dependencies. It is the source of truth Terraform uses to plan changes and detect drift.

Answer

terraform.tfvars

Answer

provider.tf

Answer

backend.tf

Question 14

What is the primary risk of relying solely on 'create_before_destroy' without considering dependency chains?

Accepted Answer

It can lead to resource contention or naming conflicts.. 'create_before_destroy' makes Terraform create the replacement resource before destroying the old one. When resources have unique names, fixed IPs, or other globally unique identifiers, the new resource cannot be created while the old one still exists, causing naming conflicts or resource contention. This is the primary risk when dependency chains are not carefully considered.

Answer

It causes infinite loops in Terraform.

Answer

It increases the cost of the plan.

Answer

It creates a security risk.

Question 15

When a resource is marked as 'tainted', what is the expected outcome of the next 'terraform apply'?

Accepted Answer

It is destroyed and recreated.. A tainted resource is one Terraform has marked as degraded or partially created, so the next 'terraform apply' will destroy the existing object and create a fresh replacement. This is the standard recovery mechanism when a resource is in an unhealthy or unknown state but you want to keep it managed by Terraform.

Answer

It is ignored.

Answer

It is removed from the state file.

Answer

It is updated in place.