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]: Reference 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.

You cannot access state stored with the local backend by using the terraform_remote_state data source. The terraform_remote_state data source is used to retrieve the root module output values from some other Terraform configuration using the latest state snapshot from the remote backend. It requires a backend that supports remote state storage, such as S3, Consul, AzureRM, or GCS. The local backend stores the state file locally on the filesystem, which terraform_remote_state cannot access.
Reference:
Terraform documentation on terraform_remote_state data source: Terraform Remote State Data Source Example usage of remote state: Example Usage (remote Backend)

Rationale for Correct Answer (B):
Terraform interacts with external systems through providers. Since this is a new proprietary service with its own API, Terraform does not support it by default. You would need to develop a custom provider that implements Terraform's provider interface and interacts with the proprietary APIs to manage resources like users.
Analysis of Incorrect Option:
A . Any service hosted on a public cloud provider: Not true. Terraform can only manage services that have providers (official or custom). Just being "hosted on a public cloud" doesn't guarantee Terraform support.
Key Concept:
Terraform providers act as the bridge between Terraform and external APIs. For unsupported services, a custom provider must be developed.
Reference:
Terraform Exam Objective - Manage Terraform Resources and Providers.

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.

To prevent two Terraform runs from changing the same state file simultaneously, state locking is used. State locking ensures that when one Terraform operation is running, others will be blocked from making changes to the same state, thus preventing conflicts and data corruption. This is achieved by configuring the state backend to support locking, which will lock the state for all operations that could write to the state.Reference = This information is supported by Terraform's official documentation, which explains the importance of state locking and how it can be configured for different backends to prevent concurrent state modifications .