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

HashiCorp TERRAFORM-ASSOCIATE-003 Online Questions & Answers

• Question 151:

  Given the Terraform configuration below, in which order will the resources be created?

  1.resource "aws_instance" "web_server"

  2.{

  3.ami = "ami-b374d5a5"

  4.instance_type = "t2.micro"

  5.}

  6.resource "aws_eip" "web_server_ip"

  7.{

  8.vpc = true instance = aws_instance.web_server.id

  9.

  }

  A. aws_eip will be created first aws_instance will be created second
  B. aws_eip will be created first aws_instance will be created second
  C. Resources will be created simultaneously
  D. aws_instance will be created first aws_eip will be created second
  D. aws_instance will be created first aws_eip will be created second

  ---

  Explanation

  Implicit and Explicit Dependencies

  By studying the resource attributes used in interpolation expressions, Terraform can automatically infer when one resource depends on another. In the example above, the reference to aws_instance.web_server.id creates an implicit

  dependency on the aws_instance named web_server.

  Terraform uses this dependency information to determine the correct order in which to create the different resources.

  # Example of Implicit Dependency

  resource "aws_instance" "web_server" {

  ami = "ami-b374d5a5"

  instance_type = "t2.micro"

  }

  resource "aws_eip" "web_server_ip" {

  vpc = true

  instance = aws_instance.web_server.id

  }

  In the example above, Terraform knows that the aws_instance must be created before the aws_eip.

  Implicit dependencies via interpolation expressions are the primary way to inform Terraform about these relationships, and should be used whenever possible. Sometimes there are dependencies between resources that are not visible to

  Terraform. The depends_on argument is accepted by any resource and accepts a list of resources to create explicit dependencies for. For example, perhaps an application we will run on our EC2 instance expects to use a specific Amazon S3

  bucket, but that dependency is configured inside the application code and thus not visible to Terraform. In that case, we can use depends_on to explicitly declare the dependency:

  # Example of Explicit Dependency

  # New resource for the S3 bucket our application will use.

  resource "aws_s3_bucket" "example" {

  bucket = "terraform-getting-started-guide"

  acl = "private"

  }

  # Change the aws_instance we declared earlier to now include "depends_on" resource "aws_instance" "example" {

  ami = "ami-2757f631"

  instance_type = "t2.micro"

  # Tells Terraform that this EC2 instance must be created only after the # S3 bucket has been created.

  depends_on = [aws_s3_bucket.example]

  }

  https://learn.hashicorp.com/terraform/getting-started/dependencies.html

• Question 152:

  You can migrate the Terraform backend but only if there are no resources currently being managed.

  A. False
  B. True
  A. False

  ---

  Explanation

  If you need to migrate to another backend, such as Terraform Cloud, so you can continue managing it. By migrating your Terraform state, you can hand off infrastructure without de-provisioning anything. https://www.terraform.io/docs/cloud/migrate/index.html

• Question 153:

  When multiple engineers start deploying infrastructure using the same state file, what is a feature of remote state storage that is critical to ensure the state doesn't become corrupt?

  A. Object Storage
  B. State Locking
  C. WorkSpaces
  D. Encryption
  B. State Locking

  ---

  Explanation

  If supported by your backend, Terraform will lock your state for all operations that could write state. This prevents others from acquiring the lock and potentially corrupting your state. State locking happens automatically on all operations that could write state. 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. Not all backends support locking. Please view the list of backend types for details on whether a backend supports locking or not.

  https://www.terraform.io/docs/state/locking.html

• Question 154:

  Jim has created several AWS resources from a single terraform configuration file. Someone from his team has manually modified one of the EC2 instance.

  Now to discard the manual change, Jim wants to destroy and recreate the EC2 instance. What is the best way to do it?

  A. terraform recreate
  B. terraform taint
  C. terraform destroy
  D. terraform refresh
  B. terraform taint

  ---

  Explanation

  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. This example will taint a single resource: $ terraform taint aws_security_group.allow_all The resource aws_security_group.allow_all in the module root has been marked as tainted. https://www.terraform.io/docs/commands/taint.html

• Question 155:

  You have a simple Terraform configuration containing one virtual machine (VM) in a cloud provider. You run terraform apply and the VM is created successfully. What will happen if you delete the VM using the cloud provider console, and run terraform apply again without changing any Terraform code?

  A. Terraform will remove the VM from state file
  B. Terraform will report an error
  C. Terraform will not make any changes
  D. Terraform will recreate the VM
  D. Terraform will recreate the VM

  ---

  Explanation

• Question 156:

  Environment variables can be used to set variables. The environment variables must be in the format "____"_. Select the correct prefix string from the following list.

  A. TF_CLI_ARGS
  B. TF_VAR
  C. TF_VAR_
  D. TF_VAR_ENV
  C. TF_VAR_

  ---

  Explanation

  Environment variables can be used to set variables. The environment variables must be in the format TF_VAR_name and this will be checked last for a value. For example:

  export TF_VAR_region=us-west-1

  export TF_VAR_ami=ami-049d8641

  export TF_VAR_alist='[1,2,3]'

  export TF_VAR_amap='{ foo = "bar", baz = "qux" }'

  https://www.terraform.io/docs/commands/environment-variables.html

• Question 157:

  What does terraform refresh modify?

  A. Your cloud infrastructure
  B. Your state file
  C. Your Terraform plan
  D. Your Terraform configuration
  B. Your state file

  ---

  Explanation

  The terraform refresh command reads the current settings from all managed remote objects and updates the Terraform state to match. Source: https://www.terraform.io/cli/commands/refresh

• Question 158:

  You have a simple Terraform configuration containing one virtual machine (VM) in a cloud provider. You run terraform apply and the VM is created successfully. What will happen if you terraform apply again immediately afterwards without changing any Terraform code?

  A. Terraform will terminate and recreate the VM
  B. Terraform will create another duplicate VM
  C. Terraform will apply the VM to the state file
  D. Nothing
  D. Nothing

  ---

  Explanation

• Question 159:

  Which of the following is not a valid Terraform string function?

  A. replace
  B. format
  C. join
  D. tostring
  D. tostring

  ---

  Explanation

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

• Question 160:

  As a member of an operations team that uses infrastructure as code (laC) practices, you are tasked with making a change to an infrastructure stack running in a public cloud. Which pattern would follow laC best practices for making a change?

  A. Make the change via the public cloud API endpoint
  B. Make the change programmatically via the public cloud CLI
  C. Submit a pull request and wait for an approved merge of the proposed changes
  D. Use the public cloud console to make the change after a database record has been approved
  E. Clone the repository containing your infrastructure code and then run the code
  C. Submit a pull request and wait for an approved merge of the proposed changes

  ---

  Explanation

  You do not need to use different Terraform commands depending on the cloud provider you use. Terraform commands are consistent across different providers, as they operate on the Terraform configuration files and state files, not on the provider APIs directly.