TERRAFORM-ASSOCIATE-003
Q: 1
[Navigate Terraform State and Backends]
You have to initialize a Terraform backend before it can be configured.
Options
Q: 2
[Navigate Terraform State and Backends]
Terraform variables and outputs that set the description argument will store that description in the
state file.
Options
Q: 3
[Navigate Terraform State and Backends]
A Terraform output that sets the "sensitive" argument to true will not store that value in the state
file.
Options
Q: 4
[Interact with Terraform Modules]
You can develop a custom provider to manage its resources using Terraform.
Options
Q: 5
[Navigate Terraform State and Backends]
One remote backend configuration always maps to a single remote workspace.
Options
Q: 6
[Manage Terraform Resources and Providers]
Terraform providers are always installed from the Internet.
Options
Q: 7
[Interact with Terraform Modules]
Any user can publish modules to the public Terraform Module Registry.
Options
Q: 8
[Understand Terraform Basics and CLI]
You modified your Terraform configuration and run Terraform plan to review the changes.
Simultaneously, your teammate manually modified the infrastructure component you are working
on. Since you already ran terraform plan locally, the execution plan for terraform apply will be the
same.
Options
Q: 9
[Interact with Terraform Modules]
The public Terraform Module Registry is free to use.
Options
Q: 10
[Interact with Terraform Modules]
Using the terraform state rm command against a resource will destroy it.
Options
Question 1 of 10