Which of the following is a benefit of using Sentinel with Terraform Cloud/Terraform Enterprise?

• A. Policy-as-code can enforce security best practices
• B. Sentinel Policies can be written in HCL
• C. You can restrict specific configurations on resources like CIDR 0.0.0.0/0 not allowed
• D. Sentinel policies are not version controlled

Answer: (A)

Policy-as-code that sits inside Terraform Cloud/Enterprise lets you codify security and governance rules so every plan and apply is automatically checked before changes are made. This is the core benefit: you define policies in Sentinel that gate Terraform runs, ensuring only compliant configurations are applied and providing a consistent, auditable security posture across teams. Policies are managed and versioned within Terraform Cloud, so you have a traceable history of what rules were in effect and why decisions were made. While a policy can block specific configurations (like open CIDR ranges), the overarching advantage is automated enforcement of security practices, not the existence of any single example rule. Sentinels don’t use HCL for policy logic, and the policy definitions are indeed versioned in Terraform Cloud, not left untracked.