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

HashiCorp TERRAFORM-ASSOCIATE-003 Online Questions & Answers

• Question 331:

  As a member of the operations team, you need to run a script on a virtual machine created by Terraform. Which provisioned is best to use in your Terraform code?

  A. local-exec
  B. file
  C. null-exec
  D. remote-exec
  D. remote-exec

  ---

  Explanation

  https://www.terraform.io/language/resources/provisioners/remote-exec

• Question 332:

  terraform validate validates the syntax of Terraform files.

  A. True
  B. False
  A. True

  ---

  Explanation

  The terraform validate command validates the syntax and arguments of the Terraform configuration files.

  https://www.terraform.io/docs/cli/code/index.html

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

• Question 333:

  The current implementation of Terraform import can only import resources into the state. It does not generate configuration.

  A. False
  B. True
  B. True

  ---

  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/docs/import/index.html#currently-state-only

• Question 334:

  terraform apply will fail if you have not run terraform plan first to update the plan output.

  A. True
  B. False
  B. False

  ---

  Explanation

• Question 335:

  From the answers below, select the advantages of using Infrastructure as Code.

  A. Provide a codified workflow to develop customer-facing applications.
  B. Safely test modifications using a "dry run" before applying any actual changes.
  C. Easily integrate with application workflows (GitLab Actions, Azure DevOps, CI/CD tools).
  D. Easily change and update existing infrastructure.
  E. Provide reusable modules for easy sharing and collaboration.
  B. Safely test modifications using a "dry run" before applying any actual changes.
  C. Easily integrate with application workflows (GitLab Actions, Azure DevOps, CI/CD tools).
  D. Easily change and update existing infrastructure.
  E. Provide reusable modules for easy sharing and collaboration.

  ---

  Explanation

  Infrastructure as Code is not used to develop applications, but it can be used to help deploy or provision those applications to a public cloud provider or on-premises infrastructure. All of the others are benefits to using Infrastructure as Code over the traditional way of managing infrastructure, regardless if it's public cloud or on-premises.

• Question 336:

  When does Sentinel enforce policy logic during a Terraform Enterprise run?

  A. Before the plan phase
  B. During the plan phase
  C. Before the a apply phase
  D. After the apply phase
  C. Before the a apply phase

  ---

  Explanation

  "Enforcing policy checks on runs-Policies are checked when a run is performed, after the terraform plan but before it can be confirmed or the terraform apply is executed."

  Sentinel policies are checked after the plan stage of a Terraform run, but before it can be confirmed or the terraform apply is executed3. This allows you to enforce rules on your infrastructure before it is created or modified.

• Question 337:

  Any user can publish modules to the public Terraform Module Registry.

  A. True
  B. False
  A. True

  ---

  Explanation

  The Terraform Registry allows any user to publish and share modules. Published modules support versioning, automatically generate documentation, allow browsing version histories, show examples and READMEs, and more. Public

  modules are managed via Git and GitHub, and publishing a module takes only a few minutes. Once a module is published, releasing a new version of a module is as simple as pushing a properly formed Git tag.

  References: The information can be verified from the Terraform Registry documentation on Publishing Modules provided by HashiCorp Developer.

• Question 338:

  Terraform configuration can only import modules from the public registry.

  A. True
  B. False
  B. False

  ---

  Explanation

  Terraform configuration can import modules from various sources, not only from the public registry. Modules can be sourced from local file paths, Git repositories, HTTP URLs, Mercurial repositories, S3 buckets, and GCS buckets. Terraform supports a number of common conventions and syntaxes for specifying module sources, as documented in the [Module Sources] page.

  References: [Module Sources]

• Question 339:

  In order to reduce the time it takes to provision resources, Terraform uses parallelism. By default, how many resources will Terraform provision concurrently?

  A. 5
  B. 50
  C. 10
  D. 20
  C. 10

  ---

  Explanation

• Question 340:

  Terraform provisioners can be added to any resource block.

  A. True
  B. False
  A. True

  ---

  Explanation

  https://www.phillipsj.net/posts/introduction-to-terraform-provisioners/ As you continue learning about Terraform, you will start hearing about provisioners. Terraform provisioners can be created on any resource and provide a way to execute actions on local or remote machines. https://www.terraform.io/language/resources/provisioners/local-exec