You have a 2GB Base64 binary large object (blob) that needs to be encrypted. Which of the following best describes the transit secrets engine?
37 comments · newest first
KE
Kenia
11 months ago
C sounds off too; Vault isn't meant for permanent storage of blobs.
XE
Xenia
11 months ago
A is definitely not right; local encryption isn't what transit is about.
GE
German
11 months ago
Wait, can Vault really handle 2GB blobs? That's surprising!
ET
Ethan
12 months ago
I disagree, D seems more accurate for size limitations.
GL
Glen
12 months ago
I think option B makes the most sense for large blobs.
MI
Mindy
12 months ago
I definitely remember that the transit engine is about encryption, but I’m not clear on whether it stores data or just encrypts it.
MA
Margart
1 year ago
I feel like option D makes sense because of the size, but I can't recall if the transit engine can handle larger data.
LA
Lavera
1 year ago
I think I came across a similar question where we discussed temporary storage in Vault. That might relate to option B.
VA
Vashti
1 year ago
I remember studying the transit secrets engine, but I'm not entirely sure how it handles large blobs like this.
LY
Lyndia
1 year ago
Okay, I think I've got this. The transit engine is designed for encrypting and decrypting data, not for permanently storing large blobs. Option D seems like the best choice.
CA
Casandra
1 year ago
Hmm, I'm a bit confused by the options here. I'll need to review the transit engine documentation to understand how it handles large binary blobs.
GA
Gail
1 year ago
This is a tricky one. I'll need to think carefully about the capabilities of the transit secrets engine to determine the best approach.
GE
Geoffrey
1 year ago
I'm pretty confident that option A is the correct answer. The transit engine uses a data key to encrypt and decrypt data locally, which should work well for a 2GB blob.
DI
Dick
1 year ago
The image shows some NX-API options, so I'll review those carefully and try to match them to the question about querying the MAC address table.
PR
Precious
1 year ago
I'm with Catalina on this one. D just cracks me up. It's like Vault is saying, 'Hey, we can handle your secrets, but anything over a few kilobytes? Nah, that's just too much for us!'
NO
Noe
1 year ago
A) A data key encrypts the blob locally, and the same key decrypts the blob locally.
OR
Oretha
1 year ago
C) Vault will store the blob permanently. Be sure to run Vault on a compute optimized machine
TE
Tesha
1 year ago
B) To process such a large blob. Vault will temporarily store it in the storage backend.
RO
Rosann
1 year ago
A) A data key encrypts the blob locally, and the same key decrypts the blob locally.
CA
Catalina
1 year ago
D has got to be the funniest option. The transit engine is not good for large binaries? That's like saying the microwave is not good for heating up an entire Thanksgiving turkey!
LE
Leonora
1 year ago
C) Vault will store the blob permanently. Be sure to run Vault on a compute optimized machine
DA
Darell
1 year ago
C) Vault will store the blob permanently. Be sure to run Vault on a compute optimized machine
BE
Berry
1 year ago
B) To process such a large blob. Vault will temporarily store it in the storage backend.
JA
Jade
1 year ago
A) A data key encrypts the blob locally, and the same key decrypts the blob locally.
TA
Tamera
1 year ago
B) To process such a large blob. Vault will temporarily store it in the storage backend.
VI
Vi
1 year ago
A) A data key encrypts the blob locally, and the same key decrypts the blob locally.
AR
Arlie
2 years ago
I don't know, C just seems like overkill for a 2GB blob. Why would I need a compute-optimized machine just for Vault to store it permanently?
MA
Major
2 years ago
Hmm, B sounds interesting. Temporarily storing the blob in the backend could work, but I wonder about the performance implications.
LI
Lizette
1 year ago
Hmm, B sounds interesting. Temporarily storing the blob in the backend could work, but I wonder about the performance implications.
EL
Elza
1 year ago
B) To process such a large blob. Vault will temporarily store it in the storage backend.
ES
Esteban
1 year ago
A) A data key encrypts the blob locally, and the same key decrypts the blob locally.
GL
Glenna
2 years ago
Option A seems like the most straightforward approach. Encrypt and decrypt locally with the same key - simple and secure!
AR
Arlean
1 year ago
User 2: Definitely, it's important to keep it simple and secure when dealing with encryption.
KE
Keena
1 year ago
User 1: Option A seems like the most straightforward approach. Encrypt and decrypt locally with the same key - simple and secure!
JU
Julianna
2 years ago
I agree with Pamella. Option A) seems like the most logical solution for encrypting a large blob.
PA
Pamella
2 years ago
I believe option A) is the best choice because it describes how the data key encrypts and decrypts the blob locally.
AI
Aileen
2 years ago
I think the transit secrets engine is used for encrypting data in transit.