TERRAFORM-ASSOCIATE-003 practice question 4 of 30
[Understand Terraform Basics and CLI] You must use different Terraform commands depending on the cloud provider you use.
Full set: 226 questionsThe core Terraform Command Line Interface (CLI) commands and workflow are designed to be provider-agnostic. The standard commands—terraform init, terraform plan, terraform apply, and terraform destroy—remain the same regardless of which cloud provider (e.g., AWS, Azure, Google Cloud) you are targeting. The differentiation between providers is handled within the Terraform configuration files (.tf) through the declaration of a specific provider block and the use of provider-specific resource types (e.g., awsinstance vs. azurermvirtualmachine).
The "True" option is incorrect because it fundamentally misunderstands one of Terraform's key value propositions: providing a consistent, unified workflow to manage infrastructure across any platform. If the commands changed for each provider, this would eliminate the benefit of a common interface and add unnecessary complexity.
1. HashiCorp Developer - Core Terraform Workflow: The official documentation outlines a standard
three-stage workflow (Write
Plan
Apply) that is universal. It states
"This core workflow is the same for any project." The commands associated with this workflow (terraform init
terraform plan
terraform apply) are presented as the consistent method for managing any infrastructure.
Source: HashiCorp Developer
"Core Terraform Workflow"
https://developer.hashicorp.com/terraform/intro/core-workflow
Introduction section.
2. HashiCorp Developer - Providers: This documentation explains that providers are plugins Terraform uses to interact with cloud providers and other APIs. It clarifies that providers are specified within the configuration code itself using a provider block. This confirms that the provider-specific logic is handled within the configuration
not by altering the CLI commands used to execute the workflow.
Source: HashiCorp Developer
"Providers"
https://developer.hashicorp.com/terraform/language/providers
"Provider Requirements" section.
3. HashiCorp Developer - Command: apply: The documentation for the terraform apply command describes its function in a generic
provider-agnostic way: "The terraform apply command executes the actions proposed in a Terraform plan." There is no mention of provider-specific variations of the command itself. This holds true for all other core workflow commands.
Source: HashiCorp Developer
"Command: apply"
https://developer.hashicorp.com/terraform/cli/commands/apply
Usage section.
Keep practicing
Take the free TERRAFORM-ASSOCIATE-003 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other TERRAFORM-ASSOCIATE-003 practice questions
- Question 1[Understand Terraform Basics and CLI] If you update the version constraint in your Terraf…
- Question 2[Navigate Terraform State and Backends] Terraform variable names are saved in the state f…
- Question 3[Understand Terraform Basics and CLI] You modified your Terraform configuration and run T…
- Question 6[Understand Terraform Basics and CLI] terraform init creates an example main.tf file in t…
- Question 7[Understand Terraform Basics and CLI] terraform validate confirms that your infrastructur…
- Question 8[Interact with Terraform Modules] All modules published on the official Terraform Module …
