Network security and bind IP in MongoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the bind IP address in the MongoDB configuration.

MongoDB

net:
  bindIp: [1]

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

A"0.0.0.0"

B"255.255.255.0"

C"127.0.0.1"

D"192.168.1.1"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 0.0.0.0 allows connections from any IP, which is insecure by default.

Using a subnet mask like 255.255.255.0 is invalid here.

The default bind IP for MongoDB is "127.0.0.1", which means it listens only on localhost for security.

2fill in blank

medium

Complete the command to restart MongoDB after changing the bind IP.

MongoDB

sudo systemctl [1] mongod

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

Arestart

Bstop

Cstart

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'start' when the service is already running won't apply changes.

Using 'stop' alone will stop the service but not start it again.

After changing the bind IP, you must restart the MongoDB service to apply changes.

3fill in blank

hard

Fix the error in the bind IP configuration line to allow connections only from localhost.

MongoDB

net:
  bindIp: [1]

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

A"localhost"

B"0.0.0.0"

C"::"

D"127.0.0.1"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'localhost' string instead of IP address causes config errors.

Using 0.0.0.0 allows all IPs, which is insecure.

"127.0.0.1" is the correct IPv4 loopback address for localhost. "localhost" as a string is invalid here.

4fill in blank

hard

Fill both blanks to configure MongoDB to bind to localhost and a specific IP address.

MongoDB

net:
  bindIp: [1],[2]

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

A"127.0.0.1"

B"192.168.0.100"

C"0.0.0.0"

D"localhost"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'localhost' string instead of IP address.

Using 0.0.0.0 which opens to all IPs.

Binding to both "127.0.0.1" and a specific LAN IP allows local and network connections.

5fill in blank

hard

Fill all three blanks to create a MongoDB configuration snippet that binds to localhost, disables authorization, and sets the port to 27017.

MongoDB

net:
  bindIp: [1]
security:
  authorization: [2]
  keyFile: [3]

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

A"127.0.0.1"

B"disabled"

Cnull

D"enabled"

Attempts:

3 left

💡 Hint

Common Mistakes

Setting authorization to 'enabled' without a keyFile causes errors.

Using a string 'null' instead of null value.

Binding to localhost restricts connections, disabling authorization turns off access control, and keyFile is null when authorization is disabled.

Practice

1. What does the bindIp setting in MongoDB control?

easy

A. The storage location of MongoDB data files

B. Which IP addresses can connect to the MongoDB server

C. The database user permissions

D. The port number MongoDB listens on

Solution

1. Step 1: Understand the purpose of bindIp

   The bindIp setting specifies which IP addresses are allowed to connect to the MongoDB server.

2. Step 2: Compare with other options

   Port number, user permissions, and data file locations are controlled by other settings, not bindIp.

3. Final Answer:

   Which IP addresses can connect to the MongoDB server -> Option B

4. Quick Check:

   bindIp controls allowed IPs [OK]

Hint: bindIp controls allowed IP addresses only [OK]

Common Mistakes:

• Confusing bindIp with port setting
• Thinking bindIp controls user permissions
• Assuming bindIp sets data file paths

2. Which of the following is the correct syntax to allow connections only from localhost in MongoDB's configuration file?

easy

A. bindIp: '192.168.1.1'

B. bindIp: '0.0.0.0'

C. bindIp: '127.0.0.1'

D. bindIp: 'localhost'

Solution

1. Step 1: Identify localhost IP address

   Localhost IP is 127.0.0.1, so to allow only local connections, bindIp must be set to this.

2. Step 2: Check other options

   0.0.0.0 allows all IPs, 192.168.1.1 is a specific network IP, and localhost is not valid syntax here.

3. Final Answer:

   bindIp: '127.0.0.1' -> Option C

4. Quick Check:

   Localhost IP = 127.0.0.1 [OK]

Hint: Use 127.0.0.1 to restrict to localhost [OK]

Common Mistakes:

• Using 'localhost' string instead of IP
• Using 0.0.0.0 which allows all IPs
• Confusing network IP with localhost

3. Given the following MongoDB config snippet:

net:
  bindIp: 127.0.0.1,192.168.1.100

Which clients can connect to this MongoDB server?

medium

A. Clients from 127.0.0.1 and 192.168.1.100 only

B. Clients from any IP address

C. Only clients from IP 127.0.0.1

D. Clients from 192.168.1.100 only

Solution

1. Step 1: Read the bindIp list

   The bindIp setting lists two IPs: 127.0.0.1 (localhost) and 192.168.1.100.

2. Step 2: Determine allowed clients

   Only clients connecting from these two IP addresses are allowed. Other IPs are blocked.

3. Final Answer:

   Clients from 127.0.0.1 and 192.168.1.100 only -> Option A

4. Quick Check:

   bindIp list limits clients to those IPs [OK]

Hint: bindIp list allows only those IPs [OK]

Common Mistakes:

• Assuming 0.0.0.0 allows all IPs here
• Ignoring second IP in the list
• Thinking it allows all local network IPs

4. You set bindIp: 127.0.0.1,192.168.1.50 in your MongoDB config, but remote clients from 192.168.1.50 cannot connect. What is the most likely cause?

medium

A. MongoDB service was not restarted after config change

B. The IP 192.168.1.50 is not a valid IP address

C. bindIp only accepts one IP address

D. Remote clients must use port 27018 instead of 27017

Solution

1. Step 1: Verify bindIp syntax

   Multiple IPs separated by commas is valid syntax, so the config is correct.

2. Step 2: Check common operational issues

   Changes to bindIp require MongoDB service restart to take effect. Without restart, old settings remain active.

3. Final Answer:

   MongoDB service was not restarted after config change -> Option A

4. Quick Check:

   Restart needed after config changes [OK]

Hint: Restart MongoDB after changing bindIp [OK]

Common Mistakes:

• Thinking bindIp accepts only one IP
• Assuming IP is invalid without checking
• Changing port without reason

5. You want your MongoDB server to accept connections only from your local machine and a trusted remote IP 10.0.0.5. Which bindIp setting achieves this securely?

hard

A. bindIp: localhost,10.0.0.5

B. bindIp: 0.0.0.0

C. bindIp: 10.0.0.5

D. bindIp: 127.0.0.1,10.0.0.5

Solution

1. Step 1: Identify IPs to allow

   You want to allow localhost (127.0.0.1) and the remote IP 10.0.0.5.

2. Step 2: Choose correct bindIp syntax

   Use a comma-separated list of IPs: 127.0.0.1,10.0.0.5. Using 0.0.0.0 allows all IPs, which is insecure. Using 'localhost' is invalid syntax.

3. Final Answer:

   bindIp: 127.0.0.1,10.0.0.5 -> Option D

4. Quick Check:

   List allowed IPs explicitly [OK]

Hint: List all allowed IPs separated by commas [OK]

Common Mistakes:

• Using 0.0.0.0 which allows all IPs
• Using 'localhost' string instead of IP
• Allowing only remote IP without localhost