HashiCorp HashiCorp Certifications TA-002-P Questions & Answers

• Question 351:

  You just scaled your VM infrastructure and realized you set the count variable to the wrong value. You correct the value and save your change.

  What do you do next to make your infrastructure match your configuration?

  A. Run an apply and confirm the planned changes

  B. Inspect your Terraform state because you want to change it

  C. Reinitialize because your configuration has changed

  D. Inspect all Terraform outputs to make sure they are correct

  Correct Answer: A

• Question 352:

  You want to use terraform import to start managing infrastructure that was not originally provisioned through infrastructure as code. Before you can import the resource's current state, what must you do in order to prepare to manage these resources using Terraform?

  A. Run terraform refresh to ensure that the state file has the latest information for existing resources.

  B. Update the configuration file to include the new resources.

  C. Shut down or stop using the resources being imported so no changes are inadvertently missed.

  D. Modify the Terraform state file to add the new resources.

  Correct Answer: B

  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. The terraform import command is used to import existing infrastructure. To import a resource, first write a resource

  block for it in our configuration, establishing the name by which it will be known to Terraform.

  Example:

  resource "aws_instance" "import_example" {

  # ...instance configuration...

  }

  Now terraform import can be run to attach an existing instance to this resource configuration.

  $ terraform import aws_instance.import_example i-03efafa258104165f aws_instance.import_example: Importing from ID "i-03efafa258104165f"...

  aws_instance.import_example: Import complete!

  Imported aws_instance (ID: i-03efafa258104165f)

  aws_instance.import_example: Refreshing state... (ID: i-03efafa258104165f) Import successful!

  The resources that were imported are shown above. These resources are now in your Terraform state and will henceforth be managed by Terraform. This command locates the AWS instance with ID i-03efafa258104165f (which has been

  created outside Terraform) and attaches its existing settings, as described by the EC2 API, to the name aws_instance.import_example in the Terraform state.

• Question 353:

  terraform init initializes a sample main.tf file in the current directory.

  A. True

  B. False

  Correct Answer: B

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

• Question 354:

  How would you reference the "name" value of the second instance of this fictitious resource?

  

  A. element(aws_instance.web, 2)

  B. aws_instance.web[1].name

  C. aws_instance.web[1]

  D. aws_instance.web[2].name

  E. aws_instance.web.*.name

  Correct Answer: B

  Reference: https://www.terraform.io/docs/configuration-0-11/interpolation.html https://www.terraform.io/language/meta-arguments/count#referring-to-instances

• Question 355:

  Which of the following is not true of Terraform providers?

  A. Providers can be written by individuals

  B. Providers can be maintained by a community of users

  C. Some providers are maintained by HashiCorp

  D. Major cloud vendors and non-cloud vendors can write, maintain, or collaborate on Terraform providers

  E. None of the above

  Correct Answer: E

  https://registry.terraform.io/providers/hashicorp/google/latest-This provider is collaboratively maintained by the Google Terraform Team at Google and the Terraform team at HashiCorp https://www.terraform.io/language/providers

• Question 356:

  Which of the following is not a key principle of infrastructure as code?

  A. Versioned infrastructure

  B. Golden images

  C. Idempotence

  D. Self-describing infrastructure

  Correct Answer: B

  Reference: https://docs.microsoft.com/en-us/azure/devops/learn/what-is-infrastructure-as-code#:~:text=Idempotence%20is%20a%20principle%20of,of%20the%20environment's%20starting%20state.

• Question 357:

  You have provisioned some virtual machines (VMs) on Google Cloud Platform (GCP) using the gcloud command line tool. However, you are standardizing with Terraform and want to manage these VMs using Terraform instead. What are the two things you must do to achieve this? (Choose two.)

  A. Provision new VMs using Terraform with the same VM names

  B. Use the terraform import command for the existing VMs

  C. Write Terraform configuration for the existing VMs

  D. Run the terraform import-gcp command

  Correct Answer: BC

  You should create the equivalent configuration first, and then run import to load it on the state file.

• Question 358:

  In contrast to Terraform Open Source, when working with Terraform Enterprise and Cloud Workspaces, conceptually you could think about them as completely separate working directories.

  A. True

  B. False

  Correct Answer: A

  https://www.terraform.io/cloud-docs/workspaces "When run locally, Terraform manages each collection of infrastructure with a persistent working directory, which contains a configuration, state data, and variables. Since Terraform CLI uses content from the directory it runs in, you can organize infrastructure resources into meaningful groups by keeping their configurations in separate directories.

• Question 359:

  Your DevOps team is currently using the local backend for your Terraform configuration. You would like to move to a remote backend to begin storing the state file in a central location. Which of the following backends would not work?

  A. Amazon S3

  B. Artifactory

  C. Git

  D. Terraform Cloud

  Correct Answer: C

  https://www.terraform.io/cdktf/concepts/remote-backends https://docs.gitlab.com/ee/user/infrastructure/iac/terraform_state.html

• Question 360:

  What features stops multiple admins from changing the Terraform state at the same time?

  A. Version control

  B. Backend types

  C. Provider constraints

  D. State locking

  Correct Answer: D

  Somewhat ambiguous question however the key phrase is "feature". You need a remote backend first with a State Locking feature available to avoid this scenario. https://blog.gruntwork.io/how-to-manage-terraform-state-28f5697e68fa