Rationale for Correct Answer: terraform plan -destroy does not destroy anything. It only creates a plan that proposes destroying all managed resources. Actual destruction happens only when you run terraform destroy or terraform apply with an approved destroy plan.

Analysis of Incorrect Options (Distractors):

A: Does trigger destruction (interactive approval by default).

B: Incorrect because terraform plan -destroy does not perform destruction.

D: Does trigger destruction and skips the interactive approval prompt.

Key Concept: Difference between planning a destroy and executing a destroy.

Inrefresh-only mode(terraform apply -refresh-only), Terraformupdates the state fileto match the actual infrastructurewithout modifying resources.

A (Terraform configuration)–Not modifiedin refresh-only mode.

B (Terraform plan)–Plan is generated but not modified.

D (Cloud infrastructure)–Not modifiedin refresh-only mode.

Official Terraform Documentation Reference:

Refresh-Only Mode

Detailed Explanation:

Rationale for Correct Answer: Terraform state files (terraform.tfstate) can store sensitive data in plain text, including attributes such as passwords, private keys, API tokens, and other secrets returned by providers. Because of this, HashiCorp recommends securing state files using encryption, access controls, and remote backends (like S3 with encryption or Terraform Cloud). Protecting the state file is a critical part of state management and security in Terraform.

Analysis of Incorrect Options (Distractors):

B. It stores all environment variables from the machine that created it. Incorrect because Terraform state does not capture environment variables; it only tracks resource attributes and metadata.

C. It can be manually edited to change the deployed resources. Incorrect because while the state file can technically be edited, this is not the reason it is considered sensitive. Also, manual edits are discouraged and risky.

D. It contains personal information about the last user to update it. Incorrect because Terraform state does not store personal user data.

Key Concept: Terraform state files may contain sensitive infrastructure data and secrets, requiring secure storage and access control.

Terraform state files are not automatically encrypted by default. Sensitive values are stored in plaintext within the state file. However, you can protect the state file by using remote backends that support encryption, such as AWS S3 with server-side encryption enabled or Terraform Cloud, which offers encrypted state storage.

The correct answer is C because local state files are not reliable for shared automation environments such as CI/CD pipelines. A local backend stores state on the machine where Terraform runs, so another pipeline worker usually cannot access that file. Moving Configuration A to a remote backend, such as HCP Terraform, Amazon S3, Azure Storage, or Google Cloud Storage, makes the state centrally available to authorized Terraform runs. Configuration B can then use the terraform_remote_state data source to read Configuration A’s outputs from that remote backend. Option A creates manual value passing and can drift from actual state. Option B fails when the file is not on the pipeline machine. Option D may work technically, but it removes useful separation between network and compute configurations.

The terraform init command is required before using a new backend or integrating with HCP Terraform/Terraform Cloud.

terraform init initializes the working directory and sets up the backend, downloading necessary provider plugins and modules.

If the backend configuration changes, Terraform willrequirere-initialization to apply those changes.

Without running terraform init, Terraform willfailto use a new backend or remote Terraform Cloud workspace.

Official Terraform Documentation Reference:

terraform init - HashiCorp Documentation

Module variable assignments are not inherited from the parent module and you need to explicitly set them using the source argument. This allows you to customize the behavior of each module instance.

Detailed Explanation:

Rationale for Correct Answer:terraform fmt rewrites Terraform configuration files (.tf, and commonly .tfvars) into Terraform’s canonical formatting style (indentation, alignment, spacing, etc.). By default, it formats files in the current directory (and with flags like -recursive, it can format subdirectories too).

Analysis of Incorrect Options (Distractors):

B: Incorrect because formatting is exactly what terraform fmt is designed to do.

Key Concept:Using terraform fmt to enforce consistent HCL formatting.

This is the backend that the Terraform CLI uses by default, unless you specify a different backend in your configuration. The local backend stores the state file in a local file named terraform.tfstate, which can be used to track and manage the state of your infrastructure.

Detailed Explanation:

Rationale for Correct Answer:

A: terraform plan -out=planfile saves the proposed execution plan so you can later run terraform apply planfile. This supports review and controlled deployments.

B: terraform plan shows what Terraform would change (create/update/destroy) so you can verify changes before applying—this is one of the primary purposes of plan.

Analysis of Incorrect Options (Distractors):

C: Incorrect. Scheduling runs is not a capability of terraform plan (that’s handled by external schedulers/CI systems or HCP Terraform scheduling features—not the CLI plan command itself).

D: Incorrect. Workspaces are selected via terraform workspace select < name > (or by using separate working directories / automation). terraform plan itself doesn’t “execute in a different workspace” without switching context first.

Key Concept:terraform plan for previewing changes and optionally saving an execution plan file for later application.