Rationale for Correct Answer:Terraform detects drift by refreshing state during terraform apply. Since the VM no longer exists but is still declared in configuration, Terraform will plan and recreate the missing resource.

Analysis of Incorrect Options (Distractors):

B. Error: Terraform treats this as drift, not an error.

C. Remove from state: Terraform does not remove resources automatically unless instructed.

D. No changes: Incorrect because drift is detected and corrected.

Key Concept:Terraform enforces the desired state defined in configuration, correcting drift automatically.

Detailed Explanation:

Rationale for Correct Answer:

A: IaC enables a plan/review workflow (for Terraform: terraform plan) where changes can be inspected and approved before applying, reducing accidental outages.

E: Declarative IaC helps reduce configuration drift because desired state is defined in code and Terraform continuously reconciles differences during plans/applies (drift becomes visible and correctable).

Analysis of Incorrect Options (Distractors):

B: Incorrect. Auto-scaling is a capability of specific platforms/services (e.g., AWS ASG), not a guaranteed property of IaC.

C: Incorrect. IaC reduces the chance of mistakes, but it does not make incorrect configurations impossible—bad code can still be applied.

D: Incorrect. Zero-downtime updates require architecture and deployment strategies (blue/green, rolling updates, etc.); IaC alone doesn’t guarantee it.

Key Concept:Reliability improvements from IaC: reviewable change plans and reduced drift through declarative desired state.

Terraform state can contain highly sensitive resource attributes, including passwords, private keys, API tokens, database credentials, and other provider-returned values. Consequently, committing terraform.tfstate to Git or another version-control system risks exposing secrets to repository users and permanently retaining them in repository history. HashiCorp explicitly recommends excluding Terraform state and state backups from version control. State should normally be stored in HCP Terraform or an appropriate remote backend where access controls, encryption, and state-locking capabilities can be applied. Option B is incorrect because the principal risk is infrastructure and secret data rather than personal information about the last operator. Option C is false because Terraform uses the local backend by default. Option D is false because Terraform requires persistent state for subsequent infrastructure management.

================

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.

The terraform import command is not part of any other Terraform workflow. It must be explicitly invoked by the user with the appropriate arguments, such as the resource address and the ID of the existing infrastructure to import. References = [Importing Infrastructure]

The terraform state file is locked when a Terraform operation that could write state is in progress. This prevents concurrent state operations that could corrupt the state. The forbidden actions when the state file is locked are those that could write state, such as terraform apply, terraform destroy, terraform refresh, terraform taint, terraform untaint, terraform import, and terraform state *. The terraform validate command is also forbidden, because it requires an initialized working directory with the state file. The allowed actions when the state file is locked are those that only read state, such as terraform plan, terraform show, terraform output, and terraform console. References = [State Locking] and [Command: validate]

Rationale for Correct Answer: Terraform logging is controlled via environment variables. TF_LOG sets the verbosity (e.g., DEBUG), and TF_LOG_PATH directs Terraform to write those logs to a specified file path. This is part of Terraform CLI troubleshooting and operational usage.

Analysis of Incorrect Options (Distractors):

B (Update the Terraform CLI configuration file): The CLI config can control some behaviors (credentials helpers, plugin cache, etc.), but log-to-file is specifically handled by TF_LOG_PATH.

C (Add a path argument to the terraform block): The terraform block configures required versions, required providers, and backends—not CLI logging output.

D (Run the terraform output command): terraform output displays output values from state; it has nothing to do with logging.

Key Concept: Terraform debugging and logging via environment variables (TF_LOG, TF_LOG_PATH).

This is the command that lets you experiment with Terraform expressions, by providing an interactive console that allows you to evaluate expressions and see their results. You can use this command to test your expressions before using them in your configuration files.

Detailed Explanation:

Rationale for Correct Answer: terraform force-unlock should be used only when Terraform’s normal automatic unlocking has failed and you are sure no other Terraform process is actively using the state. It manually removes a stale lock.

Analysis of Incorrect Options (Distractors):

A. When terraform apply has failed due to a state lock. Incorrect. A lock error alone does not justify force unlocking. Another valid Terraform operation may still be running.

B. When you have a high-priority change. Incorrect. Urgency is not a valid reason to bypass state locking safeguards.

D. When you see a status message stating that Terraform cannot acquire the lock. Incorrect. This may simply mean another run is active. You should investigate before using force-unlock.

Key Concept: Force unlocking is a recovery action for stale locks, not a normal operational shortcut.

Detailed Explanation:

Rationale for Correct Answer: The import block declaratively tells Terraform to associate an existing infrastructure object with a Terraform resource address. After the configuration is applied, Terraform imports the existing resource and updates Terraform state so that Terraform can manage it.

Analysis of Incorrect Options (Distractors):

A: Moving resources between state addresses or state files is a state-management operation; it is not the purpose of an import block.

B: The import block does not merge Terraform state files.

C: Modules are downloaded during initialization, not by an import block.

Key Concept: Bringing existing infrastructure under Terraform management by importing it into state.