Free HashiCorp Terraform-Associate-004 Practice Exam with Questions & Answers | Set: 3

Detailed Explanation:

Rationale for Correct Answer: terraform init installs required provider plugins declared in the Terraform configuration. These providers can come from HashiCorp, partner publishers, or community publishers through the Terraform Registry or another configured provider source.

Analysis of Incorrect Options (Distractors):

B. False. Incorrect. Terraform is not limited to only HashiCorp-maintained providers. It can initialize and install third-party provider plugins.

Key Concept: Terraform providers are installed during initialization with terraform init.

This command will upgrade the plugins to the latest acceptable version within the version constraints specified in the configuration. The other commands do not have an -upgrade option.

Terraform creates the .terraform.lock.hcl file after the first terraform init command. This lock file ensures that the dependencies for your project are consistent across different runs by locking the versions of the providers and modules used.

This is the command that always causes a state file to be updated with changes that might have been made outside of Terraform, as it will only refresh the state file with the current status of the real resources, without making any changes to them or creating a plan.

In Terraform Cloud, you can switch between workspaces using both the web UI and CLI. The statement that you " must use the CLI " is false. Workspaces can securely store cloud credentials, offer role-based access control, and integrate with VCS to trigger plan and apply operations.

Rationale for Correct Answer: Data sources are referenced using the address format:data. < DATA_SOURCE_TYPE > . < NAME > . < ATTRIBUTE > Here, the type is aws_ami, the name is web, and the attribute is id, so the correct reference is data.aws_ami.web.id.

Analysis of Incorrect Options (Distractors):

A (aws_ami.web.id): Incorrect because it omits the required data. prefix. This looks like a managed resource reference, not a data source.

B (web.id): Incorrect because Terraform references must include the full address (type and name); web alone is ambiguous.

D (data.web.id): Incorrect because it omits the data source type (aws_ami).

Key Concept: Terraform addressing and attribute references for data sources.

Not all standard backend types support state locking and remote operations like plan, apply, and destroy. For example, the local backend does not support remote operations and state locking. State locking is a feature that ensures that no two users can make changes to the state file at the same time, which is crucial for preventing race conditions. Remote operations allow running Terraform commands on a remote server, which is supported by some backends like remote or consul, but not all.

Terraform keeps track of the infrastructure state via the state file. When you initially ran terraform plan, Terraform determined that the port should be changed from80 to 443. However, since another team member manually modified the load balancer, Terraform ' s local state file is now outdated.

When you run terraform apply, Terraform willcompare the expected state (from the plan) with the actual state (from the provider API).

Since the port is already set to443, but the local state file still shows80, Terraform willfail with an errordue to the state mismatch.

To resolve this, you should run terraform refresh or use terraform apply -refresh-only to update the local state before applying changes.

Official Terraform Documentation Reference:

State Management - HashiCorp Documentation

Managing Drift in Terraform

Detailed Explanation:

Rationale for Correct Answer:Module input variables are set by providing arguments in the module block whose names match the module’s declared variables. Since the module expects servers, you pass it directly as servers = 3. This is the standard Terraform module input pattern.

Analysis of Incorrect Options (Distractors):

A: Incorrect. var.servers is how you reference an input variable in expressions, not how you assign a module input. Module inputs are set as arguments, not through the var. namespace.

B: Incorrect. Terraform module blocks do not use an inputs = { ... } argument (that pattern is common in some other tools, but not Terraform).

D: Incorrect. inputs.servers is not valid HCL syntax for setting module input arguments.

Key Concept:Passing input variables to modules by setting arguments on the module block.

Detailed Explanation:

Rationale for Correct Answer: To bring existing infrastructure under Terraform management, Terraform needs both a matching resource block in the configuration and an import declaration or import command that maps the real cloud object to the Terraform resource address. With modern configuration-driven import, you add an import block and a corresponding resource block, then run Terraform to import the object into state.

Analysis of Incorrect Options (Distractors):

A. Pick the two correct responses below. Incorrect. This is an instruction, not an action.

B. Run terraform state pull. Incorrect. This only downloads and displays the current state. It does not import existing cloud resources.

E. Run terraform apply -refresh-only. Incorrect. Refresh-only updates Terraform state for resources already managed in state. It does not import unmanaged VMs.

Key Concept: Existing infrastructure must be imported into Terraform state and represented in Terraform configuration before Terraform can manage it.