* Rationale for Correct answer:When using count, Terraform creates resources indexed starting at 0.
With count = 2, the instances are indexed as:
* First instance # aws_instance.web[0]
* Second instance # aws_instance.web[1]
To reference the name attribute of the second instance, the correct syntax is:
aws_instance.web[1].name
* Analysis of Incorrect Options (Distractors):
* A. [2]: Incorrect because indexing starts at 0 and only indices 0 and 1 exist.
* B. *.name: Returns a list of all names, not a single instance value.
* D. [1]: References the whole resource object, not the name attribute.
* E. element(...): Incorrect syntax and wrong index; also unnecessary when direct indexing is available.
* Key Concept:Understanding resource indexing with count and zero-based indexing in Terraform.
Reference:Terraform Exam Objective - Read, Generate, and Modify Configurations

Terraform.tfstate
Explanation:
The name of the default file where Terraform stores the state is terraform.tfstate. This file contains a JSON representation of the current state of the infrastructure managed by Terraform. Terraform uses this file to track the metadata and attributes of the resources, and to plan and apply changes. By default, Terraform stores the state file locally in the same directory as the configuration files, but it can also be configured to store the state remotely in a backend. References = [Terraform State], [State File Format]

Rationale for Correct Answers:
B). View the execution plan: Correct - terraform plan shows what Terraform intends to do (create, update, or destroy).
C). Save a generated execution plan: Correct - using terraform plan -out=planfile lets you save the plan to apply later with terraform apply planfile.
Analysis of Incorrect Options:
A). Schedule runs in the future: Incorrect, Terraform does not provide scheduling; external tools (like cron, CI
/CD) are required.
D). Execute a plan in a different workspace: Incorrect, execution happens in the current workspace; switching workspaces must be done before running the plan.
Key Concept:
terraform plan is used for previewing and optionally saving an execution plan for controlled and predictable infrastructure changes.
Reference:Terraform Exam Objective - Understand Terraform Basics and CLI.

The Terraform Registry allows any user to publish and share modules. Published modules support versioning, automatically generate documentation, allow browsing version histories, show examples and READMEs, and more. Public modules are managed via Git and GitHub, and publishing a module takes only a few minutes. Once a module is published, releasing a new version of a module is as simple as pushing a properly formed Git tag1.
References = The information can be verified from the Terraform Registry documentation on Publishing Modules provided by HashiCorp Developer1.

The terraform validate command is used to check that your Terraform configuration files are syntactically valid and internally consistent. It is a useful command for ensuring your Terraform code is error-free before applying any changes to your infrastructure.