Resource Lifecycle Management practice questions

replace_triggered_by

Why wrong: This forces replacement based on other resource changes, not ordering.

ignore_changes

Why wrong: This prevents Terraform from reacting to changes in specified attributes.

prevent_destroy

Why wrong: This prevents the resource from being deleted, but does not dictate order.

Terraform will delete the state file.

Why wrong: Terraform does not delete state files during creation.

Provider credentials will expire.

Why wrong: This is unrelated to the create_before_destroy lifecycle.

All other resources will be destroyed.

Why wrong: Only the lifecycle-managed resource is affected.

Set create_before_destroy = false.

Why wrong: This does not prevent deletion.

Use the ignore_changes meta-argument for the lifecycle block.

Why wrong: This ignores attribute changes, not deletion events.

Configure a provider-level block to disable deletions.

Why wrong: Provider blocks do not support global deletion prevention in this manner.

terraform migrate

Why wrong: No such command exists in the core Terraform CLI.

terraform plan -refactor

Why wrong: This flag does not exist.

terraform refresh

Why wrong: This synchronizes state with real-world infrastructure.

Use lifecycle { force_replace = true }

Why wrong: This is not a valid lifecycle meta-argument.

Use create_before_destroy.

Why wrong: This only controls the timing, not the trigger for replacement.

Use ignore_changes = [source_code_hash]

Why wrong: This would prevent Terraform from detecting code changes.

lifecycle { tags = ignore }

Why wrong: This is invalid syntax.

prevent_destroy = [tags]

Why wrong: prevent_destroy is a boolean, not a list.

ignore_changes = [all]

Why wrong: 'all' is not a valid syntax for ignore_changes.

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

Why wrong: Terraform stops the entire operation when a block occurs.

Terraform will ignore the rule and destroy the resource anyway.

Why wrong: The rule is enforced as a safety barrier.

Terraform will prompt for confirmation twice.

Why wrong: The rule is non-negotiable via standard destroy commands.

terraform destroy -target

Why wrong: This would destroy the resource.

terraform untrack

Why wrong: This command does not exist.

terraform apply -ignore

Why wrong: No such flag exists.

At the root of the configuration file.

Why wrong: This would result in a syntax error.

Inside the module block.

Why wrong: Modules do not have lifecycle meta-arguments.

Inside the provider block.

Why wrong: Providers do not accept lifecycle blocks.

delete_on_success

Why wrong: This is not a valid meta-argument.

wait_for_completion

Why wrong: This is not a meta-argument, though some resources have such parameters.

create_after_update

Why wrong: This is not a valid meta-argument.

To delete orphaned resources.

Why wrong: Terraform doesn't have a 'refresh to delete' command.

To apply changes to the cloud provider.

Why wrong: Use terraform apply.

To upgrade the Terraform version.

Why wrong: Use terraform init -upgrade.

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

Why wrong: The ignore_changes list explicitly prevents this.

Terraform will fail with an attribute mismatch error.

Why wrong: Terraform does not fail on ignored attributes.

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

Why wrong: Terraform updates state based on the code, not the drift.

create_before_destroy

Why wrong: This manages the ordering.

lifecycle_hooks

Why wrong: This is not a valid meta-argument.

prevent_destroy

Why wrong: This prevents destruction.

It disables the prevent_destroy rule.

Why wrong: These are two separate settings.

It ignores the resource existence entirely.

Why wrong: Terraform still manages the resource lifecycle.

It causes a syntax error.

Why wrong: 'all' is a valid keyword in Terraform.

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

Why wrong: create_before_destroy does not accept resource references.

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

Why wrong: This is not valid syntax.

In resource B, set depends_on = [resource_a]

Why wrong: depends_on manages ordering, not lifecycle replacement.

To increase the speed of the destroy process.

Why wrong: It does not impact speed.

To ensure create_before_destroy works.

Why wrong: They are distinct features.

To satisfy the AWS provider requirements.

Why wrong: The provider does not mandate this.

Terraform will do nothing.

Why wrong: Terraform will detect a change and act accordingly.

Terraform will automatically rename it in the state.

Why wrong: Terraform does not auto-detect renames.

Terraform will throw an error and stop.

Why wrong: Terraform will proceed with the plan.

terraform.tfvars

Why wrong: This stores input variables.

provider.tf

Why wrong: This configures the provider.

backend.tf

Why wrong: This configures the state backend.

ignore_changes = [ingress[0].cidr_blocks]

Why wrong: This is only valid if you define the path correctly; the list element notation is primary.

ignore_changes = [ingress.0]

Why wrong: This syntax is incorrect.

ignore_changes = { ingress = [0] }

Why wrong: This is invalid syntax.

It causes infinite loops in Terraform.

Why wrong: It does not cause infinite loops.

It increases the cost of the plan.

Why wrong: Cost is not directly related to this lifecycle meta-argument.

It creates a security risk.

Why wrong: It is not a security feature.