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

HashiCorp TERRAFORM-ASSOCIATE-003 Online Questions & Answers

• Question 11:

  When do you need to explicitly execute terraform refresh?

  A. Before every terraform plan
  B. Before every terraform apply
  C. Before every terraform import
  D. None of the above
  D. None of the above

  ---

  Explanation

  Wherever possible, avoid using terraform refresh explicitly and instead rely on Terraform's behavior of automatically refreshing existing objects as part of creating a normal plan. Source: https://www.terraform.io/cli/commands/refresh

• Question 12:

  From the code below, identify the implicit dependency:

  A. The EIP with an id of ami-2757f631
  B. The AMI used for the EC2 instance
  C. The EC2 instance labeled web_server
  D. The S3 bucket labeled company_data
  C. The EC2 instance labeled web_server

  ---

  Explanation

• Question 13:

  Mary has created a database instance in AWS and for ease of use is outputting the value of the database password with the following code:

  1.output "db_password"

  2.{

  3.value = local.db_password

  4.}

  Mary wants to hide the output value in the CLI after terraform apply? What is the best way?

  A. Use secure parameter
  B. Use sensitive parameter
  C. Use cryptographic hash
  D. Encrypt the value using encrypt() function
  B. Use sensitive parameter

  ---

  Explanation

• Question 14:

  Which of the following are advantages of using infrastructure as code (laC) instead of provisioning with a graphical user interface (GUI)? Choose two correct answers.

  A. Prevents manual modifications to your resources
  B. Lets you version, reuse, and share infrastructure configuration
  C. Secures your credentials
  D. Provisions the same resources at a lower cost
  E. Reduces risk of operator error
  B. Lets you version, reuse, and share infrastructure configuration
  E. Reduces risk of operator error

  ---

  Explanation

  Infrastructure as code (IaC) is a way of managing and provisioning cloud infrastructure using programming techniques instead of manual processes1. IaC has many advantages over using a graphical user interface (GUI) for provisioning infrastructure, such as: Versioning: IaC allows you to store your infrastructure configuration in a version control system, such as Git, and track changes over time. This enables you to roll back to previous versions, compare differences, and collaborate with other developers Reusability: IaC allows you to create reusable modules and templates that can be applied to different environments, such as development, testing, and production. This reduces duplication, improves consistency, and speeds up deployment. Sharing: IaC allows you to share your infrastructure configuration with other developers, teams, or organizations, and leverage existing code from open source repositories or registries. This fosters best practices, innovation, and standardization. Risk reduction: IaC reduces the risk of human error, configuration drift, and security breaches that can occur when provisioning infrastructure manually or using a GUI. IaC also enables you to perform automated testing, validation, and compliance checks on your infrastructure before deploying it.

  References: What is Infrastructure as Code? Explained for Beginners - freeCodeCamp.org The benefits of Infrastructure as Code - Microsoft Community Hub Infrastructure as Code : Best Practices, Benefitsand; Examples - Spacelift Benefits of Infrastructure as Code (IaC) for Modern Businesses in the Cloud The 7 Biggest Benefits of Infrastructure as Code - DuploCloud

• Question 15:

  If writing Terraform code that adheres to the Terraform style conventions, how would you properly indent each nesting level compared to the one above it?

  A. With four spaces
  B. With a tab
  C. With three spaces
  D. With two spaces
  D. With two spaces

  ---

  Explanation

  https://www.terraform.io/language/syntax/style#style-conventions

• Question 16:

  Which of the following is not true of Terraform providers?

  A. An individual person can write a Terraform Provider
  B. A community of users can maintain a provider
  C. HashiCorp maintains some providers
  D. Cloud providers and infrastructure vendors can write, maintain, or collaborate on Terraform providers
  E. None of the above
  E. None of the above

  ---

  Explanation

  All of the statements are true of Terraform providers. Terraform providers are plugins that enable Terraform to interact with various APIs and services1. Anyone can write a Terraform provider, either as an individual or as part of a community2. HashiCorp maintains some providers, such as the AWS, Azure, and Google Cloud providers3. Cloud providers and infrastructure vendors can also write, maintain, or collaborate on Terraform providers, such as the VMware, Oracle, and Alibaba Cloud providers.

  References: Providers - Configuration Language | Terraform | HashiCorp Developer Plugin Development - How Terraform Works With Plugins | Terraform | HashiCorp Developer Terraform Registry Terraform Registry

• Question 17:

  Which task does teraform init not perform?

  A. Sources any modules and copies the configuration locally
  B. Validates all required variables are present
  C. Connects to the backend
  D. Sources all providers present in the configuration and ensures they are downloaded and available locally
  B. Validates all required variables are present

  ---

  Explanation

• Question 18:

  Your company has been using Terraform Cloud for a some time now . But every team is creating their own modules , and there is no standardization of the modules , with each team creating the resources in their own unique way . You want to enforce a standardization of the modules across the enterprise . What should be your approach.

  A. Create individual workspaces for each team , and ask them to share modules across workspaces.
  B. Implement a Private module registry in Terraform cloud , and ask teams to reference them.
  C. Upgrade to Terraform enterprise , since this is not possible in terraform cloud.
  D. Upload the modules in the terraform public module registry , and ask teams to reference them
  B. Implement a Private module registry in Terraform cloud , and ask teams to reference them.

  ---

  Explanation

  Terraform Cloud's private module registry helps you share Terraform modules across your organization. It includes support for module versioning, a searchable and filterable list of available modules, and a configuration designer to help you build new workspaces faster. By design, the private module registry works much like the public Terraform Registry. If you're already used the public registry, Terraform Cloud's registry will feel familiar. Understand the different offerings in Terraform OS, Terraform Cloud and Terraform Enterprise. Terraform Cloud's private module registry helps you share Terraform modules across your organization. https://www.terraform.io/docs/cloud/registry/index.html https://www.terraform.io/docs/cloud/registry/publish.html

• Question 19:

  What is the name assigned by Terraform to reference this resource?

  

  A. dev
  B. azurerm_resource_group
  C. azurerm
  D. test
  A. dev

  ---

  Explanation

• Question 20:

  You have declared a variable name my_var in terraform configuration without a value associated with it.

  variable my_var {}

  After running terraform plan it will show an error as variable is not defined.

  A. True
  B. False
  B. False

  ---

  Explanation

  Input variables are usually defined by stating a name, type and a default value. However, the type and default values are not strictly necessary. Terraform can deduct the type of the variable from the default or input value. Variables can be

  predetermined in a file or included in the command-line options. As such, the simplest variable is just a name while the type and value are selected based on the input.

  variable "variable_name" {}

  terraform apply-var variable_name="value"

  The input variables, like the one above, use a couple of different types: strings, lists, maps, and boolean. Here are some examples of how each type are defined and used.

  String

  Strings mark a single value per structure and are commonly used to simplify and make complicated values more user-friendly. Below is an example of a string variable definition.

  variable "template" {

  type = string

  default = "01000000-0000-4000-8000-000030080200"

  }

  A string variable can then be used in resource plans. Surrounded by double quotes, string variables are a simple substitution such as the example underneath.

  storage = var.template

  List

  Another type of Terraform variables lists. They work much like a numbered catalogue of values. Each value can be called by their corresponding index in the list. Here is an example of a list variable definition.

  variable "users" {

  type = list

  default = ["root", "user1", "user2"]

  }

  Lists can be used in the resource plans similarly to strings, but you'll also need to denote the index of the value you are looking for.

  username = var.users[0]

  Map

  Maps are a collection of string keys and string values. These can be useful for selecting values based on predefined parameters such as the server configuration by the monthly price.

  variable "plans" {

  type = map

  default = {

  "5USD" = "1xCPU-1GB"

  "10USD" = "1xCPU-2GB"

  "20USD" = "2xCPU-4GB"

  }

  }

  You can access the right value by using the matching key. For example, the variable below would set the plan to "1xCPU-1GB".

  plan = var.plans["5USD"]

  The values matching to their keys can also be used to look up information in other maps. For example, underneath is a shortlist of plans and their corresponding storage sizes.

  variable "storage_sizes" {

  type = map

  default = {

  "1xCPU-1GB" = "25"

  "1xCPU-2GB" = "50"

  "2xCPU-4GB" = "80"

  }

  }

  These can then be used to find the right storage size based on the monthly price as defined in the previous example.

  size = lookup(var.storage_sizes, var.plans["5USD"]) Boolean

  The last of the available variable type is boolean. They give the option to employ simple true or false values. For example, you might wish to have a variable that decides when to generate the root user password on a new deployment.

  variable "set_password" {

  default = false

  }

  The above example boolean can be used similarly to a string variable by simply marking down the correct variable.

  create_password = var.set_password

  By default, the value is set to false in this example. However, you can overwrite the variable at deployment by assigning a different value in a command-line variable.

  terraform apply-var set_password="true"