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

HashiCorp TERRAFORM-ASSOCIATE-003 Online Questions & Answers

• Question 131:

  Terraform will sync all resources in state by default for every plan and apply, hence for larger infrastructures this can slow down terraform plan and terraform apply commands?

  A. False
  B. True
  B. True

  ---

  Explanation

  For small infrastructures, Terraform can query your providers and sync the latest attributes from all your resources. This is the default behavior of Terraform: for every plan and apply, Terraform will sync all resources in your state. For larger infrastructures, querying every resource is too slow. Many cloud providers do not provide APIs to query multiple resources at once, and the round trip time for each resource is hundreds of milliseconds. On top of this, cloud providers almost always have API rate limiting so Terraform can only request a certain number of resources in a period of time. Larger users of Terraform make heavy use of the-refresh=false flag as well as the-target flag in order to work around this. In these scenarios, the cached state is treated as the record of truth. https://www.terraform.io/docs/state/purpose.html

• Question 132:

  Terraform variable names are saved in the state file.

  A. True
  B. False
  B. False

  ---

  Explanation

  Terraform stores information about your infrastructure in a state file. This state file keeps track of resources created by your configuration and maps them to real-world resources. https://learn.hashicorp.com/tutorials/terraform/state-cli

• Question 133:

  Where can Terraform not load a provider from?

  A. Plugins directory
  B. Provider plugin cache
  C. Official HashrCorp distribution on releases, hashicorp.com
  D. Source code
  D. Source code

  ---

  Explanation

  This is where Terraform cannot load a provider from, as it requires a compiled binary file that implements the provider protocol. You can load a provider from a plugins directory, a provider plugin cache, or the official HashiCorp distribution on releases.hashicorp.com.

• Question 134:

  terraform validate validate validates that your infrastructure matches the Terraform state file.

  A. True
  B. False
  B. False

  ---

  Explanation

  The terraform validate command validates the configuration files in a directory, referring only to the configuration and not accessing any remote services such as remote state, provider APIs, etc. Validate runs checks that verify whether a

  configuration is syntactically valid and internally consistent, regardless of any provided variables or existing state. It is thus primarily useful for general verification of reusable modules, including correctness of attribute names and value types.

  Source:

  https://www.terraform.io/cli/commands/validate

• Question 135:

  You need to deploy resources into two different cloud regions in the same Terraform configuration. To do that, you declare multiple provider configurations as follows:

  

  What meta-argument do you need to configure in a resource block to deploy the resource to the "us-west-2" AWS region?

  A. alias = west
  B. provider = west
  C. provider = aws.west
  D. alias = aws.west
  C. provider = aws.west

  ---

  Explanation

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

• Question 136:

  Which of the following can you do with terraform plan? Choose two correct answers.

  A. View the execution plan and check if the changes match your expectations
  B. Schedule Terraform to run at a planned time in the future
  C. Execute a plan in a different workspace
  D. Save a generated execution plan to apply later
  A. View the execution plan and check if the changes match your expectations
  D. Save a generated execution plan to apply later

  ---

  Explanation

  https://learn.hashicorp.com/tutorials/terraform/plan

• Question 137:

  When does terraform apply reflect changes in the cloud environment?

  A. Immediately
  B. However long it takes the resource provider to fulfill the request
  C. After updating the state file
  D. Based on the value provided to the-refresh command line argument
  E. None of the above
  B. However long it takes the resource provider to fulfill the request

  ---

  Explanation

• Question 138:

  Which of these ate secure options for storing secrets for connecting to a Terraform remote backend? Choose two correct answers.

  A. A variable file
  B. Defined in Environment variables
  C. Inside the backend block within the Terraform configuration
  D. Defined in a connection configuration outside of Terraform
  B. Defined in Environment variables
  D. Defined in a connection configuration outside of Terraform

  ---

  Explanation

  Environment variables and connection configurations outside of Terraform are secure options for storing secrets for connecting to a Terraform remote backend. Environment variables can be used to set values for input variables that contain secrets, such as backend access keys or tokens. Terraform will read environment variables that start with TF_VAR_ and match the name of an input variable. For example, if you have an input variable called backend_token, you can set its value with the environment variable TF_VAR_backend_token1. Connection configurations outside of Terraform are files or scripts that provide credentials or other information for Terraform to connect to a remote backend. For example, you can use a credentials file for the S3 backend2, or a shell script for the HTTP backend3. These files or scripts are not part of the Terraform configuration and can be stored securely in a separate location. The other options are not secure for storing secrets. A variable file is a file that contains values for input variables. Variable files are usually stored in the same directory as the Terraform configuration or in a version control system. This exposes the secrets to anyone who can access the files or the repository. You should not store secrets in variable files1. Inside the backend block within the Terraform configuration is where you specify the type and settings of the remote backend. The backend block is part of the Terraform configuration and is usually stored in a version control system. This exposes the secrets to anyone who can access the configuration or the repository. You should not store secrets in the backend block4.

  References: [Terraform Input Variables]1, [Backend Type: s3]2, [Backend Type: http]3, [Backend Configuration]4

• Question 139:

  Which of the following value will be accepted for my_var?

  1.variable "my_var"

  2.{

  3.type = string

  4.}

  A. 15
  B. "15"
  C. Both A and B
  D. None of the above
  C. Both A and B

  ---

  Explanation

  The Terraform language will automatically convert number and bool values to string values when needed, and vice-versa as long as the string contains a valid representation of a number or boolean value. Example

  *

  true converts to "true", and vice-versa

  *

  false converts to "false", and vice-versa

  *

  15 converts to "15", and vice-versa Where possible, Terraform automatically converts values from one type to another in order to produce the expected type. If this isn't possible, Terraform will produce a type mismatch error and you must update the configuration with a more suitable expression. https://www.terraform.io/docs/configuration/expressions.html#type-conversion

• Question 140:

  Which of the following type of variable allows multiple values of several distinct types to be grouped together as a single value?

  A. Map
  B. Object
  C. Tuple
  D. List
  B. Object
  C. Tuple

  ---

  Explanation

  Structural type of variable allows multiple values of several distinct types to be grouped together as a single value. They require a schema as an argument, to specify which types are allowed for which elements. https://www.terraform.io/docs/configuration/types.html