TF-004 Practice Test 26 — 15 Questions

Question 1

What is the purpose of the 'terraform validate' command?

Accepted Answer

To check syntax and internal consistency of configuration files.. The 'terraform validate' command checks the syntax and internal consistency of Terraform configuration files, ensuring that the code is syntactically valid and that references between resources, data sources, and variables are correctly formed. It does not interact with providers or cloud APIs, so it cannot verify credentials or run tests.

Answer

To check the validity of provider credentials.

Answer

To format Terraform configuration files.

Answer

To run unit tests on Terraform modules.

Question 2

Drag and drop the steps to upgrade Terraform providers in a configuration in the correct order.

Accepted Answer

Check current provider versions, then update version constraints, then run terraform init to upgrade, then run terraform plan to validate.. The correct sequence for upgrading Terraform providers is: first check current provider versions to establish a baseline, then update version constraints in the configuration to target the desired versions, then run terraform init to download and install those versions, and finally run terraform plan to verify that the upgrade does not introduce unexpected changes. This order ensures a controlled and validated upgrade process.

Answer

Check current provider versions, then run terraform init to upgrade, then update version constraints, then run terraform plan to validate.

Answer

Update version constraints, then check current provider versions, then run terraform init to upgrade, then run terraform plan to validate.

Answer

Check current provider versions, then update version constraints, then run terraform plan to validate, then run terraform init to upgrade.

Question 3

A Terraform state file is stored in an S3 bucket with versioning enabled. During a deployment, the state file becomes corrupted due to a network error. What is the best way to recover?

Accepted Answer

Restore the previous version of the state file from S3 versioning.. S3 versioning preserves previous versions of objects, including Terraform state files. When the current state file becomes corrupted, you can restore a prior, uncorrupted version directly from the S3 bucket without data loss or manual re-creation of resources. This is the safest and most efficient recovery method.

Answer

Use `terraform state pull` to overwrite the corrupted state.

Answer

Run `terraform import` to import all resources.

Answer

Delete the state file and run `terraform apply` to recreate all resources.

Question 4

You have two modules that create resources in different providers. Module A creates a VPC in AWS, Module B creates a Kubernetes cluster that requires the VPC ID. You want to ensure Module B runs after Module A but avoid hardcoding the VPC ID. Which approach is most appropriate?

Accepted Answer

Output the VPC ID from Module A and pass it as input to Module B.. It establishes an explicit data dependency between modules without hardcoding values. By outputting the VPC ID from Module A and passing it as an input variable to Module B, Terraform's dependency graph automatically ensures Module A is created before Module B, and the VPC ID is dynamically available at plan time.

Answer

Use a data source in Module B to look up the VPC.

Answer

Use terraform graph to order modules.

Answer

Use module dependency via depends_on in the root module.

Question 5

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

Automates the provisioning and lifecycle management of infrastructure across multiple cloud providers.. 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

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

Answer

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

Question 6

A team is migrating from local state to an S3 remote backend. They have existing state files in the working directory. After configuring the backend block and running `terraform init`, what is the correct next step to migrate the existing state?

Accepted Answer

Execute `terraform init` and confirm yes when prompted to copy existing state. When migrating from local to remote state, Terraform automatically prompts to copy existing state during `terraform init` if the backend block changes. Selecting 'yes' will migrate the state. Option A correctly describes this process.

Answer

Run `terraform state push` to upload the local state

Answer

Delete the local state file and run `terraform apply` to recreate

Answer

Manually copy the state file to S3 using AWS CLI

Question 7

Which TWO of the following are valid ways to import existing infrastructure into Terraform management? (Choose TWO.)

Accepted Answer

Use the 'terraform import' command with the resource address and ID.. 'terraform import' is the dedicated command to bring existing infrastructure under Terraform management by associating a real-world resource ID with a resource address in state. Option D is correct because you can manually write configuration that matches the existing resource, then run 'terraform plan' to refresh state and detect any drift, allowing you to adjust the configuration until the plan shows no changes.

Answer

Use 'terraform validate' to automatically import resources.

Answer

Use 'terraform state rm' to remove resources from state, then re-add them.

Answer

Run 'terraform apply' with an empty configuration to detect resources.

Question 8

A team renamed a module from 'module.network' to 'module.vpc' in their configuration. They run 'terraform plan' and see that Terraform wants to destroy the old network resources and create new ones. They want to preserve the existing resources without downtime. What should they do?

Accepted Answer

Add a 'moved' block to the configuration to map the old module address to the new one.. The `moved` block in Terraform allows you to refactor module addresses without destroying and recreating resources. By adding a `moved` block that maps the old module address (`module.network`) to the new one (`module.vpc`), Terraform will automatically update the state to reflect the new address during the next plan and apply, preserving the existing infrastructure and avoiding downtime.

Answer

Use 'terraform state mv' to move the resources to the new module address.

Answer

Update the module source to a new version.

Answer

Accept the destroy and recreate since it's the only way.

Question 9

Which THREE variable declarations are valid in Terraform?

Accepted Answer

variable "enabled" { type = bool default = true }. Terraform variable declarations require a `type` argument and optionally a `default` value. Here, `type = bool` is a valid primitive type, and `default = true` provides a boolean default, which matches the type constraint. This syntax follows Terraform's variable block specification, where the default value must be compatible with the declared type.

Answer

variable "names" { type = list(string) default = "name" }

Answer

variable "count" { type = number default = "1" }

Question 10

A team has a monolithic Terraform configuration managing multiple AWS accounts. They want to decompose it into smaller configurations that can be managed independently. What is the recommended strategy?

Accepted Answer

Split the configuration into separate directories per account and resource type, and use remote state sharing.. Splitting a monolithic Terraform configuration into separate directories per account and resource type, combined with remote state sharing, enables independent management of each configuration while allowing them to consume outputs from one another via `terraform_remote_state` data sources. This approach aligns with the recommended practice of using separate root modules for distinct environments or accounts, avoiding tight coupling and state lock contention.

Answer

Use Terraform workspaces to separate environments within the same configuration.

Answer

Create a single super-module that contains all resources.

Answer

Move everything to Terraform Cloud and use different workspaces.

Question 11

Refer to the exhibit. A developer runs 'terraform plan' and receives the following error: 'Error: InvalidAMIID.NotFound: The image id '[ami-0c55b159cbfafe1f0]' does not exist'. What is the most likely cause?

Accepted Answer

The AMI is not available in the region specified in the provider configuration.. The error 'InvalidAMIID.NotFound' indicates that the specified AMI ID does not exist in the AWS region configured in the Terraform provider block. AMI IDs are region-specific; an AMI available in us-east-1 may not exist in eu-west-2. Terraform validates the AMI against the region's EC2 API, and if the ID is not found, it throws this exact error.

Answer

The 'tags' block is missing a required 'ami' tag.

Answer

The 'ami' argument is misspelled; it should be 'image_id'.

Answer

The AMI ID is malformed; it should start with 'ami-' but the rest is incorrect.

Question 12

A small startup is using Terraform to deploy AWS resources. They have two separate environments: development and production. Currently, they manage two sets of Terraform configuration files in different directories, each with its own state file stored locally. The CEO wants to reduce duplication and simplify management. The team decides to restructure into a single configuration with workspaces. After implementing workspaces, they run `terraform workspace new dev` and `terraform workspace new prod`, then `terraform apply` in the dev workspace. However, when they switch to prod and run `terraform apply`, the plan shows that Terraform wants to recreate all resources instead of managing the existing production resources. What is the most likely reason for this behavior?

Accepted Answer

The team did not migrate the existing production state into the 'prod' workspace.. When the team restructured into a single configuration with workspaces, they created new empty workspaces (`dev` and `prod`) but did not migrate the existing production state file into the `prod` workspace. Terraform workspaces maintain separate state files, so without importing the existing production state into the `prod` workspace, Terraform has no record of the existing production resources and plans to create them from scratch. The `terraform workspace new` command creates a fresh, empty state for that workspace.

Answer

Workspaces cannot be used for different environments; only for temporary feature branches.

Answer

The Terraform configuration uses the same resource names in both workspaces, causing conflicts.

Answer

The team must configure a remote backend for workspaces to function correctly.

Question 13

During 'terraform apply', a user receives an error: 'Error: Error creating resource: Resource already exists'. The resource does not appear in the Terraform state. What is the most likely cause?

Accepted Answer

The resource was manually created outside of Terraform before the apply.. The error 'Resource already exists' indicates that the resource was created outside of Terraform's management (e.g., manually via the cloud console or CLI). Since the resource does not appear in the Terraform state, Terraform attempts to create it during 'terraform apply', but the underlying API rejects the request because the resource already exists in the cloud provider. This is a common state drift scenario where the real-world infrastructure is out of sync with the Terraform state.

Answer

The state file was migrated from a different backend and the resource is duplicated.

Answer

The resource was removed from the configuration but not from state.

Answer

The user forgot to run terraform refresh before apply.

Question 14

Refer to the exhibit. Which change to the configuration would prevent this error in the future?

Accepted Answer

Use a data source to fetch the AMI dynamically.. Using a data source to dynamically fetch the correct AMI avoids hardcoding invalid IDs and ensures the AMI exists in the region.

Answer

Hardcode a different AMI ID.

Answer

Set the AMI to null.

Answer

Add a lifecycle rule to ignore changes.

Question 15

A developer runs `terraform plan` and receives the error: "Error: Unsupported argument; An argument named 'enable_vpn_gateway' is not expected here." What is the most likely cause?

Accepted Answer

The module version 5.0.0 does not support the 'enable_vpn_gateway' argument.. The error 'Unsupported argument' indicates that the module version currently in use does not define an input variable named 'enable_vpn_gateway'. In Terraform, each module version has a fixed set of input variables; if you attempt to pass an argument that is not declared in the module's variables.tf, Terraform will reject it. The most common reason for this is that the module version has been updated or changed, and the argument was removed or renamed in that version.

Answer

The source address is misspelled 'vpc' instead of 'vpc/aws'.

Answer

The source module is not pinned to a specific version, so it may have changed.

Answer

The module must be sourced from a different registry or repository.