Infrastructure as Code (IaC) with Terraform: 5 TF-TA004 Questions with Full Explanations
5 questions, one domain: Infrastructure as Code (IaC) with Terraform from the HashiCorp Terraform Associate (004) (TF-TA004) exam. Pick your answer, then check it against the explanation.

HashiCorp Terraform Associate (004) (TF-TA004) · Infrastructure as Code (IaC) with Terraform · 5 questions with answers and explanations
🧠What these questions look for
As the entry point of the exam, this domain checks the ideas behind infrastructure as code more than syntax. Items ask what Terraform is for, how it works across platforms, and which of its parts (providers, modules, HCL, state) plays which role. Distractors often stretch Terraform into jobs it does not do, such as managing software inside servers.
Keep in mind
• Keep the roles apart: providers translate resources into API calls, modules package reusable configuration, and state records what Terraform manages.
• When a stem talks about many clouds, the shared part is the workflow and language. Resource types still belong to each provider.
• Watch for in-guest tasks like installing packages or editing config files. Those point to configuration management tools rather than to Terraform.
Question 1 of 5
Which statement best describes how Terraform handles infrastructure across several cloud platforms?
Show answer
✅ Answer: C
Difficulty: applied · Topic: Terraform
One workflow, many providers
The use-cases page explains that multi-cloud brings fault-tolerance but also complexity because "each provider has its own interfaces, tools, and workflows. Terraform lets you use the same workflow to manage multiple providers and handle cross-cloud dependencies."
• You declare several provider requirements in one configuration.
• You write resources using each provider's resource types, such as aws_instance and azurerm_linux_virtual_machine.
• init, plan and apply work the same regardless of the platform.
The resource types are provider-specific, so Terraform gives a common workflow, not a common abstraction over all clouds.
Why each option works or fails
• ✗ A. Universal resource type: resource types are provider-specific, so moving a workload to another cloud means rewriting the resource blocks.
• ✗ B. Per-cloud installs: one CLI installs providers as plugins; no different command set is needed.
• ✓ C. Several providers in one workflow (correct): each provider handles its platform's API, while the configuration language and commands stay the same.
• ✗ D. Workload migration: Terraform provisions resources; it does not move running workloads during outages.
Question 2 of 5
A team lead says, "Terraform is our configuration manager, so we will use it to install packages and edit config files inside running servers." Which statement is accurate?
Show answer
✅ Answer: B
Difficulty: applied · Topic: Terraform
Provisioning versus configuration management
• Provisioning (what Terraform does): create, change and destroy infrastructure objects such as networks, instances, databases, buckets and DNS records by calling platform APIs.
• Configuration management (Ansible, Chef, Puppet, Salt): log in to a machine, or run an agent on it, to install packages, template files and manage services.
The two are complementary. A common pattern is that Terraform creates the instance (or an image-based fleet) and a configuration tool, or a pre-built machine image, supplies the software. Terraform's docs describe an immutable approach: replace infrastructure from a new definition instead of patching it in place.
Why each option works or fails
• ✗ A. Same category: the tools overlap at the edges, but one provisions infrastructure through APIs and the other converges the inside of machines.
• ✓ B. Provisioning focus (correct): Terraform builds the infrastructure objects, while package and file management inside a server is the usual job of a configuration manager or a baked image.
• ✗ C. On-premises only: the limitation is not about location; provisioning provider-managed resources works equally on public clouds and on-premises platforms.
• ✗ D. Replaces in-guest tools: providers expose platform APIs, not an operating system package manager, so Terraform does not take over that role.
Question 3 of 5
A central operations team receives many repetitive requests for the same kind of infrastructure. Which Terraform capability best supports a self-service model that still follows company standards?
Show answer
✅ Answer: A
Difficulty: applied · Topic: Terraform
Standardization through modules
Terraform supports "reusable configuration components called modules that define configurable collections of infrastructure, saving time and encouraging best practices". An operations team can publish a module (from the public registry, a private registry or a Git repository) that encodes standards such as tagging, encryption and network layout. Product teams use it by supplying inputs, and the result is consistent and compliant by construction. The use-cases page describes this "self-serve" model and notes that it replaces repetitive ticket handling.
Why each option works or fails
• ✓ A. Modules (correct): they encode the standard once and let other teams consume it with variables, which is self-service without lost consistency.
• ✗ B. A provider per team: providers integrate platforms; they are not the unit for packaging company standards, and they do not change CLI syntax.
• ✗ C. One shared file: concurrent edits to one file by every team invite conflicts and mistakes, and give no reusable standard.
• ✗ D. Ticket queue: this is the bottleneck the self-service pattern is designed to remove.
Question 4 of 5
Which statement about the language used to write Terraform configuration is accurate?
Show answer
✅ Answer: D
Difficulty: applied · Topic: Terraform
HCL
Terraform uses the HashiCorp Configuration Language (HCL) for files ending in .tf. It is declarative: blocks such as resource, variable and output describe objects and relationships, and the order of blocks in a file does not control execution order. References between resources create dependencies, from which Terraform builds its graph. A JSON-compatible alternative syntax (.tf.json) exists for machine-generated configuration.
Why each option works or fails
• ✗ A. Go programs: providers are written in Go, but practitioners write configuration in HCL with no compile step.
• ✗ B. Shell commands: configuration is not a script run top to bottom; it is a set of declarations whose order is derived from references.
• ✗ C. Binary only: saved plan files are binary artifacts, but the source of truth is human-readable configuration.
• ✓ D. HCL (correct): a readable declarative language, with a JSON variant for tools that generate configuration.
Question 5 of 5
Which statement about the role of Terraform providers in the IaC workflow is accurate?
Show answer
✅ Answer: B
Difficulty: applied · Topic: Terraform
Terraform core and providers
Terraform "creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API."
• Terraform core reads configuration, builds the graph and produces the plan.
• A provider is a separate plugin that knows one API: it defines the resource types and performs create, read, update and delete calls.
• Thousands of providers are published on the Terraform Registry, and you can write your own.
Why each option works or fails
• ✗ A. State files: state is a separate artifact that stores resource mappings; a provider is code, not data.
• ✓ B. Providers as plugins (correct): they implement a platform's API for Terraform, which is what lets one workflow reach AWS, Azure, Kubernetes or SaaS tools.
• ✗ C. Cloud accounts: an account belongs to the platform; the provider is the plugin that authenticates to it with credentials you supply.
• ✗ D. Reusable folders: that describes a module, which composes resources; a provider supplies the resource types themselves.
🎯 Takeaways
• Terraform standardizes the workflow across clouds via providers, not the resource definitions themselves.
• Terraform provisions infrastructure; it is not a configuration manager for software inside servers.
• Modules let one team codify a standard and many teams reuse it.
• Terraform configuration is declarative HCL (or JSON), with execution order inferred from dependencies.
• Providers are API-translating plugins; modules are packaged configuration; state is the record of managed objects.
📊 This set at a glance
Exam: TF-TA004 · 50 questions · 60 minutes
This set: 5 applied · 3 concept check, 1 comparison, 1 scenario
Topics: Terraform
🔗 More from this exam
• All TF-TA004 practice sets
• Every exam on this blog
📚 Keep studying TF-TA004
More TF-TA004 questions: https://hyunhp.github.io/cert-bank/#exam=TF-TA004
Study guide: https://hyunhp.github.io/cert-bank/study.html#exam=TF-TA004
These are original practice questions, not real exam questions, and cert-bank is not affiliated with any certification vendor.
Original practice questions written for this blog, not exam dumps.
Comments
Post a Comment