VAULT-ASSOCIATE practice question 11 of 15
You have a 2GB Base64 binary large object (blob) that needs to be encrypted. Which of the following best describes the transit secrets engine?
Full set: 57 questionsThe Vault transit secrets engine is designed for "encryption as a service," handling cryptographic operations on data passed to it without storing the data itself. However, it is not optimized for very large payloads like a 2GB blob. Such a large request would consume significant memory and network resources on the Vault server, potentially leading to instability. The default maximum request size for a Vault server is 32MB, which a 2GB file far exceeds. The recommended pattern for large data is envelope encryption, where the transit engine encrypts a locally-generated data key, and that key is then used by the client application to encrypt the large blob.
A. This describes the general process but ignores the critical constraint of the 2GB file size, which makes the direct use of the transit engine impractical and ill-advised.
B. This is incorrect. A core design principle of the transit secrets engine is that it does not store the plaintext or ciphertext data it processes; it operates on it in-memory.
C. This is incorrect. The transit secrets engine never stores the data being encrypted, either temporarily or permanently. This statement fundamentally misunderstands its purpose.
1. HashiCorp Vault Documentation, Configuration, maxrequestsize: "The maxrequestsize parameter specifies the maximum size in bytes of a request body. This is set to a default of 32MB (33554432 bytes)." A 2GB blob is significantly larger than this default, making the operation fail unless this setting is dangerously increased.
Source: HashiCorp, Vault Documentation, Server Configuration, maxrequestsize.
2. HashiCorp Learn, "Vault and the Developer: Encryption as a Service" Tutorial: "When you have a large amount of data to encrypt (e.g. database, large files), it is not practical to send the data to Vault over the network to be encrypted. Instead, you can use Vault's transit secrets engine to practice envelope encryption."
Source: HashiCorp Learn, Use Case: Transit Secrets Engine, Envelope Encryption section.
3. HashiCorp Vault Documentation, Transit Secrets Engine: "The transit secrets engine handles cryptographic functions on data in-transit. Vault doesn't store the data sent to the secrets engine." This confirms that options B and C, which claim Vault stores the blob, are incorrect.
Source: HashiCorp, Vault Documentation, Secrets Engines, Transit.
Keep practicing
Take the free VAULT-ASSOCIATE practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other VAULT-ASSOCIATE practice questions
- Question 1To give a role the ability to display or output all of the end points under the /secrets/…
- Question 4Which of the following cannot define the maximum time-to-live (TTL) for a token?
- Question 6What can be used to limit the scope of a credential breach?
- Question 8What is the Vault CLI command to query information about the token the client is currentl…
- Question 10When unsealing Vault, each Shamir unseal key should be entered:
- Question 12What command creates a secret with the key "my-password" and the value "53cr3t" at path "…
