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

HashiCorp TERRAFORM-ASSOCIATE-003 Online Questions & Answers

• Question 411:

  What does state looking accomplish?

  A. Prevent accidental Prevent accident deletion of the state file
  B. Blocks Terraform commands from modifying, the state file
  C. Copies the state file from memory to disk
  D. Encrypts any credentials stored within the state file
  B. Blocks Terraform commands from modifying, the state file

  ---

  Explanation

  This is what state locking accomplishes, by preventing other users from modifying the state file while a Terraform operation is in progress. This prevents conflicts and data loss.

• Question 412:

  resource "aws_s3_bucket" "example" { bucket = "my-test-s3-terraform-bucket" ...} resource "aws_iam_role" "test_role" { name = "test_role" ...}

  Due to the way that the application code is written , the s3 bucket must be created before the test role is created , otherwise there will be a problem. How can you ensure that?

  A. This will already be taken care of by terraform native implicit dependency. Nothing else needs to be done from your end.
  B. Add explicit dependency using depends_on . This will ensure the correct order of resource creation.
  C. Create 2 separate terraform config scripts , and run them one by one , 1 for s3 bucket , and another for IAM role , run the S3 bucket script first.
  D. This is not possible to control in terraform . Terraform will take care of it in a native way , and create a dependency graph that is best suited for the parallel resource creation.
  B. Add explicit dependency using depends_on . This will ensure the correct order of resource creation.

  ---

  Explanation

  Use the depends_on meta-argument to handle hidden resource dependencies that Terraform can't automatically infer.

  Explicitly specifying a dependency is only necessary when a resource relies on some other resource's behavior but doesn't access any of that resource's data in its arguments.

• Question 413:

  A user runs terraform init on their RHEL based server and per the output, two provider plugins are downloaded: $ terraform init

  Initializing the backend...

  Initializing provider plugins...

  -Checking for available provider plugins...

  -Downloading plugin for provider "aws" (hashicorp/aws) 2.44.0...

  -Downloading plugin for provider "random" (hashicorp/random) 2.2.1...

  Terraform has been successfully initialized! Where are these plugins downloaded to?

  A. The .terraform.plugins directory in the directory terraform init was executed in.
  B. The .terraform/plugins directory in the directory terraform init was executed in.
  C. /etc/terraform/plugins
  D. The .terraform.d directory in the directory terraform init was executed in.
  B. The .terraform/plugins directory in the directory terraform init was executed in.

  ---

  Explanation

• Question 414:

  Your DevOps team is currently using the local backend for your Terraform configuration. You would like to move to a remote backend to begin storing the state file in a central location. Which of the following backends would not work?

  A. Amazon S3
  B. Artifactory
  C. Git
  D. Terraform Cloud
  C. Git

  ---

  Explanation

  This is not a valid backend for Terraform, as it does not support locking or versioning of state files4. The other options are valid backends that can store state files in a central location. https://www.terraform.io/cdktf/concepts/remote-backends https://docs.gitlab.com/ee/user/infrastructure/iac/terraform_state.html

• Question 415:

  Why is it a good idea to declare the required version of a provider in a Terraform configuration file?

  1.terraform

  2.{

  3.required_providers

  4.{

  5.aws = "~> 1.0"

  6.}

  7.}

  A. To remove older versions of the provider.
  B. To ensure that the provider version matches the version of Terraform you are using.
  C. Providers are released on a separate schedule from Terraform itself; therefore a newer version could introduce breaking changes.
  D. To match the version number of your application being deployed via Terraform.
  C. Providers are released on a separate schedule from Terraform itself; therefore a newer version could introduce breaking changes.

  ---

  Explanation

• Question 416:

  Terraform configuration (including any module references) can contain only one Terraform provider type.

  A. True
  B. False
  B. False

  ---

  Explanation

  Terraform configuration (including any module references) can contain more than one Terraform provider type. Terraform providers are plugins that Terraform uses to interact with various cloud services and other APIs. A Terraform configuration can use multiple providers to manage resources across different platforms and services. For example, a configuration can use the AWS provider to create a virtual machine, the Cloudflare provider to manage DNS records, and the GitHub provider to create a repository. Terraform supports hundreds of providers for different use cases and scenarios.

  References: [Providers], [Provider Requirements], [Provider Configuration]

• Question 417:

  What are the benefits of using Infrastructure as Code? (select five)

  A. Infrastructure as Code is relatively simple to learn and write, regardless of a user's prior experience with developing code
  B. Infrastructure as Code provides configuration consistency and standardization among deployments
  C. Infrastructure as Code is easily repeatable, allowing the user to reuse code to deploy similar, yet different resources
  D. Infrastructure as Code gives the user the ability to recreate an application's infrastructure for disaster recovery scenarios
  E. Infrastructure as Code easily replaces development languages such as Go and .Net for application development
  F. Infrastructure as Code allows a user to turn a manual task into a simple, automated deployment (Correct)
  A. Infrastructure as Code is relatively simple to learn and write, regardless of a user's prior experience with developing code
  C. Infrastructure as Code is easily repeatable, allowing the user to reuse code to deploy similar, yet different resources
  D. Infrastructure as Code gives the user the ability to recreate an application's infrastructure for disaster recovery scenarios
  F. Infrastructure as Code allows a user to turn a manual task into a simple, automated deployment (Correct)

  ---

  Explanation

  If you are new to infrastructure as code as a concept, it is the process of managing infrastructure in a file or files rather than manually configuring resources in a user interface. A resource in this instance is any piece of infrastructure in a given environment, such as a virtual machine, security group, network interface, etc. At a high level, Terraform allows operators to use HCL to author files containing definitions of their desired resources on almost any provider (AWS, GCP, GitHub, Docker, etc) and automates the creation of those resources at the time of application.

• Question 418:

  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" ] }
  D. provisioner "remote-exec" { inline = [ "echo 0", "echo 1" ] }

  ---

  Explanation

  remote-exec Provisioner

  Example usage

  resource "aws_instance" "web" {

  # ...

  provisioner "remote-exec" {

  inline = [

  "puppet apply",

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

  ]

  }

  }

• Question 419:

  You can reference a resource created with for_each using a Splat (*) expression.

  A. True
  B. False
  B. False

  ---

  Explanation

  Splat Expressions with Maps The splat expression patterns shown above apply only to lists, sets, and tuples. To get a similar result with a map or object value you must use for expressions. Resources that use the for_each argument will appear in expressions as a map of objects, so you can't use splat expressions with those resources. For more information, see Referring to Resource Instances. https://www.terraform.io/language/meta-arguments/for_each#referring-to-instances https://www.terraform.io/language/expressions/references

• Question 420:

  Module variable assignments are inherited from the parent module and do not need to be explicitly set.

  A. True
  B. False
  B. False

  ---

  Explanation

  Module variable assignments are not inherited from the parent module and you need to explicitly set them using the source argument. This allows you to customize the behavior of each module instance.