The Terraform collection type that should be used to store key/value pairs is map. A map is a collection of values that are accessed by arbitrary labels, called keys. The keys and values can be of any type, butthe keys must be unique within a map. For example, var = { key1 = "value1", key2 = "value2" } is a map with two key
/value pairs. Maps are useful for grouping related values together, such as configuration options or metadata. References = [Collection Types], [Map Type Constraints]

Detailed Explanation:
* Rationale for Correct answer:
* init: Initializes the working directory, downloads providers and modules.
* apply: Executes the planned changes and provisions infrastructure.
Both steps are mandatory for provisioning new infrastructure.
* Analysis of Incorrect Options (Distractors):
* A. import: Used for existing resources, not provisioning new ones.
* B. plan: Optional but recommended; not strictly required.
* C. validate: Checks syntax only; does not provision resources.
* Key Concept:The Terraform workflow requires initialization and application to create infrastructure.
Reference:Terraform Exam Objective - Understand Terraform Basics and CLI

Terraforminstalls providers during the terraform init phase.
Providers aredownloaded and installedwhen running terraform init.
A (terraform plan)is incorrect because terraform plan only calculates changes but does not install providers.
C (terraform refresh)is incorrect because terraform refresh only updates the state but does not install providers.
Official Terraform Documentation Reference:
Provider Installation - HashiCorp Documentation

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

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.