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.