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

HashiCorp TERRAFORM-ASSOCIATE-003 Online Questions & Answers

• Question 431:

  After executing a terraform apply, you notice that a resource has a tilde (~) next to it. What does this infer?

  A. The resource will be updated in place.
  B. The resource will be created.
  C. Terraform can't determine how to proceed due to a problem with the state file.
  D. The resource will be destroyed and recreated.
  A. The resource will be updated in place.

  ---

  Explanation

  The prefix-/+ means that Terraform will destroy and recreate the resource, rather than updating it in-place.

  The prefix ~ means that some attributes and resources can be updated in-place.

  $ terraform apply

  aws_instance.example: Refreshing state... [id=i-0bbf06244e44211d1] An execution plan has been generated and is shown below. Resource actions are indicated with the following symbols:

  -/+ destroy and then create replacement

  Terraform will perform the following actions:

  # aws_instance.example must be replaced

  -/+ resource "aws_instance" "example" {

  ~ ami = "ami-2757f631"-> "ami-b374d5a5" # forces replacement ~ arn = "arn:aws:ec2:us-east-1:130490850807:instance/i-0bbf06244e44211d1"-> (known after apply) ~ associate_public_ip_address = true-> (known after apply) ~

  availability_zone = "us-east-1c"-> (known after apply) ~ cpu_core_count = 1-> (known after apply) ~ cpu_threads_per_core = 1-> (known after apply)

  -disable_api_termination = false-> null

  -ebs_optimized = false-> null

  get_password_data = false

  +

  host_id = (known after apply)

  ~ id = "i-0bbf06244e44211d1"-> (known after apply) ~ instance_state = "running"-> (known after apply) instance_type = "t2.micro" ~ ipv6_address_count = 0-> (known after apply)

  ~ ipv6_addresses = []-> (known after apply)

  +

  key_name = (known after apply)

  -monitoring = false-> null

  +

  network_interface_id = (known after apply)

  +

  password_data = (known after apply)

  +

  placement_group = (known after apply)

  ~ primary_network_interface_id = "eni-0f1ce5bdae258b015"-> (known after apply) ~ private_dns = "ip-172-31-61-141.ec2.internal"-> (known after apply) ~ private_ip = "172.31.61.141"-> (known after apply) ~ public_dns = "ec2-54-166-19244.compute-1.amazonaws.com"-> (known after apply) ~ public_ip = "54.166.19.244"-> (known after apply) ~ security_groups = [

  -"default",

  ]-> (known after apply)

  source_dest_check = true

  ~ subnet_id = "subnet-1facdf35"-> (known after apply) ~ tenancy = "default"-> (known after apply)

  ~ volume_tags = {}-> (known after apply)

  ~ vpc_security_group_ids = [

  -"sg-5255f429",

  ]-> (known after apply)

  -credit_specification {

  -cpu_credits = "standard"-> null

  }

  +

  ebs_block_device {

  +

  delete_on_termination = (known after apply)

  +

  device_name = (known after apply)

  +

  encrypted = (known after apply)

  +

  iops = (known after apply)

  +

  snapshot_id = (known after apply)

  +

  volume_id = (known after apply)

  +

  volume_size = (known after apply)

  +

  volume_type = (known after apply)

  }

  +

  ephemeral_block_device {

  +

  device_name = (known after apply)

  +

  no_device = (known after apply)

  +

  virtual_name = (known after apply)

  }

  +

  network_interface {

  +

  delete_on_termination = (known after apply)

  +

  device_index = (known after apply)

  +

  network_interface_id = (known after apply)

  }

  ~ root_block_device {

  ~ delete_on_termination = true-> (known after apply) ~ iops = 100-> (known after apply)

  ~ volume_id = "vol-0079e485d9e28a8e5"-> (known after apply) ~ volume_size = 8-> (known after apply)

  ~ volume_type = "gp2"-> (known after apply)

  }

  }

  Plan: 1 to add, 0 to change, 1 to destroy.

• Question 432:

  Which of the following is true about terraform apply? (Choose two.)

  A. It only operates on infrastructure defined in the current working directory or workspace
  B. You must pass the output of a terraform plan command to it
  C. Depending on provider specification, Terraform may need to destroy and recreate your infrastructure resources
  D. By default, it does not refresh your state file to reflect current infrastructure configuration
  E. You cannot target specific resources for the operation
  A. It only operates on infrastructure defined in the current working directory or workspace
  C. Depending on provider specification, Terraform may need to destroy and recreate your infrastructure resources

  ---

  Explanation

  https://www.terraform.io/cli/run

• Question 433:

  Which Terraform command will check and report errors within modules, attribute names, and value types to make sure they are syntactically valid and internally consistent?

  A. terraform validate
  B. terraform format
  C. terraform fmt
  D. terraform show
  A. terraform validate

  ---

  Explanation

  The terraform validate command validates the configuration files in a directory, referring only to the configuration and not accessing any remote services such as remote state, provider APIs, etc. Validate runs checks that verify whether a

  configuration is syntactically valid and internally consistent, regardless of any provided variables or existing state. It is thus primarily useful for general verification of reusable modules, including the correctness of attribute names and value

  types.

  It is safe to run this command automatically, for example as a post-save check in a text editor or as a test step for a re-usable module in a CI system.

• Question 434:

  A module block is shown in the Exhibit space of this page. When you use a module block to reference a module from the Terraform Registry such as the one in the example, how do you specify version 1.0.0 of the module?

  A. Append ?ref=v1.0.0 argument to the source path.
  B. You cannot. Modules stored on the public Terraform Registry do not support versioning.
  C. Add a version = "1.0.0" attribute to the module block.
  D. Nothing. Modules stored on the public Terraform module Registry always default to version 1.0.0.
  C. Add a version = "1.0.0" attribute to the module block.

  ---

  Explanation

  Module Versioning: To specify a version in a module block for modules in the Terraform Registry, you add the version attribute, e.g., version = "1.0.0". Terraform Registry Support: The public registry supports versioning by enabling semantic

  constraints, allowing users to define specific versions compatible with their infrastructure requirements.

  Refer to the module versioning documentation in Terraform's official registry guide.

• Question 435:

  Taint the resource "aws_instance" "baz" resource that lives in module bar which lives in module foo.

  A. terraform taint module.foo.module.bar.baz
  B. terraform taint module.foo.bar.aws_instance.baz
  C. terraform taint module.foo.module.bar.aws_instance.baz
  D. terraform taint foo.bar.aws_instance.baz
  C. terraform taint module.foo.module.bar.aws_instance.baz

  ---

  Explanation

  Check resource addressing https://www.terraform.io/docs/internals/resource-addressing.html

• Question 436:

  You have to initialize a Terraform backend before it can be configured.

  A. True
  B. False
  B. False

  ---

  Explanation

  You can configure a backend in your Terraform code before initializing it. Initializing a backend will store the state file remotely and enable features like locking and workspaces.

  References: [Terraform Backends]

• Question 437:

  When should you use the force-unlock command?

  A. You see a status message that you cannot acquire the lock
  B. You have a high priority change
  C. Automatic unlocking failed
  D. Your apply failed due to a state lock
  C. Automatic unlocking failed

  ---

  Explanation

  You should use the force-unlock command when automatic unlocking failed. Terraform will lock your state for all operations that could write state, such as plan, apply, or destroy. This prevents others from acquiring the lock and potentially corrupting your state. State locking happens automatically on all operations that could write state and you won't see any message that it is happening. If state locking fails, Terraform will not continue. You can disable state locking for most commands with the -lock flag but it is not recommended. If acquiring the lock is taking longer than expected, Terraform will output a status message. If Terraform doesn't output a message, state locking is still occurring if your backend supports it. Terraform has a force-unlock command to manually unlock the state if unlocking failed. Be very careful with this command. If you unlock the state when someone else is holding the lock it could cause multiple writers. Force unlock should only be used to unlock your own lock in the situation where automatic unlocking failed. To protect you, the force-unlock command requires a unique lock ID. Terraform will output this lock ID if unlocking fails. This lock ID acts as a nonce, ensuring that locks and unlocks target the correct lock. The other situations are not valid reasons to use the force-unlock command. You should not use the force-unlock command if you have a high priority change, if apply failed due to a state lock, or if you see a status message that you cannot acquire the lock. These situations indicate that someone else is holding the lock and you should wait for them to finish their operation or contact them to resolve the issue. Using the force-unlock command in these cases could result in data loss or inconsistency. Be very careful with this command. If you unlock the state when someone else is holding the lock it could cause multiple writers. Force unlock should only be used to unlock your own lock in the situation where automatic unlocking failed. Source: https://www.terraform.io/language/state/locking https://www.terraform.io/cli/commands/force-unlock

• Question 438:

  Multiple providers can be declared within a single Terraform configuration file.

  A. True
  B. False
  A. True

  ---

  Explanation

  You can optionally define multiple configurations for the same provider, and select which one to use on a per-resource or per-module basis. The primary reason for this is to support multiple regions for a cloud platform; other examples include

  targeting multiple Docker hosts, multiple Consul hosts, etc.

  To include multiple configurations for a given provider, include multiple provider blocks with the same provider name, but set the alias meta-argument to an alias name to use for each additional configuration.

  For Example

  # The default provider configuration

  provider "aws" {

  region = "us-east-1"

  }

  # Additional provider configuration for west coast region provider "aws" {

  alias = "west"

  region = "us-west-2"

  }

  The provider block without alias set is known as the default provider configuration. When alias is set, it creates an additional provider configuration. For providers that have no required configuration arguments, the implied empty configuration

  is considered to be the default provider configuration.

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

• Question 439:

  You want to define a single input variable to capture configuration values for a server. The values must represent memory as a number, and the server name as a string. Which variable type could you use for this input?

  A. List
  B. Object
  C. Map
  D. Terraform does not support complex input variables of different types
  B. Object

  ---

  Explanation

  This is the variable type that you could use for this input, as it can store multiple attributes of different types within a single value. The other options are either invalid or incorrect for this use case.

• Question 440:

  In Terraform Enterprise, a workspace can be mapped to how many VCS repos?

  A. 5
  B. 2
  C. 3
  D. 1
  D. 1

  ---

  Explanation

  A workspace can only be configured to a single VCS repo, however, multiple workspaces can use the same repo. https://www.terraform.io/docs/cloud/workspaces/vcs.html