To make Terraform's logging more verbose for troubleshooting purposes, you must configure the TF_LOG environment variable. This variable controls the level of logging and can be set to TRACE, DEBUG, INFO, WARN, or ERROR, with TRACE providing the most verbose output.Reference = Detailed debugging instructions and the use of environment variables like TF_LOG for increasing verbosity are part of Terraform's standard debugging practices

Rationale for Correct answer: Locals are evaluated as expressions, and one local can reference another using local.<name>. This supports building up derived values cleanly:
locals {
env = "prod"
app_name = "api-${local.env}"
}
Analysis of Incorrect Options (Distractors):
B (False): Incorrect-Terraform explicitly supports local-to-local references.
Key Concept: Local values (locals) and expression references.

Rationale for Correct answer: terraform graph outputs a Graphviz DOT representation of Terraform's dependency graph, which you can pipe into Graphviz tools (e.g., dot) to visualize resource/module dependencies.
Analysis of Incorrect Options (Distractors):
B: terraform show displays state or a plan file in human-readable form (or JSON with -json), not DOT.
C: terraform refresh (deprecated as a standalone command in newer workflows) refreshes state, not graph output.
D: terraform output prints root module outputs, not dependency graphs.
Key Concept: Visualizing Terraform's dependency graph using terraform graph.
Reference:

You must initialize your working directory before running terraform validate, as it will ensure that all the required plugins and modules are installed and configured properly. If you skip this step, you may encounter errors or inconsistencies when validating your configuration files.

Rationale for Correct answer: Terraform is designed to be idempotent. If the configuration and real infrastructure match the state, a subsequent terraform apply will show no changes and perform no actions.
Analysis of Incorrect Options (Distractors):
A: Terraform does not recreate resources unless the plan requires it (configuration change, forced replacement, drift that requires replacement, etc.).
B: Terraform won't create duplicates unless the configuration indicates multiple instances (e.g., count, for_each) or a new resource address.
C: The state was already written during the first successful apply; a second apply doesn't "re-apply to the state file" as a distinct action.
Key Concept: Terraform idempotency and convergence to desired state.
Reference: