HashiCorp HashiCorp Certifications TERRAFORM-ASSOCIATE-003 Questions & Answers

• Question 11:

  You much initialize your working directory before running terraform validate.

  A. True

  B. False

  Correct Answer: A

  You must initialize your working directory before running terraform validate, as it will ensure that all the required plugins and modules are installed and configured properly. If you skip this step, you may encounter errors or inconsistencies when validating your configuration files.

• Question 12:

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

  A. True

  B. False

  Correct Answer: B

  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 13:

  It is best practice to store secret data in the same version control repository as your Terraform configuration.

  A. True

  B. False

  Correct Answer: B

  It is not a best practice to store secret data in the same version control repository as your Terraform configuration, as it could expose your sensitive information to unauthorized parties or compromise your security. You should use environment variables, vaults, or other mechanisms to store and provide secret data to Terraform.

• Question 14:

  Which of the following is not a valid Terraform variable type?

  A. list

  B. array

  C. nap

  D. string

  Correct Answer: B

  This is not a valid Terraform variable type. The other options are valid variable types that can store different kinds of values2.

• Question 15:

  Which of these statements about Terraform Cloud workspaces is false?

  A. They have role-based access controls

  B. You must use the CLI to switch between workspaces

  C. Plans and applies can be triggered via version control system integrations

  D. They can securely store cloud credentials

  Correct Answer: B

  The statement that you must use the CLI to switch between workspaces is false. Terraform Cloud workspaces are different from Terraform CLI workspaces. Terraform Cloud workspaces are required and represent all of the collections of infrastructure in an organization. They are also a major component of role-based access in Terraform Cloud. You can grant individual users and user groups permissions for one or more workspaces that dictate whether they can manage variables, perform runs, etc. You can create, view, and switch between Terraform Cloud workspaces using the Terraform Cloud UI, the Workspaces API, or the Terraform Enterprise Provider5. Terraform CLI workspaces are optional and allow you to create multiple distinct instances of a single configuration within one working directory. They are useful for creating disposable environments for testing or experimenting without affecting your main or production environment. You can create, view, and switch between Terraform CLI workspaces using the terraform workspace command6. The other statements about Terraform Cloud workspaces are true. They have role-based access controls that allow you to assign permissions to users and teams based on their roles and responsibilities. You can create and manage roles using the Teams API or the Terraform Enterprise Provider7. Plans and applies can be triggered via version control system integrations that allow you to link your Terraform Cloud workspaces to your VCS repositories. You can configure VCS settings, webhooks, and branch tracking to automate your Terraform Cloud workflow8. They can securely store cloud credentials as sensitive variables that are encrypted at rest and only decrypted when needed. You can manage variables using the Terraform Cloud UI, the Variables API, or the Terraform Enterprise Provider9. References = [Workspaces]5, [Terraform CLI Workspaces]6, [Teams and Organizations]7, [VCS Integration]8, [Variables]9

• Question 16:

  What are some benefits of using Sentinel with Terraform Cloud/Terra form Cloud? Choose three correct answers.

  A. You can enforce a list of approved AWS AMIs

  B. Policy-as-code can enforce security best practices

  C. You can check out and check in cloud access keys

  D. You can restrict specific resource configurations, such as disallowing the use of CIDR=0.0.0.0/0.

  E. Sentinel Policies can be written in HashiCorp Configuration Language (HCL)

  Correct Answer: ABD

  These are some of the benefits of using Sentinel with Terraform Cloud/Terraform Enterprise, as they allow you to implement logic-based policies that can access and evaluate the Terraform plan, state, and configuration. The other options are not true, as Sentinel does not manage cloud access keys, and Sentinel policies are written in Sentinel language, not HCL.

• Question 17:

  How would you output returned values from a child module in the Terraform CLI output?

  A. Declare the output in the root configuration

  B. Declare the output in the child module

  C. Declare the output in both the root and child module

  D. None of the above

  Correct Answer: C

  To output returned values from a child module in the Terraform CLI output, you need to declare the output in both the child module and the root module. The child module output will return the value to the root module, and the root module output will display the value in the CLI. References = [Terraform Outputs]

• Question 18:

  Terraform providers are part of the Terraform core binary.

  A. True

  B. False

  Correct Answer: B

  Terraform providers are not part of the Terraform core binary. Providers are distributed separately from Terraform itself and have their own release cadence and version numbers. Providers are plugins that Terraform uses to interact with various APIs, such as cloud providers, SaaS providers, and other services. You can find and install providers from the Terraform Registry, which hosts providers for most major infrastructure platforms. You can also load providers from a local mirror or cache, or develop your own custom providers. To use a provider in your Terraform configuration, you need to declare it in the provider requirements block and optionally configure its settings in the provider block. References = : Providers - Configuration Language | Terraform : Terraform Registry

  -Providers Overview | Terraform

• Question 19:

  What kind of configuration block will create an infrastructure object with settings specified within the block?

  A. provider

  B. state

  C. data

  D. resource

  Correct Answer: D

  This is the kind of configuration block that will create an infrastructure object with settings specified within the block. The other options are not used for creating infrastructure objects, but for configuring providers, accessing state data, or querying data sources.

• Question 20:

  You ate creating a Terraform configuration which needs to make use of multiple providers, one for AWS and one for Datadog. Which of the following provider blocks would allow you to do this?

  

  A. Option A

  B. Option B

  C. Option C

  D. Option D

  Correct Answer: C

  Option C is the correct way to configure multiple providers in a Terraform configuration. Each provider block must have a name attribute that specifies which provider it configures2. The other options are either missing the name attribute or using an invalid syntax.