Encryption at rest protects data stored on disk. What does it mainly prevent?
Think about what happens if someone steals the physical hard drive.
Encryption at rest ensures that if someone gets the physical storage, they cannot read the data without the encryption keys.
After running db.adminCommand({ getCmdLineOpts: 1 }), which output indicates encryption at rest is active?
db.adminCommand({ getCmdLineOpts: 1 })Look for a security setting that shows encryption is turned on.
The presence of "enableEncryption": true under security confirms encryption at rest is enabled.
Choose the valid YAML configuration to enable encryption at rest with a key file.
Check the exact option names and boolean values.
The correct keys are enableEncryption set to true and encryptionKeyFile specifying the key file path.
What is a common performance effect when encryption at rest is enabled?
Think about what extra work the server does when encrypting data.
Encryption requires CPU cycles to encrypt data before writing and decrypt after reading, increasing CPU load.
Given this config snippet, MongoDB fails to start. What is the likely cause?
security: enableEncryption: true encryptionKeyFile: /etc/mongodb/keyfile encryptionCipherMode: AES256-CBC
Check MongoDB documentation for supported cipher modes.
MongoDB deprecated AES256-CBC mode; using it causes startup failure. Supported mode is AES256-GCM.