Terraform is built on a plugin-based architecture, enabling developers to extend Terraform by writing new plugins or compiling modified versions of existing plugins1. Terraform plugins are executable binaries written in Go that expose an implementation for a specific service, such as a cloud resource, SaaS platform, or API2. If there is no existing provider for your API, you can create one using the Terraform Plugin SDK3 or the Terraform Plugin Framework4. References =
*1: Plugin Development - How Terraform Works With Plugins | Terraform | HashiCorp Developer
*2: Lab: Terraform Plug-in Based Architecture - GitHub
*3: Terraform Plugin SDK - Terraform by HashiCorp
*4: HashiCorp Terraform Plugin Framework Now Generally Available

This is what state locking accomplishes, by preventing other users from modifying the state file while a Terraform operation is in progress. This prevents conflicts and data loss.

In Terraform, theresource nameis the second argument in the resource block.
The structure of a resource block is:
resource " provider_resource_type " " resource_name " {
# Configuration settings
}
Here, the provider type isgoogle_compute_instance, and theresource nameis " main " .
The name " test " is simply the value assigned to the name attribute, which is unrelated to the Terraform resource name.
" google " and " compute_instance " are part of the provider and resource type, not the resource name.
Official Terraform Documentation Reference:
Terraform Resource Documentation

While terraform destroy is a common way to remove infrastructure, it isnot the only way.
You can also remove resources bydeleting them from the configuration and running terraform apply.
Manually deleting resources in the cloud provider can also remove infrastructure (but Terraform won't be aware unless the state is updated).
Official Terraform Documentation Reference:
terraform destroy - HashiCorp Documentation

Detailed Explanation:
Rationale for Correct Answer: HashiCorp recommends storing secrets in secure, purpose-built systems or mechanisms that avoid exposing sensitive values in plaintext or version control:
B). HashiCorp Vault is a dedicated secrets management solution designed to securely store and control access to sensitive data.
D). Environment variables (TF_VAR_) allow passing sensitive values at runtime without persisting them in configuration files or version control.
E). HCP Terraform sensitive variables are encrypted and hidden from logs and UI output, making them a secure option for managing secrets in Terraform Cloud/Enterprise environments.
These approaches align with Terraform best practices for secure secret management and protecting sensitive inputs in IaC workflows.
Analysis of Incorrect Options (Distractors):
A). Plaintext document on a shared drive is insecure and exposes secrets to unauthorized access.
C). terraform.tfvars committed to version control is explicitly discouraged because secrets would be stored in plaintext and tracked in Git history, creating a major security risk.
Key Concept: Secure handling of sensitive data in Terraform using Vault, environment variables, and sensitive input variables.
Reference: Terraform Objective Domain: Manage Terraform Workspaces and Cloud