HashiCorp Terraform Associate (004) Question 56
Single answer3b Initialize a Terraform working directoryA platform engineer clones a Terraform configuration for an existing project into a new workstation. The root module already contains a required_providers block for hashicorp/aws and a backend "s3" block for remote state. The engineer wants Terraform to download the required provider plugin and configure the working directory to use the remote backend before running plan. Which command should they run from the root of the configuration?
- A
terraform init
- B
terraform validate
- C
terraform refresh
- D
terraform get
Show answer and explanation
Correct answer: A
Explanation
The correct answer is terraform init. In a newly cloned or changed Terraform working directory, init is the first command typically run. It prepares the directory by initializing the backend, downloading and installing provider plugins, and installing referenced modules. This is especially important when the configuration includes a remote backend such as s3, because Terraform must configure state access before planning or applying. HashiCorp documentation describes terraform init as the command that initializes a working directory containing Terraform configuration files. Commands such as validate and plan are used after initialization, while terraform get is not a full substitute for init in modern Terraform workflows.
- A. Correct.
Correct. terraform init is the command used to initialize a working directory that contains Terraform configuration files. During initialization, Terraform installs required providers, sets up the configured backend such as s3, and prepares the .terraform directory so subsequent commands like terraform plan can run successfully.
- B. Incorrect.
Incorrect. terraform validate checks whether the configuration is syntactically valid and internally consistent, but it is not the primary command used to initialize the working directory. While validation may require initialization first in many cases, it does not perform backend initialization or provider installation as its main purpose.
- C. Incorrect.
Incorrect. terraform refresh updates the state with real infrastructure information, but it does not initialize a new working directory. A common misconception is that refresh prepares Terraform to work with existing infrastructure; however, initialization with terraform init must happen first so Terraform can configure the backend and install providers.
- D. Incorrect.
Incorrect. terraform get is associated with downloading and updating modules in older workflows, but it does not fully initialize the working directory for current Terraform usage. It does not replace terraform init, which handles provider installation, backend initialization, and module installation together.