Rename dangerous commands in Redis - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why rename dangerous Redis commands?

What is the main reason to rename dangerous Redis commands like FLUSHALL or CONFIG in a production environment?

A To prevent accidental or unauthorized execution that could cause data loss or security issues

B To improve the performance of Redis commands

C To enable Redis to run on multiple ports simultaneously

D To allow Redis commands to be executed faster by the CPU

💡 Hint

Think about what could happen if someone runs FLUSHALL by mistake.

Renaming dangerous commands helps protect the database from accidental or malicious actions that could delete data or expose sensitive configurations.

❓ query_result

intermediate

Effect of renaming FLUSHALL command

If you rename the FLUSHALL command to DISABLE_FLUSHALL in Redis configuration, what happens when you try to run FLUSHALL?

A Redis executes the flush and deletes all keys

B Redis returns an error saying the command is unknown

C Redis ignores the command and does nothing

D Redis restarts automatically

💡 Hint

Renaming a command means the original name no longer exists.

When a command is renamed, the original command name is disabled and Redis will not recognize it, returning an error.

📝 Syntax

advanced

Correct syntax to rename CONFIG command

Which of the following is the correct way to rename the CONFIG command to DISABLE_CONFIG in the Redis configuration file?

A rename-command CONFIG DISABLE_CONFIG

B rename command CONFIG DISABLE_CONFIG

C rename_command CONFIG DISABLE_CONFIG

D renamecommand CONFIG DISABLE_CONFIG

💡 Hint

Check the exact spelling and spacing of the rename command.

The correct syntax uses a hyphen and no spaces inside the command name: rename-command CONFIG DISABLE_CONFIG.

❓ optimization

advanced

Best practice for renaming multiple dangerous commands

You want to rename multiple dangerous commands in Redis to prevent accidental use. Which approach is best?

A Rename all commands to the same name to simplify configuration

B Disable all commands by removing them from Redis source code

C Rename each dangerous command to a unique, hard-to-guess name in the Redis config file

D Do not rename commands; rely on user training only

💡 Hint

Think about security and manageability.

Renaming each command to a unique name prevents accidental execution and keeps commands manageable and traceable.

🔧 Debug

expert

Why does renaming a command fail to take effect?

You added rename-command FLUSHDB DISABLE_FLUSHDB to your Redis config file but the FLUSHDB command still works as usual after restart. What is the most likely reason?

A The command name is case sensitive and must be lowercase

B Redis does not support renaming commands

C The rename-command line is placed after a conflicting command that overrides it

D The config file was not saved before restarting Redis

💡 Hint

Check if your changes were applied after restart.

If the config file changes are not saved, Redis will load the old config and the rename will not apply.