HashiCorp Certified - Vault Associate Course - Vault Policies—Path

The video tutorial delves into the concept of paths within Vault, emphasizing their importance in managing access and functionality. It explains the structure of paths, including system-based paths and those requiring root or sudo privileges. The tutorial also covers the KV secrets engine and how data is stored and accessed through paths. Additionally, it highlights the critical nature of root protected paths and the necessary permissions to manage them.

What is a common prefix for system-based paths in Vault?

• data

• sys

• user

• app

In the context of the KV secrets engine, what does the 'data' prefix signify?

• The type of data stored

• The version of the secret engine

• The metadata of the secret

• The location of the secret engine

Which of the following is NOT a higher-level path where data can be stored?

• secrets/data/platform

• secrets/data/metadata

• secrets/data/AWS/tools

• secrets/data/Ansible

What is required to access root-protected paths in Vault?

• A root token or sudo capabilities

• A user token

• An admin password

• A developer key

Which path would you need sudo privileges to manually seal a Vault?

• sys/rekey

• sys/stepdown

• sys/rotate

• sys/seal