Why meta-arguments control resource behavior in Terraform - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does the 'count' meta-argument affect resource creation?

Consider a Terraform resource with the meta-argument count = 3. What is the effect of this meta-argument on the resource behavior?

A Terraform duplicates the resource configuration three times but creates only one instance.

B Terraform creates one resource but applies three different configurations to it.

C Terraform creates a resource only if the count is greater than zero, otherwise skips it.

D Terraform creates exactly three instances of the resource.

💡 Hint

Think about how repeating a resource multiple times works in Terraform.

The count meta-argument tells Terraform to create multiple separate instances of the resource, each with the same configuration. So, count = 3 means three identical resources are created.

❓ Architecture

intermediate

What does the 'depends_on' meta-argument control in Terraform?

In Terraform, the depends_on meta-argument is used in a resource block. What behavior does it control?

A It forces Terraform to create the resource only after the specified dependencies are created.

B It merges the resource configuration with the dependencies.

C It automatically deletes the resource if any dependency is removed.

D It duplicates the resource for each dependency listed.

💡 Hint

Think about how Terraform manages the order of resource creation.

The depends_on meta-argument explicitly tells Terraform to wait until the listed resources are created before creating this resource, ensuring correct order.

❓ service_behavior

advanced

What is the effect of the 'lifecycle' meta-argument with 'prevent_destroy' set to true?

Given a Terraform resource with the following snippet:

lifecycle {
  prevent_destroy = true
}

What behavior does this enforce when you try to destroy the resource?

A Terraform ignores the destroy command and continues without error.

B Terraform will destroy the resource but recreate it immediately.

C Terraform will block the destruction of the resource and show an error.

D Terraform converts the destroy command into an update.

💡 Hint

Consider what 'prevent_destroy' means literally.

Setting prevent_destroy = true in the lifecycle meta-argument stops Terraform from destroying the resource. If a destroy is attempted, Terraform raises an error to protect the resource.

❓ security

advanced

How does the 'ignore_changes' lifecycle meta-argument affect resource updates?

In Terraform, if a resource has:

lifecycle {
  ignore_changes = ["tags"]
}

What happens when the tags are changed outside Terraform?

A Terraform ignores changes to tags and does not try to update them.

B Terraform overwrites the tags with the configuration on every apply.

C Terraform throws an error if tags are changed outside Terraform.

D Terraform deletes the resource if tags differ from the configuration.

💡 Hint

Think about what 'ignore_changes' means for specific attributes.

The ignore_changes lifecycle argument tells Terraform to skip updating specified attributes, even if they differ from the configuration. This is useful for attributes changed outside Terraform.

✅ Best Practice

expert

Why should you avoid using 'count' with complex resource dependencies?

When using the count meta-argument on resources that have complex dependencies, what is a common issue that can arise?

A It automatically merges all resources into one, losing individual control.

B It can cause unpredictable resource creation order leading to dependency errors.

C It disables the use of 'depends_on' meta-argument completely.

D It causes Terraform to ignore lifecycle meta-arguments.

💡 Hint

Think about how Terraform handles multiple instances and dependencies.

Using count with complex dependencies can make it hard for Terraform to determine the correct order of resource creation, causing errors or unexpected behavior.