Protected mode in Redis - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to check if Redis is running in protected mode.

Redis

CONFIG GET [1]

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

Amaxclients

Brequirepass

Ctimeout

Dprotected-mode

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'requirepass' instead of 'protected-mode'.

Using 'timeout' which is unrelated to protected mode.

The Redis configuration parameter protected-mode controls if Redis runs in protected mode.

2fill in blank

medium

Complete the command to disable protected mode in Redis configuration.

Redis

CONFIG SET [1] [2]

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

Arequirepass

Bprotected-mode

Ctimeout

Dno

Attempts:

3 left

💡 Hint

Common Mistakes

Setting 'protected-mode' to 'yes' instead of 'no'.

Using unrelated parameters like 'requirepass'.

To disable protected mode, set protected-mode to no. Here, the second blank should be 'no'.

3fill in blank

hard

Fix the error in the command to enable protected mode.

Redis

CONFIG SET protected-mode [1]

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

Ayes

Bno

Cdisable

Doff

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'no' or 'off' which disables protected mode.

Using 'disable' which is not a valid value.

To enable protected mode, the value must be yes.

4fill in blank

hard

Fill both blanks to check the current protected mode status and set it to 'no'.

Redis

CONFIG GET [1]
CONFIG SET [2] no

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

Aprotected-mode

Brequirepass

Ctimeout

Dmaxclients

Attempts:

3 left

💡 Hint

Common Mistakes

Using different parameters for get and set commands.

Using unrelated parameters like 'requirepass'.

Both commands use the protected-mode parameter to get and set its value.

5fill in blank

hard

Fill all three blanks to get, set protected mode to 'yes', and verify the change.

Redis

CONFIG GET [1]
CONFIG SET [2] [3]
CONFIG GET protected-mode

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

Aprotected-mode

Bno

Cyes

Drequirepass

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'no' instead of 'yes' to enable protected mode.

Using different parameter names for get and set.

The first and second blanks are the parameter name protected-mode. The third blank is the value yes to enable protected mode.

Practice

1. What is the main purpose of Redis protected-mode?

easy

A. To increase Redis performance by caching data

B. To limit connections and keep Redis safe by default

C. To enable automatic backups of Redis data

D. To allow unlimited remote connections without restrictions

Solution

1. Step 1: Understand what protected mode does

   Protected mode is designed to keep Redis safe by limiting who can connect to it.

2. Step 2: Identify the main purpose

   It prevents unauthorized access by restricting connections unless properly configured.

3. Final Answer:

   To limit connections and keep Redis safe by default -> Option B

4. Quick Check:

   Protected mode = Limits connections [OK]

Hint: Protected mode restricts connections to protect Redis [OK]

Common Mistakes:

• Thinking it improves performance
• Confusing it with backup features
• Assuming it allows open access

2. Which of the following is the correct way to disable protected mode in the Redis configuration file?

easy

A. protected-mode no

B. protected-mode yes

C. protected_mode no

D. disable-protected-mode true

Solution

1. Step 1: Identify the correct syntax for the setting

   The Redis config uses protected-mode with a dash, not underscore or other variations.

2. Step 2: Determine the value to disable it

   Setting protected-mode no disables protected mode.

3. Final Answer:

   protected-mode no -> Option A

4. Quick Check:

   Disable protected mode = protected-mode no [OK]

Hint: Use dash and 'no' to disable protected mode [OK]

Common Mistakes:

• Using underscore instead of dash
• Setting value to 'yes' to disable
• Using invalid config keys

3. Given the Redis config snippet:

protected-mode yes
bind 127.0.0.1

What will happen if a client tries to connect from a remote IP?

medium

A. Connection will be rejected due to protected mode and bind settings

B. Connection will be accepted without restrictions

C. Redis will crash with an error

D. Connection will be accepted only if password is provided

Solution

1. Step 1: Analyze protected mode and bind settings

   Protected mode is enabled and Redis is bound only to localhost (127.0.0.1).

2. Step 2: Understand remote connection behavior

   Clients from remote IPs cannot connect because Redis listens only on localhost and protected mode blocks unsafe access.

3. Final Answer:

   Connection will be rejected due to protected mode and bind settings -> Option A

4. Quick Check:

   Protected mode + bind localhost = reject remote [OK]

Hint: Protected mode + bind localhost blocks remote clients [OK]

Common Mistakes:

• Assuming remote connections are allowed
• Thinking Redis crashes on remote connect
• Believing password alone allows connection

4. You set protected-mode no in your Redis config but remote clients still cannot connect. What is the most likely cause?

medium

A. Redis server is not running

B. Redis requires a password to connect remotely

C. The bind setting restricts connections to localhost

D. Protected mode is still enabled by default

Solution

1. Step 1: Check the effect of disabling protected mode

   Disabling protected mode allows remote connections if no other restrictions exist.

2. Step 2: Identify other config restrictions

   If bind 127.0.0.1 is set, Redis only listens on localhost, blocking remote clients.

3. Final Answer:

   The bind setting restricts connections to localhost -> Option C

4. Quick Check:

   Bind localhost blocks remote even if protected mode off [OK]

Hint: Check bind setting if remote access fails despite disabling protected mode [OK]

Common Mistakes:

• Assuming protected mode disables instantly without config reload
• Ignoring bind restrictions
• Thinking password is mandatory for remote connect

5. You want to allow remote connections to Redis safely. Which configuration is the best practice?

hard

A. Set protected-mode no and bind 0.0.0.0 without password

B. Keep protected-mode yes, bind to localhost, and use SSH tunnel for remote access

C. Disable protected mode and allow connections from any IP without authentication

D. Disable protected mode, bind to all interfaces, and require a strong password

Solution

1. Step 1: Understand risks of disabling protected mode

   Disabling protected mode requires securing Redis by other means like authentication.

2. Step 2: Combine settings for safe remote access

   Binding to all interfaces (0.0.0.0) allows remote connections, but a strong password is needed to secure access.

3. Final Answer:

   Disable protected mode, bind to all interfaces, and require a strong password -> Option D

4. Quick Check:

   Safe remote access = disable protected mode + bind all + password [OK]

Hint: Disable protected mode only with password and open bind [OK]

Common Mistakes:

• Disabling protected mode without password
• Binding only to localhost for remote access
• Allowing open access without authentication