Rationale for Correct Answer:
A (State versions and run history): HCP Terraform workspaces track state versions and maintain run history for auditability and rollback/reference—this is a hosted workflow feature beyond local-only Community Edition.
C (Variable sets): HCP Terraform provides variable sets to centrally manage and share Terraform/environment variables across multiple workspaces—Community Edition does not have this workspace-level managed feature.
D (Remote execution): HCP Terraform can execute plans/applies remotely in its managed runners, instead of requiring local execution.
Analysis of Incorrect Options (Distractors):
B: Not a standard “workspace feature” guaranteed as part of HCP Terraform workspaces in the same way as state/run history/remote runs/variables; security scanning depends on additional capabilities/policies/integrations rather than being the core baseline feature described here.
E: Storing configuration in VCS is not unique to HCP Terraform—you can store Terraform code in VCS with Community Edition as well. (HCP Terraform can integrate with VCS-driven workflows, but it doesn’t uniquely “store” your configuration.)
F: Terraform Community Edition also supports multiple cloud providers via providers; this is not exclusive to HCP Terraform.
Key Concept: Differences between local Terraform (Community Edition) and HCP Terraform workspace capabilities: remote runs, state history, centralized variables.
[Reference: Terraform Objectives — Manage Terraform Workspaces and Cloud (HCP Terraform/Terraform Enterprise workspace features)., , , , , ]
