HashiCorp Terraform Associate (004) Question 17
Single answer1c Explain how Terraform manages multi-cloud, hybrid cloud, and service-agnostic workflowsA platform team is standardizing infrastructure delivery for an application that runs partly in AWS and partly on-premises VMware. They also want the same Terraform workflow to manage a third-party DNS provider used by both environments. The team wants one approach that can provision resources across these systems without rewriting their process for each platform. Which statement best explains how Terraform supports this requirement?
- A
Terraform uses providers to interact with different platforms and services, so the same workflow can manage AWS, VMware, and DNS resources in a unified configuration.
- B
Terraform can manage multiple clouds only if all target platforms expose the same native API structure and resource model.
- C
Terraform requires separate CLI tools and separate state engines for each cloud, so multi-cloud and hybrid workflows must be orchestrated outside Terraform.
- D
Terraform supports hybrid infrastructure only for HashiCorp products; third-party services such as external DNS providers must be managed manually.
Show answer and explanation
Correct answer: A
Explanation
Terraform manages multi-cloud, hybrid cloud, and service-agnostic workflows through its provider model. A provider is a plugin that defines resources and data sources for a specific platform or service, allowing Terraform to interact with cloud providers, virtualization platforms, SaaS products, networking tools, and more. Because a single Terraform configuration can declare multiple providers, teams can provision and coordinate infrastructure across AWS, on-premises VMware, and a DNS platform in the same workflow. This aligns with Terraform documentation describing providers as the mechanism for interacting with cloud providers and other APIs. The key exam point is that Terraform is not tied to one cloud or vendor-specific workflow; instead, it offers a consistent declarative approach across heterogeneous environments.
- A. Correct.
Correct. Terraform is service-agnostic because it relies on providers, which translate Terraform configuration into API calls for many different platforms and services. In practice, a single configuration can use multiple providers, such as AWS for cloud resources, vSphere for VMware infrastructure, and a DNS provider for external DNS records. This is exactly how Terraform enables multi-cloud, hybrid cloud, and broader service-agnostic workflows.
- B. Incorrect.
Incorrect. Terraform does not require platforms to share a common API structure or identical resource model. Providers abstract those differences. AWS, VMware, and DNS services all have different APIs, but Terraform can still manage them together through their respective providers.
- C. Incorrect.
Incorrect. Terraform uses one CLI workflow across providers. While teams may choose different state backends for collaboration, Terraform does not require a separate state engine or a separate native CLI per cloud in order to support multi-cloud or hybrid deployments. This option reflects a common misconception that Terraform merely wraps vendor-specific tooling.
- D. Incorrect.
Incorrect. Terraform is not limited to HashiCorp products for hybrid workflows. A major strength of Terraform is that it can manage many third-party platforms and SaaS services through providers. External DNS providers are a common real-world example of non-HashiCorp services managed with Terraform.