HashiCorp Certified - Vault Associate Course - Key/Value Secrets Engine

The video tutorial provides an in-depth look at the key value secrets engine in Vault, focusing on its use for storing static secrets. It explains the differences between KV version 1 and version 2, highlighting the versioning capabilities of KV V2. The tutorial covers how to access secrets through various interfaces, enforce access policies, and organize data within KV stores. It also demonstrates enabling secrets engines using both the UI and CLI, and discusses the importance of planning data organization to ensure security and ease of management.

What is the primary use of the Key-Value Secrets Engine in Vault?

• To manage user access

• To dynamically generate secrets

• To encrypt data

• To store static secrets

Which version of the Key-Value Secrets Engine supports versioning?

• Neither version

• Version 2

• Both versions

• Version 1

How can secrets be accessed in Vault?

• Only through the API

• Only through the CLI

• Through the UI, CLI, and API

• Only through the UI

What is required to write a new secret in the KV store?

• List capability

• Read capability

• Create capability

• Delete capability

What is a recommended practice before organizing secrets in the KV store?

• Enable all possible paths

• Plan and organize the data structure

• Consult with a Vault expert

• Start saving secrets immediately

What is the default path for enabling a KV secrets engine?

• /default

• /kv

• /secret

• /data

What does the 'data' prefix indicate in KV version 2?

• The path for storing secrets

• The path for accessing the UI

• The path for metadata

• The path for CLI commands

What happens when you delete a secret in KV version 2?

• It is archived

• It is encrypted

• It is marked for soft deletion

• It is permanently removed

How can you upgrade a KV version 1 secrets engine to version 2?

• By deleting the existing engine

• By using the enable-versioning command

• By reinstalling Vault

• By using the CLI to create a new path

What is the purpose of metadata in KV version 2?

• To encrypt secrets

• To track version history and creation dates

• To manage access policies

• To store user information