From the Terraform Output Docs – Sensitive:

" Marking an output as sensitive prevents Terraform from showing its value in the CLI output,but it will still bestored in the state file. "

Thus, it protects display, not storage.

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

Rationale for Correct Answer: Terraform uses a declarative approach: you define the desired end state of infrastructure in configuration files that can be version-controlled and repeatedly applied. Terraform then computes an execution plan to reach that state. This is a key distinction from ad-hoc API calls or hand-written scripts that typically manage infrastructure in a more imperative and less state-aware way.

Analysis of Incorrect Options (Distractors):

B: Incorrect because Terraform is not “merely a wrapper.” It provides a workflow (state, diff/plan, dependency graph, drift detection) that fundamentally changes how infrastructure is managed.

C: Incorrect because Terraform does not replace provider APIs; providers still use the underlying cloud/service APIs.

D: Incorrect because Terraform is primarily declarative, not imperative scripting to force a specific order (ordering is derived from dependencies).

Key Concept: Declarative desired-state configuration, plan/apply workflow, and version-controlled IaC.

Rationale for Correct Answer:

C: Securely managed .tfvars files are acceptable if not committed to version control.

D: HCP Terraform provides secure storage for sensitive variables.

E: HashiCorp Vault is designed for secrets management and integrates with Terraform.

Analysis of Incorrect Options (Distractors):

A: Plaintext storage is insecure.

B: Secrets should never be committed to version control.

Key Concept:Sensitive values must be stored using secure secret management solutions.

Some backends support state locking, which prevents other users from modifying the state file while a Terraform operation is in progress. This prevents conflicts and data loss. Not all backends support this feature, and you can check the documentation for each backend type to see if it does.

Terraform variable names are not saved in the state file, only their values are. The state file only stores the attributes of the resources and data sources that are managed by Terraform, not the variables that are used to configure them.

Detailed Explanation:

Rationale for Correct Answer:Terraform’s import block (introduced in newer versions) requires two essential pieces of information:

A. Resource address – This specifies where in Terraform configuration the imported resource will be mapped (e.g., aws_db_instance.example).

C. Resource ID – This is the unique identifier used by the provider to locate the existing infrastructure (e.g., database ID in AWS, Azure, etc.).

These two elements allow Terraform to associate an existing real-world resource with a resource block in your configuration, aligning with the objective of managing existing infrastructure using Terraform.

Analysis of Incorrect Options (Distractors):

B. Path to the .tf file Incorrect because Terraform does not require file paths; it works with resource addresses defined in configuration.

D. Database platform and version Incorrect because this information may exist in configuration but is not required for the import operation itself.

E. Connection string Incorrect because Terraform uses provider APIs, not direct connection strings, to manage infrastructure.

Key Concept: Importing existing infrastructure requires a resource address and provider-specific resource ID.

It lets you version, reuse, and share infrastructure configuration as code files, which can be stored in a source control system and integrated with your CI/CD pipeline.

It reduces risk of operator error by automating repetitive tasks and ensuring consistency across environments. IaC does not necessarily provision resources at a lower cost, secure your credentials, or prevent manual modifications to your resources - these depend on other factors such as your cloud provider, your security practices, and your access policies.

terraform initretrieves and caches providers and modules, butonly for explicitly declared modulesin the configuration.

If a module isadded or updated, terraform init needs to be re-run to download the new version.

Terraform does not automatically cache all remote modules unless they are explicitly referenced in the configuration.

Official Terraform Documentation Reference:

terraform init - HashiCorp Documentation

In Terraform, the max function can be used to select the largest number from a list of numbers. The max function takes multiple arguments and returns the highest one. For the list numcpus = [18, 3, 7, 11, 2], using max(numcpus...) will return 18, which is the largest number in the list.