How is the Terraform remote backend different than other state backends such as S3, Consul, etc.?

• A. It can execute Terraform runs on dedicated infrastructure on premises or in Terraform Cloud
• B. It doesn't show the output of a terraform apply locally
• C. It is only available to paying customers
• D. All of the above

Answer: (A)

Remote backends enable remote operations: the plan and apply runs are executed on dedicated infrastructure (such as Terraform Cloud or on‑premises Terraform Enterprise) rather than on your local machine. That’s why the core distinction from common state backends like S3 or Consul is not just storing state—it's where the Terraform work actually runs. The best answer captures this by stating that remote backends can execute Terraform runs on on‑premises infrastructure or in Terraform Cloud.

The other points aren’t universal truths: while using a remote backend the detailed apply output is typically viewed in the remote workspace UI rather than fully locally, and the remote backend isn’t strictly restricted to paying customers since Terraform Cloud offers free tiers as well.