Home > TA-002-P / HashiCorp

HashiCorp TA-002-P Exam Prep Guide Prep guide for the TA-002-P Exam [Q55-Q75]

Published date May 15, 2024

Author admin

Comments: 0

Rate this post

HashiCorp TA-002-P Exam Prep Guide: Prep guide for the TA-002-P Exam

2024 New Preparation Guide of HashiCorp TA-002-P Exam

Aruba Networks Certified: Mobility Associate-Professional Exam Certified Professional salary

The estimated average salary of HashiCorp Certified: Terraform Associate TA-002-P Professional Exam is listed below:

Europe: 88,032 EURO
India: 7,199,4 INR
United States: 100,146 USD
England: 71,460 POUND

These salaries are calculated at the time of writing according to the currency rates.

HashiCorp TA-002-P exam is a certification exam that assesses one’s knowledge and skills in utilizing HashiCorp Terraform to provision infrastructure. Terraform is an open-source tool that enables users to create, manage, and deploy infrastructure as code. HashiCorp Certified: Terraform Associate certification exam is designed for professionals who work with Terraform and want to validate their expertise in using the tool to build, manage, and maintain infrastructure.

Q55. Which of the following type of variable allows multiple values of several distinct types to be grouped together as a single value?

Map

Object

Tuple

List

Structural type of variable allows multiple values of several distinct types to be grouped together as a single value. They require a schema as an argument, to specify which types are allowed for which elements.
https://www.terraform.io/docs/configuration/types.html

Q56. Terraform requires the Go runtime as a prerequisite for installation.

True

False

Explanation
https://www.terraform.io/plugin/sdkv2/guides/v1-upgrade-guide and
https://www.terraform.io/plugin/sdkv2/guides/v2-upgrade-guide

Q57. Which of the below configuration file formats are supported by Terraform? (Select TWO)

YAML

Node

JSON

HCL

Q58. You have created a terraform script that uses a lot of new constructs that have been introduced in terraform
v0.12. However, many developers who are cloning the script from your git repo, are using v0.11, and getting
errors. What can be done from your end to solve this problem?

Force developer to use v0.12 by using terraform setting ‘required_version’ and set it to >=0.12.

Refactor the code to support both v0.11, and v0.12. It might be a difficult process, but there is no other
way.

Add a condition in front of each such specific construct, to check whether the running terraform version
id v0.11 or v0.12, and ,work accordingly.

Add comments in your code to tell developers to use v0.12 . If they use v0.11 , that should be their
problem , which they need to figure out.

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

Q59. Why should secrets not be hard coded into Terraform code? Choose two correct answers

All passwords should be rotated on a quarterly basis.

The Terraform code is copied to the target resources to be applied locally and could expose secrets if a target resource is compromised.

Terraform code is typically stored in version control, as well as copied to the systems from h it’s run. Any of those may not have robust security mechanisms.

It makes the code less reusable.

Q60. Examine the following Terraform configuration, which uses the data source for an AWS AMI.
What value should you enter for the ami argument in the AWS instance resource?

aws_ami.ubuntu

data.aws_ami.ubuntu

data.aws_ami.ubuntu.id

aws_ami.ubuntu.id

resource “aws_instance” “web” {
ami = data.aws_ami.ubuntu.id

Q61. You have deployed a new webapp with a public IP address on a cloud provider. However, you did not create any outputs for your code. What is the best method to quickly find the IP address of the resource you deployed?

In a new folder, use the terraform_remote_state data source to load in the state file, then write an output for each resource that you find the state file

Run terraform state list to find the name of the resource, then terraform state show to find the attributes including public IP address

Run terraform output ip_address to view the result

Run terraform destroy then terraform apply and look for the IP address in stdout

This is a quick way to inspect the state file and find the information you need without modifying anything5. The other options are either incorrect or inefficient.

Q62. You need to deploy resources into two different cloud regions in the same Terraform configuration. To do that,
you declare multiple provider configurations as follows:

What meta-argument do you need to configure in a resource block to deploy the resource to the “us-west-2”
AWS region?

alias = west

provider = west

provider = aws.west

alias = aws.west

Explanation
https://www.terraform.io/language/providers/configuration

Q63. You need to write some Terraform code that adds 42 firewall rules to a security group as shown in the
example.

What can you use to avoid writing 42 different nested ingress config blocks by hand?

A count loop

A for block

A for each block

A dynamic block

Explanation
A dynamic block acts much like a for expression, but produces nested blocks instead of a complex typed
value. It iterates over a given complex value, and generates a nested block for each element of that complex
value. Reference: https://www.terraform.io/language/expressions/dynamic-blocks

Q64. Select two answers to complete the following sentence: Before a new provider can be used, it must be ______ and _______.

approved by HashiCorp

uploaded to source control

declared in the configuration

initialized

Explanation
Each time a new provider is added to configuration — either explicitly via a provider block or by adding a resource from that provider — Terraform must initialize the provider before it can be used. Initialization downloads and installs the provider’s plugin so that it can later be executed.

Q65. Which feature of Terraform allows multiple state files for a single configuration file depending upon the environment?

Terraform Modules

Terraform Enterprise

Terraform Workspaces

Terraform Remote Backends

Q66. Which of the following allows Terraform users to apply policy as code to enforce standardized configurations for resources being deployed via infrastructure as code?

Sentinel

Module registry

Functions

Workspaces

Explanation
Sentinel is a language and framework for policy built to be embedded in existing software to enable fine-grained, logic-based policy decisions. A policy describes under what circumstances certain behaviors are allowed. Sentinel is an enterprise-only feature.
https://www.youtube.com/watch?v=Vy8s7AAvU6g&feature=emb_title

Q67. A Terraform provisioner must be nested inside a resource configuration block.

True

False

Explanation
Most provisioners require access to the remote resource via SSH or WinRM, and expect a nested connection block with details about how to connect.
Reference: https://www.terraform.io/docs/language/resources/provisioners/connection.html

Q68. You have multiple developers working on a terraform project (using terraform OSS), and have saved the terraform state in a remote S3 bucket . However ,team is intermittently experiencing inconsistencies in the provisioned infrastructure / failure in the code . You have traced this problem to simultaneous/concurrent runs of terraform apply command for 2/more developers . What can you do to fix this problem?

Use terraform workspaces feature, this will fix this problem by default , as every developer will have their own state file , and terraform will merge them on server side on its own.

Structure your team in such a way that only one individual will run terraform apply , everyone will just make changes and share with him. Then there will be no chance of any inconsistencies.

Stop using remote state , and store the developer tfstate in their own machine . Once a day , all developers should sit together and merge the state files manually , to avoid any inconsistencies.

Enable terraform state locking for the S3 backend using DynamoDB table. This prevents others from acquiring the lock and potentially corrupting your state.

S3 backend support state locking using DynamoDB.
https://www.terraform.io/docs/state/locking.html

Q69. A colleague has informed you that a new version of a Terraform module that your team hosts on an Amazon
S3 bucket is broken. The Amazon S3 bucket has versioning enabled. Your colleague tells you to make sure
you are not using the latest version in your configuration. You have the following configuration block in your
code that refers to the module:
module “infranet” { source = “s3::https://s3-us-west-2.amazonaws.com/infrabucket/infra_module.zip”}
What is the best way to ensure that you are not using the latest version of the module?

Add a module version constraint in your configuration’s backend block and specify a previous version.

Add a version key to the module configuration and specify a previous version.

Delete the latest version of the module in S3 to rollback to the previous version.

Add a version property to the module in Terraform’s state file and specify a previous version.

Explanation
Version constraints are supported only for modules installed from a module registry, such as the Terraform
Registry or Terraform Cloud’s private module registry. Other module sources can provide their own versioning
mechanisms within the source string itself, or might not support versions at all. In particular, modules sourced
from local file paths do not support version; since they’re loaded from the same source repository.
Only Terraform Registries support module versioning by using the version key, one cannot configure a
previous version of the module in the configuration. Deleting the latest version of the module in S3 is the only
option of the available options that ensures you won’t use the latest version. You could also modify the source
URL to specify a versionId URL parameter for a previous version.
https://www.terraform.io/docs/configuration/modules.html#source

Q70. The Terraform language does not support user-defined functions, and so only the functions built in to the language are available for use.

False

True

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

Q71. Which of the below features of Terraform can be used for managing small differences between different environments which can act more like completely separate working directories.

Repositories

Workspaces

Environment Variables

Backends

Explanation
workspaces allow conveniently switching between multiple instances of a single configuration within its single backend. They are convenient in a number of situations, but cannot solve all problems.
A common use for multiple workspaces is to create a parallel, distinct copy of a set of infrastructure in order to test a set of changes before modifying the main production infrastructure. For example, a developer working on a complex set of infrastructure changes might create a new temporary workspace in order to freely experiment with changes without affecting the default workspace.
Non-default workspaces are often related to feature branches in version control. The default workspace might correspond to the “master” or “trunk” branch, which describes the intended state of production infrastructure.
When a feature branch is created to develop a change, the developer of that feature might create a corresponding workspace and deploy into it a temporary “copy” of the main infrastructure so that changes can be tested without affecting the production infrastructure. Once the change is merged and deployed to the default workspace, the test infrastructure can be destroyed and the temporary workspace deleted.
https://www.terraform.io/docs/state/workspaces.html
https://www.terraform.io/docs/state/workspaces.html#when-to-use-multiple-workspaces

Q72. 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. }

YES

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.

Q73. You have created a custom variable definition file my_vars.tfvars. How will you use it for provisioning
infrastructure?

terraform apply -var-state-file =”my_vars.tfvars”

terraform apply var-file=”my_vars.tfvars”

terraform plan -var-file=”my_vars.tfvar”

terraform apply -var-file=”my_vars.tfvars”

Explanation
To set lots of variables, it is more convenient to specify their values in a variable definitions file (with a
filename ending in either .tfvars or .tfvars.json) and then specify that file on the command line with -var-file:
terraform apply -var-file=”my_vars.tfvars”
https://www.terraform.io/docs/configuration/variables.html#variable-definitions-tfvars-files

Q74. A user has created three workspaces using the command line – prod, dev, and test. The user wants to create a fourth workspace named stage. Which command will the user execute to accomplish this?

terraform workspace new stage

terraform workspace -new stage

terraform workspace -create stage

terraform workspace create stage

The terraform workspace new command is used to create a new workspace.
https://www.terraform.io/docs/commands/workspace/new.html

Q75. 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. What command will do this?

terraform taint

terraform apply

terraform graph

terraform refresh

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

Loading …