Terraform-Associate-004 Exam Questions Tutorials

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.

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.

Rationale for Correct Answer (C):

Credentials should not be hardcoded in Terraform files. Best practice is to configure them via environment variables or secret managers.

Analysis of Incorrect Options:

A: Shared servers introduce risk and drift.

B: Storing secrets in config/version control is insecure.

D: Incorrect since option C is valid.

Key Concept:

Separation of credentials from code is a Terraform security best practice.

Rationale for Correct Answer: A moved block tells Terraform that an object’s address in state has changed (renamed/refactored) and it should move the state from the old address to the new address. This preserves the existing real resource and prevents unnecessary destroy/recreate.

Analysis of Incorrect Options (Distractors):

A: Works but is unnecessarily risky/extra work; moved is the intended refactoring mechanism for renames.

B: Incorrect—refresh-only updates state to match real infrastructure, but it does not remap an object from one address to another.

C: Incorrect—Terraform will treat the new name as a new resource address and the old one as removed unless you explicitly move/rename state.

Key Concept: Refactoring addresses safely using moved blocks (state address migration).