TF-004 Interact with Terraform modules Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Configure backend with locking, then run terraform init, then run terraform apply, then run terraform destroy.

  Why this is correct

  This is the correct order because the backend must be configured with a locking mechanism first, then initialized with terraform init to set up the backend, then terraform apply acquires the lock during infrastructure creation, and terraform destroy acquires the lock during teardown, ensuring no concurrent state modifications.

• ✗

  Run terraform init, then configure backend with locking, then run terraform apply, then run terraform destroy.

  Why it's wrong here

  Running "terraform init" prematurely, before the backend configuration with locking is defined in the HCL, will cause Terraform to initialize with a local state backend by default. This means the critical locking mechanism is completely absent from the initialized working directory. Subsequent backend configuration, even if added to the HCL, requires another "terraform init -reconfigure" to be recognized and applied, making the initial "init" ineffective for state locking.

• ✗

  Configure backend with locking, then run terraform apply, then run terraform init, then run terraform destroy.

  Why it's wrong here

  Executing "terraform apply" prior to "terraform init" will invariably result in an error because the Terraform working directory has not been properly prepared. "terraform init" is responsible for downloading necessary providers, configuring the remote backend, and setting up the local ".terraform" directory. Without this foundational initialization, "apply" cannot locate providers, manage state, or engage any backend-specific features like state locking, rendering the command inoperable.

• ✗

  Run terraform apply, then configure backend with locking, then run terraform init, then run terraform destroy.

  Why it's wrong here

  Attempting to run "terraform apply" as the very first step is fundamentally incorrect because Terraform requires a configured and initialized environment to operate. Without any backend configuration defined in the HCL and subsequently initialized via "terraform init", "apply" has no remote state to interact with, no providers to use, and no locking mechanism to enforce. This sequence would lead to immediate errors, preventing any infrastructure changes and completely bypassing state management and locking.

Go deeper

Related to this question