Encryption at rest concept in MongoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable encryption at rest in MongoDB configuration.

MongoDB

security:
  enableEncryption: [1]

Drag options to blanks, or click blank then click option'

Aenabled

Bfalse

Con

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using strings like 'enabled' or 'on' instead of boolean true.

Setting the value to false disables encryption.

Setting enableEncryption to true activates encryption at rest in MongoDB.

2fill in blank

medium

Complete the code to specify the encryption key file path in MongoDB configuration.

MongoDB

security:
  encryptionKeyFile: [1]

Drag options to blanks, or click blank then click option'

A/etc/mongodb/keyfile

Btrue

C/var/lib/mongodb/data

DenableEncryption

Attempts:

3 left

💡 Hint

Common Mistakes

Using boolean values instead of a file path.

Confusing the key file path with data directory paths.

The encryptionKeyFile option requires the path to the key file used for encryption at rest.

3fill in blank

hard

Fix the error in the MongoDB configuration to properly enable encryption at rest.

MongoDB

security:
  enableEncryption: [1]

Drag options to blanks, or click blank then click option'

ATrue

BTRUE

Ctrue

Dyes

Attempts:

3 left

💡 Hint

Common Mistakes

Using capitalized or uppercase boolean values.

Using 'yes' instead of true.

MongoDB configuration requires lowercase true to enable boolean options correctly.

4fill in blank

hard

Fill both blanks to configure encryption at rest with the key file and enable it.

MongoDB

security:
  enableEncryption: [1]
  encryptionKeyFile: [2]

Drag options to blanks, or click blank then click option'

Atrue

B/etc/mongodb/keyfile

C/var/lib/mongodb/data

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Setting enableEncryption to false disables encryption.

Using incorrect file paths for the key file.

Encryption is enabled by setting enableEncryption to true and specifying the correct encryptionKeyFile path.

5fill in blank

hard

Fill all three blanks to create a MongoDB configuration snippet that enables encryption at rest, specifies the key file, and sets the storage engine.

MongoDB

security:
  enableEncryption: [1]
  encryptionKeyFile: [2]
storage:
  engine: [3]

Drag options to blanks, or click blank then click option'

Atrue

B/etc/mongodb/keyfile

CwiredTiger

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'false' disables encryption.

Using storage engines that do not support encryption.

Incorrect file paths for the key file.

Encryption at rest is enabled with true, the key file path is specified, and the storage engine is set to wiredTiger, which supports encryption.

Practice

1. What does encryption at rest mean in MongoDB?

easy

A. Data is encrypted only in the application memory.

B. Data is encrypted when stored on disk to protect it from unauthorized access.

C. Data is encrypted only during query execution.

D. Data is encrypted only when it is sent over the network.

Solution

1. Step 1: Understand encryption at rest meaning

   Encryption at rest means data is protected by encoding it while stored on disk, not just during transfer or processing.

2. Step 2: Identify correct option

   Only Data is encrypted when stored on disk to protect it from unauthorized access. correctly describes encryption at rest as protecting stored data on disk.

3. Final Answer:

   Data is encrypted when stored on disk to protect it from unauthorized access. -> Option B

4. Quick Check:

   Encryption at rest = Data encrypted on disk [OK]

Hint: Encryption at rest means data is safe on disk, not just in transit [OK]

Common Mistakes:

• Confusing encryption at rest with encryption in transit
• Thinking encryption happens only during queries
• Assuming encryption applies only in memory

2. Which of the following is the correct way to enable encryption at rest in MongoDB?

easy

A. Run a query like db.enableEncryption() in the shell.

B. Use encrypt() command on collections.

C. Configure the MongoDB server with encryption options in the config file.

D. Set encryption flags in the client application code.

Solution

1. Step 1: Know how encryption at rest is enabled

   Encryption at rest is enabled by configuring the MongoDB server settings, not by running queries or client code.

2. Step 2: Match correct method

   Only Configure the MongoDB server with encryption options in the config file. correctly states enabling encryption via server config file.

3. Final Answer:

   Configure the MongoDB server with encryption options in the config file. -> Option C

4. Quick Check:

   Encryption at rest enabled via server config [OK]

Hint: Encryption at rest is a server setting, not a query command [OK]

Common Mistakes:

• Trying to enable encryption using shell queries
• Assuming client code controls encryption at rest
• Confusing encryption at rest with field-level encryption

3. Given MongoDB is configured with encryption at rest enabled, what will happen if the encryption key is lost?

medium

A. Only new data is encrypted; old data remains readable.

B. Data can still be read normally without the key.

C. MongoDB automatically regenerates the key and decrypts data.

D. Data becomes inaccessible and cannot be decrypted.

Solution

1. Step 1: Understand role of encryption key

   The encryption key is essential to decrypt data stored on disk. Losing it means data cannot be read.

2. Step 2: Evaluate options

   Data becomes inaccessible and cannot be decrypted. correctly states data becomes inaccessible without the key. Other options are incorrect because data cannot be read or auto-decrypted without the key.

3. Final Answer:

   Data becomes inaccessible and cannot be decrypted. -> Option D

4. Quick Check:

   Lost key = no data access [OK]

Hint: Without the key, encrypted data is unreadable [OK]

Common Mistakes:

• Assuming MongoDB can recover data without the key
• Thinking only new data is encrypted
• Believing data remains readable without key

4. A MongoDB admin tries to enable encryption at rest by running db.enableEncryption() in the shell but gets an error. What is the likely cause?

medium

A. Encryption at rest cannot be enabled via shell commands; it requires server config changes.

B. The shell command syntax is incorrect; it should be db.enableEncryption(true).

C. Encryption at rest is enabled by default and does not require commands.

D. The admin lacks permissions to run shell commands.

Solution

1. Step 1: Understand how encryption at rest is enabled

   Encryption at rest is a server-level feature enabled via configuration files, not shell commands.

2. Step 2: Identify cause of error

   Trying to enable it via db.enableEncryption() causes error because this command does not exist.

3. Final Answer:

   Encryption at rest cannot be enabled via shell commands; it requires server config changes. -> Option A

4. Quick Check:

   Enable encryption via config, not shell [OK]

Hint: Encryption at rest needs config file, not shell commands [OK]

Common Mistakes:

• Trying to enable encryption with shell commands
• Assuming encryption is on by default
• Blaming permissions instead of wrong method

5. You want to ensure your MongoDB data is encrypted at rest and can be recovered safely. Which combination of steps is best practice?

hard

A. Enable encryption at rest in server config and securely manage encryption keys separately.

B. Encrypt data manually in application code and store keys in the database.

C. Use shell commands to enable encryption and keep keys in the same server folder.

D. Rely on MongoDB default settings without managing keys.

Solution

1. Step 1: Understand encryption at rest best practices

   Encryption at rest should be enabled via server config, and keys must be managed securely outside the database for safety and recovery.

2. Step 2: Evaluate options for key management and encryption

   Enable encryption at rest in server config and securely manage encryption keys separately. correctly combines enabling encryption at rest with secure key management. Other options either misuse shell commands, store keys insecurely, or rely on defaults.

3. Final Answer:

   Enable encryption at rest in server config and securely manage encryption keys separately. -> Option A

4. Quick Check:

   Config encryption + secure keys = best practice [OK]

Hint: Enable encryption in config and keep keys safe separately [OK]

Common Mistakes:

• Storing keys inside the database
• Trying to enable encryption via shell commands
• Ignoring key management importance