HashiCorp TERRAFORM-ASSOCIATE-003 Online Practice Questions and Exam Preparation

HashiCorp TERRAFORM-ASSOCIATE-003 Online Questions & Answers

• Question 531:

  During a terraform apply, a resource is successfully created but eventually fails during provisioning. What happens to the resource?

  A. The resource will be planned for destruction and recreation upon the next terraform apply
  B. Terraform will retry to provision again.
  C. The failure of provisioner will be ignored and it will not cause a failure to terraform apply
  D. The resource will be automatically destroyed.
  A. The resource will be planned for destruction and recreation upon the next terraform apply

  ---

  Explanation

  If a creation-time provisioner fails, the resource is marked as tainted. A tainted resource will be planned for destruction and recreation upon the next terraform apply. Terraform does this because a failed provisioner can leave a resource in a semi-configured state. Because Terraform cannot reason about what the provisioner does, the only way to ensure proper creation of a resource is to recreate it. This is tainting. You can change this behavior by setting the on_failure attribute, which is covered in detail below.

  https://www.terraform.io/docs/provisioners/index.html#creation-time-provisioners https://www.terraform.io/docs/provisioners/index.html#destroy-time-provisioners https://www.terraform.io/docs/provisioners/index.html#failure-behavior

• Question 532:

  A "backend" in Terraform determines how state is loaded and how an operation such as apply is executed. Which of the following is not a supported backend type?

  A. Terraform enterprise
  B. Consul
  C. Github
  D. S3
  E. Artifactory
  C. Github

  ---

  Explanation

  Github is not a supported backend type. https://www.terraform.io/docs/backends/types/index.html

• Question 533:

  You should run terraform fnt to rewrite all Terraform configurations within the current working directory to conform to Terraform-style conventions.

  A. True
  B. False
  A. True

  ---

  Explanation

  You should run terraform fmt to rewrite all Terraform configurations within the current working directory to conform to Terraform-style conventions. This command applies a subset of the Terraform language style conventions, along with other minor adjustments for readability. It is recommended to use this command to ensure consistency of style across different Terraform codebases. The command is optional, opinionated, and has no customization options, but it can help you and your team understand the code more quickly and easily.

  References: : Command: fmt : Using Terraform fmt Command to Format Your Terraform Code

• Question 534:

  When using constraint expressions to signify a version of a provider, which of the following are valid provider versions that satisfy the expression found in the following code snippet: (select two)

  1.terraform

  2.{

  3.required_providers

  4.{

  5.aws = "~> 1.2.0"

  6.}

  7.}

  A. 1.3.1
  B. 1.2.3
  C. 1.2.9
  D. 1.3.0
  B. 1.2.3
  C. 1.2.9

  ---

  Explanation

  As your Terraform usage becomes more advanced, there are some cases where you may need to modify the Terraform state. Rather than modify the state directly, the terraform state commands can be used in many cases instead. This command is a nested subcommand, meaning that it has further subcommands. https://www.terraform.io/docs/commands/state/index.html

• Question 535:

  The_________determines how Terraform creates, updates, or delete resources.

  A. Terraform configuration
  B. Terraform provisioner
  C. Terraform provider
  D. Terraform core
  C. Terraform provider

  ---

  Explanation

  This is what determines how Terraform creates, updates, or deletes resources, as it is responsible for understanding API interactions with some service and exposing resources and data sources based on that API.

• Question 536:

  You have provisioned some aws resources in your test environment through Terraform for a POC work. After the POC, now you want to destroy the resources but before destroying them you want to check what resources will be getting destroyed through terraform. what are the options of doing that? (Select TWO)

  A. Use terraform destroy command
  B. This is not possible
  C. Use terraform plan command
  D. Use terraform plan-destroy command.
  A. Use terraform destroy command
  D. Use terraform plan-destroy command.

  ---

  Explanation

  https://learn.hashicorp.com/terraform/getting-started/destroy

• Question 537:

  If a Terraform creation-time provisioner fails, what will occur by default?

  A. The resource will not be affected, but the provisioner will need to be applied again
  B. The resource will be destroyed
  C. The resource will be marked as "tainted"
  D. Nothing, provisioners will not show errors in the command line
  C. The resource will be marked as "tainted"

  ---

  Explanation

  If a creation-time provisioner fails, the resource is marked as tainted. A tainted resource will be planned for destruction and recreation upon the next terraform apply .

• Question 538:

  Terraform providers are always installed from the Internet.

  A. True
  B. False
  B. False

  ---

  Explanation

  Terraform providers are not always installed from the Internet. There are other ways to install provider plugins, such as from a local mirror or cache, from a local filesystem directory, or from a network filesystem. These methods can be useful for offline or air- gapped environments, or for customizing the installation process. You can configure the provider installation methods using the provider_installation block in the CLI configuration file.

  https://www.terraform.io/docs/language/providers/configuration.html

• Question 539:

  The terraform init command is always safe to run multiple times, to bring the working directory up to date with changes in the configuration. Though subsequent runs may give errors, this command will never delete your existing configuration or state.

  A. False
  B. True
  B. True

  ---

  Explanation

  https://www.terraform.io/docs/commands/init.html

• Question 540:

  You can access state stored with the local backend by using terraform_remote_state data source.

  A. True
  B. False
  B. False

  ---

  Explanation

  You cannot access state stored with the local backend by using the terraform_remote_state data source. The terraform_remote_state data source is used to retrieve the root module output values from some other Terraform configuration

  using the latest state snapshot from the remote backend. It requires a backend that supports remote state storage, such as S3, Consul, AzureRM, or GCS. The local backend stores the state file locally on the filesystem, which

  terraform_remote_state cannot access.

  References:

  Terraform documentation on terraform_remote_state data source: Terraform Remote State Data Source

  Example usage of remote state: Example Usage (remote Backend)