HashiCorp HashiCorp Certifications TA-002-P Questions & Answers

• Question 321:

  How does Terraform handle working with so many providers?

  A. Terraform ships with all of the plugins embedded in the Terraform binary.

  B. Terraform uses a plugin architecture for providers and only installs the provider plugins required by your configuration in the configuration's working directory.

  C. Terraform uses a plugin architecture for providers and only installs the provider plugins required by your configuration in a shared, system-wide plugins directory.

  D. Terraform allows you to select the providers you want to support during the Terraform installation process.

  Correct Answer: B

  Terraform is built on a plugin-based architecture. All providers and provisioners that are used in Terraform configurations are plugins, even the core types such as AWS and Heroku. Users of Terraform are able to write new plugins in order to support new functionality in Terraform.

• Question 322:

  Which one of the following will run echo 0 and echo 1 on a newly created host?

  A. provisioner "local-exec" { command = "echo 0" command = "echo 1" }

  B. provisioner "remote-exec" { inline = [ echo 0, echo 1 ] }

  C. provisioner "remote-exec" { command = "${echo 0}" command = "${echo 1}" }

  D. provisioner "remote-exec" { inline = [ "echo 0", "echo 1" ] }

  Correct Answer: D

  remote-exec Provisioner

  Example usage

  resource "aws_instance" "web" {

  # ...

  provisioner "remote-exec" {

  inline = [

  "puppet apply",

  "consul join ${aws_instance.web.private_ip}",

  ]

  }

  }

• Question 323:

  You have created 2 workspaces PROD and RQA. You have switched to RQA and provisioned RQA infrastructure from this workspace. Where is your state file stored?

  A. terraform.tfstate.d

  B. terraform.d

  C. terraform.tfstate.RQA

  D. terraform.tfstate

  Correct Answer: A

• Question 324:

  Provisioners should only be used as a last resort.

  A. False

  B. True

  Correct Answer: B

  Provisioners are a Last Resort Terraform includes the concept of provisioners as a measure of pragmatism, knowing that there will always be certain behaviors that can't be directly represented in Terraform's declarative model. However, they also add a considerable amount of complexity and uncertainty to Terraform usage. Firstly, Terraform cannot model the actions of provisioners as part of a plan because they can in principle take any action. Secondly, successful use of provisioners requires coordinating many more details than Terraform usage usually requires: direct network access to your servers, issuing Terraform credentials to log in, making sure that all of the necessary external software is installed, etc. The following sections describe some situations which can be solved with provisioners in principle, but where better solutions are also available. We do not recommend using provisioners for any of the use-cases described in the following sections. Even if your specific use-case is not described in the following sections, we still recommend attempting to solve it using other techniques first, and use provisioners only if there is no other option. https://www.terraform.io/docs/provisioners/index.html

• Question 325:

  Terraform has detailed logs which can be enabled by setting the _________ environmental variable.

  A. TF_TRACE

  B. TF_DEBUG

  C. TF_LOG

  D. TF_INFO

  Correct Answer: C

  Terraform has detailed logs that can be enabled by setting the TF_LOG environment variable to any value. This will cause detailed logs to appear on stderr. You can set TF_LOG to one of the log levels TRACE, DEBUG, INFO, WARN or ERROR to change the verbosity of the logs. TRACE is the most verbose and it is the default if TF_LOG is set to something other than a log level name.

  https://www.terraform.io/docs/internals/debugging.html

• Question 326:

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

  A. workspace

  B. backend

  C. state file

  D. metadata store

  Correct Answer: C

  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 327:

  What does terrafom plan do ?

  A. Create an execution plan by evaluating the difference between configuration file and state file.

  B. Performs a refresh, unless explicitly disabled, and then apply the changes that are necessary to achieve the desired state specified in the configuration files.

  C. Create an execution plan by evaluating the difference between configuration file and actual infrastructure.

  D. Checks whether the execution plan for a set of changes matches your expectations by making changes to real resources or to the state.

  Correct Answer: A

• Question 328:

  Which Terraform command will force a marked resource to be destroyed and recreated on the next apply?

  A. terraform fmt

  B. terraform destroy

  C. terraform taint

  D. terraform refresh

  Correct Answer: C

  The terraform taint command manually marks a Terraform-managed resource as tainted, forcing it to be destroyed and recreated on the next apply. This command will not modify infrastructure, but does modify the state file in order to mark a resource as tainted. Once a resource is marked as tainted, the next plan will show that the resource will be destroyed and recreated and the next apply will implement this change. Forcing the recreation of a resource is useful when you want a certain side effect of recreation that is not visible in the attributes of a resource. For example: re-running provisioners will cause the node to be different or rebooting the machine from a base image will cause new startup scripts to run. Note that tainting a resource for recreation may affect resources that depend on the newly tainted resource. For example, a DNS resource that uses the IP address of a server may need to be modified to reflect the potentially new IP address of a tainted server. The plan command will show this if this is the case. https://www.terraform.io/docs/commands/taint.html

• Question 329:

  The Terraform language does not support user-defined functions, and so only the functions built in to the language are available for use.

  A. False

  B. True

  Correct Answer: B

  https://www.terraform.io/docs/configuration/functions.html

• Question 330:

  While using generic git repository as a module source, which of the below options allows terraform to select a specific version or tag instead of selecting the HEAD.

  A. Append ref argument as module "vpc" { source = "git::https://example.com/vpc.git?ref=v1.2.0"}

  B. Append version argument as module "vpc" { source = "git::https://example.com/vpc.git?version=v1.2.0"}

  C. Append ref argument as module "vpc" { source = "git::https://example.com/vpc.git#ref=v1.2.0"}

  D. By default, Terraform will clone and use the default branch (referenced by HEAD) in the selected repository and you can not override this.

  Correct Answer: A

  By default, Terraform will clone and use the default branch (referenced by HEAD) in the selected repository. You can override this using the ref argument:

  module "vpc" {

  source = "git::https://example.com/vpc.git?ref=v1.2.0" }

  The value of the ref argument can be any reference that would be accepted by the git checkout command, including branch and tag names.

  https://www.terraform.io/docs/modules/sources.html