Rationale for Correct answer:
D: Many remote backends support state locking, preventing concurrent operations from corrupting state and enabling safer team collaboration.
E: Remote state often supports encryption at rest (for example, via the remote storage system's server-side encryption), improving security of sensitive values that may reside in state.
Analysis of Incorrect Options (Distractors):
A: Incorrect-remote state does not prevent drift; drift can still occur if changes are made outside Terraform.
B: Incorrect-credentials for providers are still required; remote state doesn't remove that need (though a platform like HCP Terraform can centralize variable/credential management).
C: Incorrect-remote backends do not inherently make plan/apply faster; latency can even increase. Performance depends on environment and backend behavior.
Key Concept: Benefits of remote state: collaboration via locking and improved security controls for state storage.
Reference:

E (✅Correct)-IaC aims to eliminate manual cloud console workflowsby using code-based automation.
A, B, C (✅Advantages of IaC)- IaC enablesself-service deployment, API-driven workflows, and dynamic resource scaling.
D (diff command)- While useful, troubleshooting via diff is not acore advantageof IaC.
Official Terraform Documentation Reference:
What is Infrastructure as Code?

Infrastructure as Code (IaC) refers to managing infrastructureprogrammatically, enabling automation and repeatability.
Ais incorrect becauseIaC is not just about software delivery pipelines; it specifically deals with infrastructure.
Bis incorrect because"Write once, run anywhere" applies more to software development than IaC.
Dis incorrect becauseIaC does not enforce vendor-agnostic APIs; it depends on the tool and provider.
Official Terraform Documentation Reference:
What is Infrastructure as Code?

In Terraform, the correct way to reference a resource attribute is:
pgsql
CopyEdit
resource_type.resource_name.attribute
For example, if the resource block is:
hcl
CopyEdit
resource "kubernetes_namespace" "example" {
metadata {
name = "my-namespace"
}
}
To reference the name attribute, use:
pgsql
CopyEdit
kubernetes_namespace.example.name
Explanation of incorrect answers:
A (resource.kubernetes_namespace.example.name)- Incorrect. Terraform does not use the resource. prefix when referencing resources.
C (data.kubernetes.namespace.name)- Incorrect. This syntax is used fordata sources, not resources.
D (kubernetes_namespace.test.name)- Incorrect. The resource name is "example", not "test".
Official Terraform Documentation Reference:
Terraform Resource Reference

You need to write Terraform configuration files for the existing infrastructure that you want to import into Terraform, otherwise Terraform will not know how to manage it. The configuration files should match the type and name of the resources that you want to import.