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

HashiCorp TERRAFORM-ASSOCIATE-003 Online Questions & Answers

• Question 231:

  By default, a defined provisioner is a creation-time provisioner.

  A. True
  B. False
  A. True

  ---

  Explanation

  https://www.terraform.io/docs/provisioners/index.html

• Question 232:

  Which of these statements about Terraform Cloud workspaces is false?

  A. They have role-based access controls
  B. You must use the CLI to switch between workspaces
  C. Plans and applies can be triggered via version control system integrations
  D. They can securely store cloud credentials
  B. You must use the CLI to switch between workspaces

  ---

  Explanation

  The statement that you must use the CLI to switch between workspaces is false. Terraform Cloud workspaces are different from Terraform CLI workspaces. Terraform Cloud workspaces are required and represent all of the collections of infrastructure in an organization. They are also a major component of role-based access in Terraform Cloud. You can grant individual users and user groups permissions for one or more workspaces that dictate whether they can manage variables, perform runs, etc. You can create, view, and switch between Terraform Cloud workspaces using the Terraform Cloud UI, the Workspaces API, or the Terraform Enterprise Provider5. Terraform CLI workspaces are optional and allow you to create multiple distinct instances of a single configuration within one working directory. They are useful for creating disposable environments for testing or experimenting without affecting your main or production environment. You can create, view, and switch between Terraform CLI workspaces using the terraform workspace command6. The other statements about Terraform Cloud workspaces are true. They have role-based access controls that allow you to assign permissions to users and teams based on their roles and responsibilities. You can create and manage roles using the Teams API or the Terraform Enterprise Provider. Plans and applies can be triggered via version control system integrations that allow you to link your Terraform Cloud workspaces to your VCS repositories. You can configure VCS settings, webhooks, and branch tracking to automate your Terraform Cloud workflow. They can securely store cloud credentials as sensitive variables that are encrypted at rest and only decrypted when needed. You can manage variables using the Terraform Cloud UI, the Variables API, or the Terraform Enterprise Provider.

  References: [Workspaces], [Terraform CLI Workspaces], [Teams and Organizations], [VCS Integration]8, [Variables]

• Question 233:

  Why does this backend configuration not follow best practices?

  

  A. You should not store credentials in Terraform Configuration
  B. You should use the local enhanced storage backend whenever possible
  C. An alias meta-argument should be included in backend blocks whenever possible
  D. The backend configuration should contain multiple credentials so that more than one user can execute terraform plan and terraform apply
  A. You should not store credentials in Terraform Configuration

  ---

  Explanation

  This is a bad practice, as it exposes your credentials to anyone who can access your configuration files or state files. You should use environment variables, credential files, or other mechanisms to provide credentials to Terraform.

• Question 234:

  How is terraform import run?

  A. As a part of terraform init
  B. As a part of terraform plan
  C. As a part of terraform refresh
  D. By an explicit call
  E. All of the above
  D. By an explicit call

  ---

  Explanation

  "The current implementation of Terraform import can only import resources into the state. It does not generate configuration. A future version of Terraform will also generate configuration. Because of this, prior to running terraform import it is necessary to write manually a resource configuration block for the resource, to which the imported object will be mapped. While this may seem tedious, it still gives Terraform users an avenue for importing existing resources." https:// www.terraform.io/cli/import/usage

• Question 235:

  Which of the following is not valid source path for specifying a module?

  A. source = "./modulelversion=v1.0.0"
  B. source = "github.com/hashicorp/example?ref=v1.0.0"
  C. source = "./module"
  D. source = "hashicorp/consul/aws"
  A. source = "./modulelversion=v1.0.0"

  ---

  Explanation

• Question 236:

  Terraform must track metadata such as resource dependencies. Where is this data stored?

  A. workspace
  B. backend
  C. state file
  D. metadata store
  C. state file

  ---

  Explanation

  Terraform typically uses the configuration to determine dependency order. However, when you delete a resource from a Terraform configuration, Terraform must know how to delete that resource. Terraform can see that a mapping exists for a resource not in your configuration and plan to destroy. However, since the configuration no longer exists, the order cannot be determined from the configuration alone. To ensure correct operation, Terraform retains a copy of the most recent set of dependencies within the state. Now Terraform can still determine the correct order for destruction from the state when you delete one or more items from the configuration. https://www.terraform.io/docs/state/purpose.html#metadata

• Question 237:

  A user has created three workspaces using the command line-prod, dev, and test. The user wants to create a fourth workspace named stage. Which command will the user execute to accomplish this?

  A. terraform workspace new stage
  B. terraform workspace-new stage
  C. terraform workspace-create stage
  D. terraform workspace create stage
  A. terraform workspace new stage

  ---

  Explanation

  The terraform workspace new command is used to create a new workspace.

  https://www.terraform.io/docs/commands/workspace/new.html

• Question 238:

  The following is a snippet from a Terraform configuration file:

  Which, when validated, results in the following error:

  Fill in the blank in the error message with the correct string from the list below.

  A. version
  B. multi
  C. label
  D. alias
  D. alias

  ---

  Explanation

  https://www.terraform.io/docs/configuration/providers.html#alias-multiple-providerinstances

• Question 239:

  When using Terraform to deploy resources into Azure, which scenarios are true regarding state files? (Choose two.)

  A. When a change is made to the resources via the Azure Cloud Console, the changes are recorded in a new state file
  B. When a change is made to the resources via the Azure Cloud Console, Terraform will update the state file to reflect them during the next plan or apply
  C. When a change is made to the resources via the Azure Cloud Console, the current state file will not be updated
  D. When a change is made to the resources via the Azure Cloud Console, the changes are recorded in the current state file
  B. When a change is made to the resources via the Azure Cloud Console, Terraform will update the state file to reflect them during the next plan or apply
  C. When a change is made to the resources via the Azure Cloud Console, the current state file will not be updated

  ---

  Explanation

• Question 240:

  Which of the following Terraform files should be ignored by Git when committing code to a repo? (select Three)

  A. Files named exactly terraform.tfvars or terraform.tfvars.json.
  B. Any files with names ending in .auto.tfvars or .auto.tfvars.json.
  C. input.tf
  D. terraform.tfstate
  E. output.tf
  A. Files named exactly terraform.tfvars or terraform.tfvars.json.
  B. Any files with names ending in .auto.tfvars or .auto.tfvars.json.
  D. terraform.tfstate

  ---

  Explanation

  The .gitignore file should be configured to ignore Terraform files that either contain sensitive data or are not required to save. Terraform state (terraform.tfstate) can contain sensitive data, depending on the resources in use and your definition of "sensitive." The state contains resource IDs and all resource attributes. For resources such as databases, this may contain initial passwords. When using local state, state is stored in plain-text JSON files. The terraform.tfvars file may contain sensitive data, such as passwords or IP addresses of an environment that you may not want to share with others.