Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. HashiCorp
  5. VA-002-P

HashiCorp VA-002-P Exam
HashiCorp Certified: Vault Associate (Page 4 )

Updated On: 30-Jan-2026
Page 4 of 41
PDF with 200 Questions

True or False: You can migrate the Terraform backend but only if there are no resources currently being managed.

  1. False
  2. True

Answer(s): A

Explanation:

If you are already using Terraform to manage infrastructure, you probably want to transfer to another backend, such as Terraform Cloud, so you can continue managing it. By migrating your Terraform state, you can hand off infrastructure without de-provisioning anything.



Which of the following actions are performed during a terraform init? (select three)

  1. provisions the declared resources in your configuration
  2. download the declared providers which are supported by HashiCorp
  3. initializes the backend configuration
  4. initializes downloaded and/or installed providers

Answer(s): B,C,D

Explanation:

The terraform init command is used to initialize a working directory containing Terraform
configuration files. This is the first command that should be run after writing a new Terraform configuration or cloning an existing one from version control. It is safe to run this command multiple times.



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

  1. functions
  2. workspaces
  3. module registry
  4. sentinel

Answer(s): D

Explanation:

Sentinel is an embedded policy-as-code framework integrated with the HashiCorp Enterprise products. It enables fine-grained, logic-based policy decisions, and can be extended to use information from external sources.



When multiple engineers start deploying infrastructure using the same state file, what is a feature of remote state storage that is critical to ensure the state does not become corrupt?

  1. state locking
  2. object storage
  3. encryption
  4. workspaces

Answer(s): A

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. State locking happens automatically on all operations that could write state. You won't see any message that it is happening. If state locking fails, Terraform will not continue. You can disable state locking for most commands with the -lock flag but it is not recommended.



Your organization has moved to AWS and has manually deployed infrastructure using the console. Recently, a decision has been made to standardize on Terraform for all deployments moving forward. What can you do to ensure that all existing is managed by Terraform moving forward without interruption to existing services?

  1. resources that are manually deployed in the AWS console cannot be imported by Terraform
  2. using terraform import, import the existing infrastructure into your Terraform state
  3. delete the existing resources and recreate them using new a Terraform configuration so Terraform can manage them moving forward
  4. submit a ticket to AWS and ask them to export the state of all existing resources and use terraform import to import them into the state file

Answer(s): B

Explanation:

Terraform is able to import existing infrastructure. This allows you to take resources you've created by some other means and bring it under Terraform management. This is a great way to slowly transition infrastructure to Terraform or to be sure you're confident that you can use Terraform in the future if it currently doesn't support every AWS service or feature you need

today.



Viewing page 4 of 41
Viewing questions 16 - 20 out of 200 questions



Post your Comments and Discuss HashiCorp VA-002-P exam prep with other Community members:

Join the VA-002-P Discussion