Rationale for Correct answer: Remote state storage is configured using a backend block, which lives inside the top-level terraform block (for example, terraform { backend "s3" { ... } }). Backends control where Terraform stores state (local vs remote), locking, and related settings-this is squarely in the Terraform configuration's global settings area, not in resources or providers.
Analysis of Incorrect Options (Distractors):
A (The resource block): Resources define infrastructure objects (e.g., servers, buckets). They do not configure where Terraform stores state.
B (The provider block): Providers configure how Terraform talks to an API (credentials/regions/features). They don't define state storage.
C (The data block): Data sources read existing infrastructure; they are unrelated to backend/state storage configuration.
Key Concept: Backends and remote state configuration using terraform { backend ... }.
Reference:

Rationale for Correct answer: With immutable infrastructure, you don't modify running servers/resources in place; you replace them with new versions built from a known image/artifact. This reduces configuration drift and "snowflake" issues, making deployments and rollbacks more predictable-often resulting in less operational complexity compared with troubleshooting in-place changes.
Analysis of Incorrect Options (Distractors):
A: Incorrect-immutable infrastructure specifically avoids in-place upgrades.
B: Not the best answer-upgrades can be fast in some setups, but "quicker" is not guaranteed; replacing infrastructure may take time depending on provisioning and rollout strategy.
C: Incorrect-immutability doesn't inherently mean upgrades are "automatic"; automation is a separate practice/tooling choice.
Key Concept: Immutable vs mutable infrastructure; replace instead of modify to reduce drift and simplify operations.

The error messageindicates an authentication issue (403 - Access Denied), which requiresdebugging Terraform logs.
Setting TF_LOG=DEBUG enablesdetailed logs, providing insights into API requests, state loading, and authentication errors.
Terraformdoes not log errors in /var/log/terraform.log or syslog, making optionsC and D incorrect.
A (terraform login)is only relevant forTerraform Cloud, but this error appears to be related toprovider authentication.
Official Terraform Documentation Reference:
Debugging Terraform

Rationale for Correct answer: terraform plan creates and displays an execution plan showing what Terraform would change, add, or destroy to reach the desired state-this is the standard preview step before applying changes.
Analysis of Incorrect Options (Distractors):
A: terraform show displays a human-readable view of an existing state or plan file; it doesn't compute proposed changes by itself.
C: terraform validate checks configuration syntax and internal consistency, not proposed infrastructure changes.
D: terraform get downloads modules; it doesn't preview infrastructure changes.
Key Concept: Previewing changes with plan in the Terraform workflow.
Reference:

To see all the resources that Terraform will delete, you can use either of these two commands:
terraform destroy will show the plan of destruction and ask for your confirmation before proceeding. You can cancel the command if you do not want to destroy the resources.
terraform plan -destroy will show the plan of destruction without asking for confirmation. You can use this command to review the changes before running terraform destroy. Reference = : Destroy Infrastructure : Plan Command: Options