Why key management matters in Redis - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is consistent key naming important in Redis?

Imagine you store user data in Redis. Why should you use a consistent naming pattern for keys?

A It automatically encrypts the data stored under those keys.

B It helps avoid key collisions and makes data easier to find.

C It increases the speed of Redis commands by changing internal algorithms.

D It allows Redis to store keys in multiple databases simultaneously.

💡 Hint

Think about how you find things in a messy room versus a tidy one.

Consistent key naming helps prevent accidentally overwriting data and makes it easier to retrieve related data by pattern matching keys.

❓ query_result

intermediate

What keys will the command return?

Given these keys in Redis: 'user:1:name', 'user:2:name', 'session:1', 'user:1:email', what does the command KEYS user:1:* return?

A ['user:1:name', 'user:1:email']

B []

C ['session:1']

D ['user:1:name', 'user:2:name', 'user:1:email']

💡 Hint

The asterisk (*) matches any characters after 'user:1:'.

The pattern 'user:1:*' matches keys starting exactly with 'user:1:' followed by anything, so it returns keys for user 1 only.

📝 Syntax

advanced

Identify the syntax error in this Redis command

Which option shows a Redis command with a syntax error?

Command: SET user:100 name 'Alice'

A SET user:100:name Alice

B SET user:100:name 'Alice'

C SET user:100 name 'Alice'

D 'ecilA' eman:001:resu TES

💡 Hint

Remember the SET command syntax: SET key value

The SET command expects exactly two arguments: a key and a value. Option C has three arguments, which is invalid syntax.

❓ optimization

advanced

Which key design improves Redis memory usage?

You want to store session data for millions of users. Which key design is best to reduce memory usage?

A Use short keys like 's:userid' and store all session data in hashes.

B Use long descriptive keys like 'user:session:data:region:country:userid'.

C Use random UUIDs as keys without any pattern.

D Store all sessions in one big JSON string under a single key.

💡 Hint

Think about key length and data structure efficiency.

Short keys reduce memory overhead. Using hashes groups related fields under one key, saving space compared to many separate keys.

🔧 Debug

expert

Why does this Redis key expire unexpectedly?

You set a key with SET user:123:name 'Bob' EX 3600. Later, you run DEL user:123:name and then SET user:123:name 'Bob' without expiration. But the key still expires after 1 hour. Why?

A You must restart Redis to clear expiration timers on keys.

B Redis caches the expiration time and applies it to new keys automatically.

C The second SET command did not remove the expiration, so the TTL remains.

D The DEL command failed silently, so the old key with expiration still exists.

💡 Hint

Check how Redis handles expiration when overwriting keys.

When you overwrite a key with SET without expiration, Redis removes the old TTL. But if you use commands like SETNX or certain scripts, TTL may persist. Here, DEL removes the key, so the new SET should not have TTL. The issue is likely the DEL did not succeed or was not executed properly.

Practice

1. Why is it important to use clear and consistent key names in Redis?

easy

A. It helps organize data and makes it easier to find keys.

B. It increases the size of the Redis database automatically.

C. It allows Redis to run without any memory limits.

D. It prevents Redis from accepting new connections.

Solution

1. Step 1: Understand key naming purpose

   Clear and consistent key names help keep data organized in Redis.

2. Step 2: Identify benefits of good key names

   Organized keys make it easier to find and manage data quickly.

3. Final Answer:

   It helps organize data and makes it easier to find keys. -> Option A

4. Quick Check:

   Good key names = easier data management [OK]

Hint: Think: clear names = easy to find data [OK]

Common Mistakes:

• Assuming key names affect database size
• Believing key names control memory limits
• Confusing key names with connection settings

2. Which of the following is the correct way to set a key with a prefix in Redis CLI?

easy

A. SET user-1001 "John"

B. SET user:1001 "John"

C. SET user/1001 "John"

D. SET user1001 "John"

Solution

1. Step 1: Recognize common prefix pattern

   Using a colon ':' is the standard way to separate prefixes in Redis keys.

2. Step 2: Check each option's syntax

   Only SET user:1001 "John" uses the colon prefix format correctly.

3. Final Answer:

   SET user:1001 "John" -> Option B

4. Quick Check:

   Prefix with ':' is correct Redis key style [OK]

Hint: Use ':' to separate prefixes in keys [OK]

Common Mistakes:

• Using dashes or slashes instead of colons
• Not using any separator between prefix and key
• Confusing key naming with command syntax

3. Given these Redis keys: user:1, user:2, order:1, what will the command KEYS user:* return?

medium

A. []

B. ["order:1"]

C. ["user:1", "user:2", "order:1"]

D. ["user:1", "user:2"]

Solution

1. Step 1: Understand the KEYS command with pattern

   KEYS user:* matches all keys starting with 'user:' prefix.

2. Step 2: Identify matching keys

   Only 'user:1' and 'user:2' match the pattern; 'order:1' does not.

3. Final Answer:

   ["user:1", "user:2"] -> Option D

4. Quick Check:

   KEYS user:* returns keys with 'user:' prefix [OK]

Hint: KEYS with prefix* returns keys starting with prefix [OK]

Common Mistakes:

• Expecting keys with different prefixes to appear
• Thinking KEYS returns empty if any key exists
• Confusing pattern matching syntax

4. You want to delete all keys with prefix session: but your command DEL session:* returns an error. What is the problem?

medium

A. DEL command requires a password to delete keys.

B. The prefix 'session:' is invalid in Redis keys.

C. DEL does not accept wildcards; you must delete keys individually.

D. You must restart Redis before deleting keys.

Solution

1. Step 1: Understand DEL command behavior

   DEL command deletes specific keys; it does not support wildcards.

2. Step 2: Identify correct deletion method

   To delete keys by pattern, you must first find keys (e.g., with KEYS) then delete them individually.

3. Final Answer:

   DEL does not accept wildcards; you must delete keys individually. -> Option C

4. Quick Check:

   DEL needs exact keys, no wildcards [OK]

Hint: DEL needs exact keys; use KEYS + DEL loop [OK]

Common Mistakes:

• Trying to use wildcards directly with DEL
• Thinking prefixes are invalid keys
• Believing Redis needs restart to delete keys

5. You have keys cache:item:1, cache:item:2, and cache:user:1. You want to delete only keys related to items efficiently. Which approach is best?

hard

A. Use SCAN 0 MATCH cache:item:* to find keys, then delete them one by one.

B. Run DEL cache:* to delete all cache keys at once.

C. Rename keys to remove 'item' prefix before deleting.

D. Flush the entire Redis database to remove all keys.

Solution

1. Step 1: Identify keys to delete

   Only keys with prefix 'cache:item:' should be deleted, not 'cache:user:'.

2. Step 2: Choose efficient deletion method

   SCAN with MATCH finds keys without blocking Redis; then delete keys individually.

3. Step 3: Avoid unsafe commands

   DEL with wildcards or FLUSHDB deletes too much; renaming keys is unnecessary.

4. Final Answer:

   Use SCAN 0 MATCH cache:item:* to find keys, then delete them one by one. -> Option A

5. Quick Check:

   SCAN + MATCH + DEL = safe selective deletion [OK]

Hint: Use SCAN with MATCH to safely find keys before deleting [OK]

Common Mistakes:

• Using DEL with wildcards causing errors
• Flushing entire DB losing all data
• Renaming keys unnecessarily before deletion