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

HashiCorp TERRAFORM-ASSOCIATE-003 Online Questions & Answers

• Question 371:

  What does state locking accomplish?

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

  ---

  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. Source: https://www.terraform.io/language/state/locking

• Question 372:

  Terraform Enterprise (also referred to as pTFE) requires what type of backend database for a clustered deployment?

  A. PostgreSQL
  B. Cassandra
  C. MySQL
  D. MSSQL
  A. PostgreSQL

  ---

  Explanation

  External Services mode stores the majority of the stateful data used by the instance in an external PostgreSQL database and an external S3-compatible endpoint or Azure blob storage. There is still critical data stored on the instance that must be managed with snapshots. Be sure to check the PostgreSQL Requirements for information that needs to be present for Terraform Enterprise to work. This option is best for users with expertise managing PostgreSQL or users that have access to managed PostgreSQL offerings like AWS RDS.

• Question 373:

  Which of the following command can be used to view the specified version constraints for all providers used in the current configuration.

  A. terraform providers
  B. terraform state show
  C. terraform provider
  D. terraform plan
  A. terraform providers

  ---

  Explanation

  Use the terraform providers command to view the specified version constraints for all providers used in the current configuration. https://www.terraform.io/docs/configuration/providers.html

• Question 374:

  Infrastructure as Code (laC) can be stored in a version control system along with application code.

  A. True
  B. False
  A. True

  ---

  Explanation

  Infrastructure as Code (IaC) can indeed be stored in a version control system along with application code. This practice is a fundamental principle of modern infrastructure management, allowing teams to apply software development practices like versioning, peer review, and CI/CD to infrastructure management. Storing IaC configurations in version control facilitates collaboration, history tracking, and change management.

  References: While this concept is a foundational aspect of IaC and is widely accepted in the industry, direct references from the HashiCorp Terraform Associate (003) study materials were not found in the provided files. However, this practice is encouraged in Terraform's best practices and various HashiCorp learning resources.

• Question 375:

  You have decided to create a new Terraform workspace to deploy a development environment. What is different about this workspace?

  A. It uses a different branch of code
  B. It uses a different backend
  C. It has its own state file
  D. It pulls in a different terraform.tvars file
  C. It has its own state file

  ---

  Explanation

• Question 376:

  Your firm employs a version control system (for example, git) and has requested that you commit all terraform code to it. During the commit, you must be cautious with sensitive information. Which of the following files should be left out of the commit?

  A. main.tf
  B. variables.tf
  C. provisioner.tf
  D. terraform.tfstate
  D. terraform.tfstate

  ---

  Explanation

• Question 377:

  The terraform state command can be used to ____

  A. Update current state
  B. Refresh existing state file
  C. Print the current state file in console
  D. It is not a valid command
  A. Update current state

  ---

  Explanation

  The terraform state command is used for advanced state management. Rather than modify the state directly, the terraform state commands can be used in many cases instead. https://www.terraform.io/docs/commands/state/index.html

• Question 378:

  Which of these is true about Terraform's plugin-based architecture?

  A. Terraform can only source providers from the internet
  B. Every provider in a configuration has its own state file for its resources
  C. You can create a provider for your API if none exists
  D. All providers are part of the Terraform core binary
  C. You can create a provider for your API if none exists

  ---

  Explanation

  Terraform is built on a plugin-based architecture, enabling developers to extend Terraform by writing new plugins or compiling modified versions of existing plugins. Terraform plugins are executable binaries written in Go that expose an implementation for a specific service, such as a cloud resource, SaaS platform, or API. If there is no existing provider for your API, you can create one using the Terraform Plugin SDK or the Terraform Plugin Framework.

  References: Plugin Development - How Terraform Works With Plugins | Terraform | HashiCorp Developer Lab: Terraform Plug-in Based Architecture - GitHub Terraform Plugin SDK - Terraform by HashiCorp HashiCorp Terraform Plugin Framework Now Generally Available

• Question 379:

  To check if all code in a Terraform configuration with multiple modules is properly formatted without making changes, what command should be run?

  A. terraform fmt-check
  B. terraform fmt-write-false
  C. terraform fmt "list-recursive
  D. terraform fmt-check-recursive
  D. terraform fmt-check-recursive

  ---

  Explanation

  -check Check if the input is formatted. Exit status will be 0 if all input is properly formatted and non-zero otherwise.-recursive Also process files in subdirectories. By default, only the given directory (or current directory) is processed.

• Question 380:

  Which of the following arguments are required when declaring a Terraform output?

  A. sensitive
  B. description
  C. default
  D. value
  D. value

  ---

  Explanation

  When declaring a Terraform output, the value argument is required. Outputs are a way to extract information from Terraform-managed infrastructure, and the value argument specifies what data will be outputted. While other arguments like description and sensitive can provide additional context or security around the output, value is the only mandatory argument needed to define an output.

  References: The requirement of the value argument for outputs is specified in Terraform's official documentation, which provides guidelines on defining and using outputs in Terraform configurations.