HashiCorp Terraform Associate (004) Question 18
Single answer1c Explain how Terraform manages multi-cloud, hybrid cloud, and service-agnostic workflowsA platform team needs to standardize infrastructure delivery for two application groups. One group deploys to AWS, another deploys to Azure, and both depend on a shared SaaS DNS provider for public records. The company also has a small VMware-based private environment for legacy workloads. The team wants one workflow and one language for provisioning across these environments, while still allowing each environment to use its own APIs. Which approach best explains how Terraform supports this requirement?
- A
Use Terraform providers for AWS, Azure, VMware, and the DNS service in the same configuration or across modules, because Terraform uses provider plugins to interact with different platform APIs through a common workflow.
- B
Use Terraform only for one cloud at a time, because each Terraform configuration can communicate with only a single provider and cannot coordinate resources across multiple platforms.
- C
Convert all infrastructure targets to Kubernetes first, because Terraform can manage multi-cloud resources only when they are exposed through a Kubernetes API.
- D
Use Terraform to provision the public cloud resources, but use separate vendor-specific IaC tools for VMware and SaaS services because Terraform is cloud-specific and cannot manage hybrid or service-agnostic workflows.
Show answer and explanation
Correct answer: A
Explanation
Terraform manages multi-cloud, hybrid cloud, and service-agnostic workflows through its provider-based architecture. A provider is a plugin that exposes resources and data sources for a specific platform or service. This lets the same Terraform language and workflow manage AWS, Azure, private infrastructure such as VMware vSphere, and third-party services such as DNS providers. Terraform then builds a dependency graph across all referenced resources, even when they come from different providers. This is why organizations can use one workflow for heterogeneous environments without requiring a single vendor API or a Kubernetes layer. HashiCorp documentation for Terraform providers and the Terraform workflow emphasizes that Terraform is platform-agnostic and works by integrating with APIs through providers, making it suitable for multi-cloud and hybrid scenarios.
- A. Correct.
Correct. Terraform is designed around provider plugins, which let it communicate with many different infrastructure and service APIs, including public clouds, private infrastructure platforms, and SaaS products. In practice, a team can use providers such as AWS, AzureRM, vSphere, and DNS/SaaS providers within a consistent workflow of init, plan, and apply. This is the core of how Terraform supports multi-cloud, hybrid cloud, and service-agnostic automation.
- B. Incorrect.
Incorrect. A common misconception is that Terraform is limited to one provider per configuration. In reality, a single configuration can use multiple providers, and modules can also be composed to organize resources by environment or platform. Terraform regularly coordinates dependencies across different providers in one graph.
- C. Incorrect.
Incorrect. Terraform does not require Kubernetes as an abstraction layer for multi-cloud management. While Terraform can manage Kubernetes resources through a Kubernetes provider, it can also interact directly with cloud, virtualization, networking, and SaaS APIs through their respective providers.
- D. Incorrect.
Incorrect. Terraform is not limited to public cloud provisioning. Its service-agnostic model is specifically based on providers for many types of platforms, including on-premises virtualization and external services. Using separate tools may be an organizational choice, but it is not required because Terraform can support hybrid and SaaS-integrated workflows.