TF-004 Understand Terraform's purpose Practice Test 2 — 15 Questions

Question 1

A team member runs terraform apply with the configuration shown in the exhibit. The apply succeeds, but the output of the local-exec provisioner shows an empty string for the public IP address. What is the most likely cause?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

The aws_instance resource does not have a public IP assigned because it is launched in a default VPC without auto-assign public IP, and no Elastic IP is attached.. The `local-exec` provisioner runs on the machine executing Terraform, not on the AWS instance itself. If the instance is launched in a default VPC without `auto-assign public IP` enabled and no Elastic IP is attached, the `self.public_ip` attribute will be an empty string. The provisioner then outputs that empty string, as it simply reads the attribute value from the resource state.

Answer

There is a dependency cycle between the aws_instance and null_resource causing Terraform to skip the provisioner.

Answer

The local-exec provisioner only runs during terraform destroy, not during apply.

Answer

The provisioner cannot access the aws_instance resource's attributes because it is defined in a separate resource block.

Question 2

Which of the following accurately describe core purposes and benefits of using Terraform in a cloud infrastructure environment? Choose all that apply. (There are four correct answers.)

Accepted Answer

Facilitates collaboration through remote state backends and version-controlled configuration files.. Terraform's core purpose is to enable Infrastructure as Code (IaC) by allowing users to define cloud resources in declarative HCL (HashiCorp Configuration Language) files. It automates provisioning and lifecycle management across multiple providers (AWS, Azure, GCP, etc.) using a single workflow. State management is fundamental: Terraform maintains a state file to track real-world resources, enabling incremental planning and safe updates. Collaboration is facilitated by storing state remotely (e.g., in S3, Terraform Cloud) and using version control for configuration files, ensuring team consistency and auditability.

Answer

Provides a built-in drift detection mechanism that automatically reverts unauthorized manual changes to infrastructure.

Answer

Generates real-time billing and cost optimization recommendations for deployed resources.

Question 3

Drag and drop the steps to destroy infrastructure managed by Terraform in the correct order.

Accepted Answer

Run terraform plan -destroy, then run terraform destroy with confirmation.. Destroy plan previews removal; destroy command with confirmation tears down infrastructure.

Answer

Run terraform destroy, then run terraform plan -destroy.

Answer

Run terraform apply, then run terraform destroy.

Answer

Run terraform plan, then run terraform destroy.

Question 4

Match each Terraform error code to its meaning.

Accepted Answer

Exit code 0: Command succeeded without any error. Terraform exit codes indicate the result of command execution. Exit code 0 means success, 1 means general error, and 2 means usage error. The other codes are not defined by Terraform.

Answer

Exit code 0: General error during execution

Answer

Exit code 2: Command succeeded without any error

Answer

Exit code 3: State lock error

Question 5

A company wants to manage both on-premises and cloud infrastructure with a single tool. Which feature of Terraform makes this possible?

Accepted Answer

Provider plugins. Terraform uses provider plugins as the abstraction layer that allows it to interact with different infrastructure platforms. Each provider plugin (e.g., AWS, Azure, vSphere) implements the necessary API calls to manage resources on that platform. By using multiple provider plugins in the same configuration, Terraform can manage both on-premises infrastructure (e.g., VMware vSphere) and cloud infrastructure (e.g., AWS EC2) with a single tool.

Answer

State files

Answer

Provisioners

Answer

Workspaces

Question 6

During a terraform apply, the state file becomes corrupted. What is the recommended recovery method?

Accepted Answer

Restore from backup. The recommended recovery method for a corrupted Terraform state file is to restore it from a known good backup. Terraform does not have built-in corruption repair mechanisms, so maintaining regular backups of the state file (e.g., using remote backends with versioning like S3 versioning or Terraform Cloud) is the standard operational practice. Restoring from backup ensures the state accurately reflects the real-world infrastructure without manual intervention.

Answer

Re-run apply

Answer

Delete the state and re-import all resources

Answer

Use terraform state pull

Question 7

Which Terraform feature allows managing multiple separate sets of infrastructure from the same configuration?

Accepted Answer

Workspaces. Workspaces allow you to manage multiple distinct sets of infrastructure resources from the same Terraform configuration by maintaining separate state files. Each workspace isolates its own state data, enabling you to deploy, modify, or destroy infrastructure for different environments (e.g., dev, staging, prod) without interfering with each other. This is the native Terraform feature designed specifically for managing multiple separate instances of infrastructure from a single configuration.

Answer

Count

Answer

Providers

Answer

For_each

Question 8

What does Terraform's declarative model mean for infrastructure changes?

Accepted Answer

You describe the desired end state. Terraform's declarative model means you describe the desired end state of your infrastructure in configuration files, and Terraform determines the actions needed to reach that state. You do not specify the sequence of API calls or the order of resource creation; Terraform builds a dependency graph and executes operations in the correct order automatically. This contrasts with imperative scripting, where you must define each step explicitly.

Answer

You manually approve each step

Answer

You must specify the order of creation

Answer

You write scripts to create resources

Question 9

A company wants to ensure that Terraform configurations are consistent across teams. What practice should they adopt?

Accepted Answer

Use modules from a registry. Using modules from a registry (Option B) is the correct practice because modules encapsulate reusable, version-controlled infrastructure configurations that enforce consistency across teams. By referencing a shared registry, teams can standardize on approved module versions, reducing drift and ensuring compliance with organizational policies. This approach aligns with Terraform's best practices for code reuse and collaboration.

Answer

Write all code in a single file

Answer

Use provisioners extensively

Answer

Avoid using variables

Question 10

Which Terraform feature helps manage dependencies between resources?

Accepted Answer

depends_on. The depends_on meta-argument in Terraform explicitly defines dependencies between resources, ensuring that one resource is created only after another. This is useful when Terraform cannot infer the dependency from expressions.

Answer

data source

Answer

output

Answer

provisioner

Question 11

What is the primary purpose of Terraform's state file?

Accepted Answer

Map configurations to real-world resources. Terraform's state file is the authoritative record that maps resources declared in configuration to the actual real-world objects (e.g., AWS instance IDs, Azure resource IDs). Without it, Terraform cannot know what it has already created, what to update, or what to destroy.

Answer

Provide a GUI

Answer

Execute scripts

Answer

Store secrets

Question 12

A DevOps engineer needs to integrate Terraform with a CI/CD pipeline. What is a common practice?

Accepted Answer

Run terraform plan in a pull request. Running `terraform plan` in a pull request is a common practice because it allows the team to review the proposed infrastructure changes before they are applied. This integrates Terraform's safety mechanism into the CI/CD pipeline, ensuring that any destructive or unexpected modifications are caught during code review, not during deployment. It aligns with the principle of infrastructure as code (IaC) where changes are validated and approved through the same workflow as application code.

Answer

Avoid using variables

Answer

Use -auto-approve always

Answer

Store state in a local file

Question 13

A company has a Terraform configuration that works correctly in us-east-1 but fails in us-west-2 due to resource availability. What is the best way to handle this?

Accepted Answer

Use data sources. Data sources allow Terraform to query the target region for available resources at plan time, enabling dynamic configuration that adapts to regional differences. By using a data source to filter or validate resource availability, the configuration can fail gracefully or select an alternative resource without hardcoding region-specific values.

Answer

Hardcode region in resources

Answer

Use count

Answer

Use provisioners

Question 14

Which TWO are benefits of Terraform's immutable infrastructure approach?

Accepted Answer

Easier rollbacks. Terraform's immutable infrastructure approach replaces entire resources rather than modifying them in-place. This means the previous version of the infrastructure is preserved as a state snapshot, allowing you to roll back by simply reapplying the prior configuration from your version control system. This eliminates the complexity of tracking incremental changes and ensures a clean, predictable rollback process.

Answer

Better performance

Answer

Faster provisioning

Answer

Lower cost

Question 15

Which THREE are considered Terraform's best practices?

Accepted Answer

Use variables to parameterize configurations. A is correct because using variables to parameterize configurations is a core Terraform best practice that enables reusability, flexibility, and separation of concerns. By defining input variables in `variables.tf` and passing values via `terraform.tfvars` or environment variables, you avoid hardcoding values like instance types or region names, making configurations portable across environments (dev, staging, prod). This aligns with Terraform's principle of writing infrastructure as code that is modular and maintainable.

Answer

Use latest version of all modules

Answer

Use provisioners for all software installs