Practice exams for Vault Associate

50 questions · 60 min

  • Secrets engines 11 questions
  • Authentication methods 8 questions
  • Vault tokens 8 questions
  • Vault policies 6 questions
  • Vault deployment architecture 6 questions
  • Vault architecture fundamentals 4 questions
  • Vault leases 3 questions
  • Encryption as a Service 2 questions
  • Access management architecture 2 questions
Study mode Exam mode

25 free questions across all domains, no account required.

The full set of 50 questions is included in the All certifications subscription. Subscribe

How to prepare for Vault Associate with InfraPrep

The 50 questions cover 9 domains: Secrets engines, Authentication methods, Vault tokens, Vault policies, Vault deployment architecture, Vault architecture fundamentals, Vault leases, Encryption as a Service, Access management architecture. 25 of them are free, without an account.

Study mode

Answer at your pace: each answer is corrected straight away, with an explanation and the link to the documentation it relies on.

Exam mode

A timed exam of 60 minutes, with a question map to flag and come back to questions before you submit.

Results by domain

Your score is broken down by domain, so you know what to review first.

Original questions

Every question is written from the public documentation, never copied from the exam. You can contest an answer from study mode.

Sample question

Authentication methods

A new platform engineer is reviewing a Vault design document and asks what role the auth methods play, as opposed to the secrets engines. Which description of an auth method is correct?

  1. It encrypts the storage backend so that data at rest cannot be read without the root key
  2. It stores, generates, or encrypts data on behalf of applications
  3. It verifies user or machine information against a system and generates a token on success
  4. It records every request and response for later forensic review
Show the answer and the explanation

Correct answer: C

Authentication is the verification of user- or machine-supplied information against an internal or external system; on success a token is generated.

Source: official documentation

Try the free questions