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

HashiCorp TERRAFORM-ASSOCIATE-003 Online Questions & Answers

• Question 281:

  Choose the answer that correctly completes the sentence: _______backends support state locking.

  A. All
  B. No
  C. Only local
  D. Some
  D. Some

  ---

  Explanation

  Some backends support state locking, which prevents other users from modifying the state file while a Terraform operation is in progress. This prevents conflicts and data loss. Not all backends support this feature, and you can check the documentation for each backend type to see if it does.

• Question 282:

  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
  A. terraform.tfstate.d

  ---

  Explanation

• Question 283:

  What Terraform feature is shown in the example below?

  A. conditional expression
  B. local values
  C. dynamic block
  D. data source
  C. dynamic block

  ---

  Explanation

• Question 284:

  What are some of the features of Terraform state? (select three)

  A. inspection of cloud resources
  B. determining the correct order to destroy resources
  C. mapping configuration to real-world resources
  D. increased performance
  C. mapping configuration to real-world resources
  D. increased performance

  ---

  Explanation

• Question 285:

  How do you specify a module's version when publishing it to the public Terraform Module Registry?

  A. The module's configuration page on the Terraform Module Registry
  B. Terraform Module Registry does not support versioning modules
  C. The release tags in the associated repo
  D. The module's Terraform code
  C. The release tags in the associated repo

  ---

  Explanation

  https://www.terraform.io/registry/modules/publish

• Question 286:

  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.
  A. Append ref argument as module "vpc" { source = "git::https://example.com/vpc.git?ref=v1.2.0"}

  ---

  Explanation

  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

• Question 287:

  The canonical format may change in minor ways between Terraform versions, so after upgrading Terraform it is recommended to proactively run.

  A. terraform fmt
  B. terraform init
  C. terraform validate
  D. terraform plan
  A. terraform fmt

  ---

  Explanation

• Question 288:

  Dawn has created the below child module. Without changing the module, can she override the instance_type from t2.micro to t2.large form her code while calling this module?

  1.resource "aws_instance" "myec2"

  2.{

  3.ami = "ami-082b5a644766e0e6f"

  4.instance_type = "t2.micro

  5.}

  A. YES
  B. No
  B. No

  ---

  Explanation

  As the instance_type is hard-coded in source module, you will not be able to change its value from destination module. Instead of hard-coding you should use variable with default values.

• Question 289:

  Refer below code where pessimistic constraint operator has been used to specify a version of a provider.

  terraform { required_providers { aws = "~> 1.1.0" }}

  Which of the following options are valid provider versions that satisfy the above constraint? (select two)

  A. 1.1.1
  B. 1.2.9
  C. 1.1.8
  D. 1.2.0
  A. 1.1.1
  C. 1.1.8

  ---

  Explanation

  Pessimistic constraint operator, constraining both the oldest and newest version allowed. For example, ~> 0.9 is equivalent to >= 0.9, < 1.0, and ~> 0.8.4, is equivalent to >= 0.8.4, < 0.9

• Question 290:

  Hanah is writing a terraform configuration with nested modules, there are multiple places where she has to use the same conditional expression but she wants to avoid repeating the same values or expressions multiple times in the configuration,. What is a better approach to dealing with this?

  A. Expressions
  B. Local Values
  C. Variables
  D. Functions
  B. Local Values

  ---

  Explanation

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