Terraform init retrieves the source code for all referenced modules.

Terraform init retrieves the source code for all referenced modules.

• A. True
• B. False
• C. It validates the syntax without fetching sources
• D. It only downloads provider plugins

Answer: (A)

Terraform init initializes the working directory by fetching and preparing the code for all modules referenced in the configuration. When a module declares a remote source (such as the Terraform Registry, a Git repository, or another URL), init downloads that module’s source code so Terraform can access and use it during planning and applying. The downloaded modules are stored in the .terraform/modules cache for reuse. Local path modules are used directly from your filesystem, but the overall effect is that the sources for all referenced modules are available before Terraform proceeds. This is why the statement is correct: init ensures you have the sources for all modules you reference. It also downloads provider plugins, but that doesn’t change the fact that module sources are fetched as part of initialization.

Terraform init initializes the working directory by fetching and preparing the code for all modules referenced in the configuration. When a module declares a remote source (such as the Terraform Registry, a Git repository, or another URL), init downloads that module’s source code so Terraform can access and use it during planning and applying. The downloaded modules are stored in the .terraform/modules cache for reuse. Local path modules are used directly from your filesystem, but the overall effect is that the sources for all referenced modules are available before Terraform proceeds. This is why the statement is correct: init ensures you have the sources for all modules you reference. It also downloads provider plugins, but that doesn’t change the fact that module sources are fetched as part of initialization.