Free Terraform-Associate-003 Actual Exam Questions - Question 4 Discussion
You must use different Terraform commands depending on the cloud provider you use.
Actually, B makes more sense since Terraform’s CLI commands like init and apply are the same regardless of the cloud provider. The provider differences are all in the code, not the commands.
B, commands stay the same; provider details go in config, not CLI.
B imo. The core Terraform commands don’t change whether you’re using AWS, Azure, or Google Cloud. The providers are just plugins that Terraform uses to talk to the different clouds, but you still run the same init, plan, apply commands. If anything, you might configure providers differently in your files, but the CLI stays consistent.
Option B, commands are consistent; provider differences are handled in config files.
I’m with the group on this—definitely B. Terraform’s core CLI commands like init, plan, and apply work the same way no matter the provider. You don’t have to learn a new set of commands for AWS or Azure. The provider differences come in the configuration files, not the CLI itself.
This one’s straightforward. Terraform CLI commands stay consistent regardless of the cloud provider you choose. So, it’s definitely B. They built Terraform to avoid switching up commands for each provider, which makes managing multi-cloud setups way easier.
B. Each provider uses the same Terraform CLI commands, no exceptions.
B imo. The whole point of Terraform is to have a consistent CLI no matter the provider, so you don’t need to learn new commands for each cloud.
It’s B. Terraform commands are the same regardless of the cloud provider you’re using.