Terraform Associate 004 ยท Infrastructure as Code basics
Multi-cloud and service-agnostic Terraform
One workflow and HCL language across providers (cloud, SaaS, on-prem), providers as plugins, what Terraform does not abstract away (1c).
Key points
- One Write, Plan, Apply workflow and one language (HCL) across clouds, SaaS and on-prem. Providers are plugins that call each platform's API. Terraform does not make resources portable: an AWS resource type is not an Azure one.
Source: https://developer.hashicorp.com/terraform/intro
Practice questions
How does Terraform communicate with a platform such as AWS or Kubernetes?
- Through provider plugins that call the platform API
- By logging in over SSH and typing commands
- Through a built-in client for every vendor in core
- By editing the vendor's database directly
Show answer
Answer: A. Through provider plugins that call the platform API
Providers are plugins that translate configuration into that platform's API calls. Terraform core does not embed every vendor's API.
Which can Terraform manage through providers?
- Public cloud resources
- SaaS resources such as DNS records
- On-premises platforms with an API, such as Kubernetes
- Employees' working habits
- Paper contracts with vendors
Show answer
Answer: A. Public cloud resources, B. SaaS resources such as DNS records, C. On-premises platforms with an API, such as Kubernetes
Providers exist for public clouds, SaaS services and on-prem or hybrid platforms. A person's habits or a paper contract are not API-managed objects.
True or false: Terraform lets you write one resource block that deploys unchanged to both AWS and Azure.
Show answer
Answer: False
False. Terraform unifies the workflow and language, not the resource types; each provider defines its own resources and arguments.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
