HCVA0-003 practice question 19 of 35

True or False? When encrypting data with the Transit secrets engine, Vault always stores the ciphertext in a dedicated KV store along with the associated encryption key.

Full set: 285 questions
Answer options
A: True Correct answer
B: False
Correct Answer:
F; A. True; L; S; E
Explanation

The statement is fundamentally incorrect. The HashiCorp Vault Transit secrets engine is designed to provide "encryption as a service" by performing cryptographic operations on data without ever storing that data. A client application sends plaintext to the Vault API endpoint for the Transit engine; Vault encrypts the data using a named key that it manages and returns the resulting ciphertext to the client. The client application is then responsible for storing the ciphertext in its own primary datastore (e.g., a database, object store). Vault only stores and manages the encryption keys, not the data that is encrypted with them.

Why Incorrect

The "True" option is incorrect because it misrepresents the core architectural principle of the Transit secrets engine. The engine's primary value is decoupling key management from data storage. If Vault stored the ciphertext alongside the key, it would become a data storage system, which is not its intended function in this context.

References

1. HashiCorp Vault Official Documentation, "Transit Secrets Engine": In the introductory section, the documentation explicitly states: "The transit secrets engine handles cryptographic functions on data in-transit. Vault doesn't store the data sent to the secrets engine. It can also be viewed as 'cryptography as a service'."

Source: HashiCorp Developer Portal, Vault Documentation, Secrets Engines, Transit. (developer.hashicorp.com/vault/docs/secrets/transit)

2. HashiCorp Vault Tutorial, "Encryption as a Service: Transit Secrets Engine": This tutorial clarifies the intended workflow: "The primary use case for transit is to encrypt data from applications while still storing that encrypted data in a primary datastore like PostgreSQL... This allows the security team to manage encryption keys and define encryption policies, and developers can store encrypted data in their application datastore without having access to the encryption keys."

Source: HashiCorp Developer Portal, Vault Tutorials, Encryption as a Service, "EAAS with Transit". (developer.hashicorp.com/vault/tutorials/encryption-as-a-service/eaas-transit)

3. HashiCorp Vault API Documentation, "Encrypt Data": The API documentation for the transit/encrypt/:name endpoint describes a request/response model where plaintext is provided in the request payload and ciphertext is returned in the response. There is no mechanism or parameter described that would cause Vault to store the resulting ciphertext. The operation is stateless regarding the data being processed.

Source: HashiCorp Developer Portal, Vault API Documentation, Secret: Transit, "Encrypt Data". (developer.hashicorp.com/vault/api-docs/secret/transit#encrypt-data)

Scroll to Top