Key naming conventions (colons for namespacing) in Redis - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use colons in Redis key names?

In Redis, why do developers often use colons (:) in key names like user:1001:profile?

A Because Redis requires colons to separate key parts

B To create a clear hierarchy and group related keys logically

C To make keys shorter and save memory

D To encrypt the key names for security

💡 Hint

Think about how colons help organize keys for easier management.

Colons in Redis keys act like folders in a file system. They help group related keys, making it easier to find and manage them.

❓ query_result

intermediate

Find keys with a specific namespace

Given Redis keys: user:1001:profile, user:1002:profile, order:5001:status, which command lists all keys related to users?

A KEYS user:*

B KEYS *:user:*

C KEYS user

D KEYS *user*

💡 Hint

Use a pattern that matches keys starting with 'user:'

The pattern user:* matches all keys that start with 'user:' which includes all user-related keys.

📝 Syntax

advanced

Identify the invalid Redis key name

Which of the following Redis key names is invalid or problematic due to naming conventions?

A user::profile

B config:system:version

C cache:page:home

D session:abc123:token

💡 Hint

Look for unusual or repeated colons that might cause confusion.

Double colons :: can cause confusion or errors in key parsing and are generally avoided in Redis key naming.

❓ optimization

advanced

Optimizing Redis key design for large datasets

You have millions of user session keys like session:userid:token. Which key naming strategy helps improve Redis performance and memory usage?

A Use very long descriptive keys for clarity, e.g., <code>session:user:uniqueid:token</code>

B Use random characters instead of user IDs to avoid collisions

C Use short prefixes and avoid unnecessary parts, e.g., <code>s:uid:tok</code>

D Use spaces instead of colons to separate parts

💡 Hint

Shorter keys save memory and improve speed.

Shorter keys reduce memory usage and improve Redis lookup speed, especially with large datasets.

🔧 Debug

expert

Troubleshoot key pattern matching issue

You want to delete all keys related to orders using DEL order:* but it doesn't delete any keys. Why?

A DEL command does not support wildcards; use KEYS with DEL instead

B Keys have spaces instead of colons, so pattern doesn't match

C Redis keys are case-sensitive and keys are uppercase

D DEL command requires a list of keys, not a pattern

💡 Hint

Think about how DEL works with patterns.

The DEL command does not accept patterns. You must first get matching keys with KEYS and then delete them.

Practice

1. Why do Redis keys often use colons (:) in their names?

easy

A. To encrypt the key names for security

B. To make keys shorter and save memory

C. To organize keys into logical groups like folders

D. To separate keys by data type automatically

Solution

1. Step 1: Understand Redis key naming

   Redis keys are simple strings, but using colons helps group related keys logically.

2. Step 2: Recognize the purpose of colons

   Colons act like folder separators, making it easier to find and manage keys.

3. Final Answer:

   To organize keys into logical groups like folders -> Option C

4. Quick Check:

   Colons = logical grouping [OK]

Hint: Colons separate key parts like folders in a path [OK]

Common Mistakes:

• Thinking colons shorten keys
• Believing colons encrypt keys
• Assuming colons change data types

2. Which of the following is the correct Redis key name using colons for namespacing?

easy

A. user1000profile

B. user:1000:profile

C. user_1000_profile

D. user-1000-profile

Solution

1. Step 1: Identify proper colon usage

   Redis keys use colons to separate logical parts, like 'user', '1000', and 'profile'.

2. Step 2: Compare options

   Only user:1000:profile uses colons correctly to namespace the key.

3. Final Answer:

   user:1000:profile -> Option B

4. Quick Check:

   Colons separate key parts correctly [OK]

Hint: Look for colons separating key parts clearly [OK]

Common Mistakes:

• Using dashes or underscores instead of colons
• Not separating parts at all
• Mixing separators inconsistently

3. Given these Redis keys:
user:1000:name
user:1000:email
user:1001:name
Which command will return all keys for user 1000?

medium

A. KEYS user:1000:*

B. KEYS user:*:name

C. KEYS user:1001:*

D. KEYS *:email

Solution

1. Step 1: Understand the key pattern

   Keys for user 1000 start with 'user:1000:' followed by any suffix.

2. Step 2: Match the pattern with the command

   The command 'KEYS user:1000:*' matches all keys starting with 'user:1000:'.

3. Final Answer:

   KEYS user:1000:* -> Option A

4. Quick Check:

   Pattern matches user 1000 keys [OK]

Hint: Use * wildcard after user:1000: to get all keys [OK]

Common Mistakes:

• Using wrong user ID in pattern
• Using wildcard in wrong position
• Confusing name and email keys

4. You have keys named session:1234 and session-1234. You want to list all session keys using KEYS session:* but it returns only session:1234. What is the issue?

medium

A. The command syntax is incorrect

B. Redis does not support dashes in keys

C. Keys with dashes are automatically deleted

D. Keys with dashes are not matched by colon wildcard

Solution

1. Step 1: Understand pattern matching

   The pattern 'session:*' matches keys starting with 'session:' only, not 'session-'.

2. Step 2: Identify why keys with dashes are missed

   Keys with dashes do not match the colon separator pattern, so they are excluded.

3. Final Answer:

   Keys with dashes are not matched by colon wildcard -> Option D

4. Quick Check:

   Colon wildcard matches only colon keys [OK]

Hint: Wildcards match exact separators; dashes differ from colons [OK]

Common Mistakes:

• Thinking dashes are invalid in Redis keys
• Assuming command syntax is wrong
• Believing keys with dashes get deleted

5. You want to store user data in Redis with keys for profile and settings. Which key naming scheme best follows Redis conventions for easy management?

hard

A. user:1000:profile and user:1000:settings

B. user1000profile and user1000settings

C. user-profile-1000 and user-settings-1000

D. profile:user:1000 and settings:user:1000

Solution

1. Step 1: Identify clear namespacing

   Using 'user:1000' as a prefix groups all user data logically.

2. Step 2: Check key suffixes for data types

   'profile' and 'settings' as suffixes clearly describe the data stored.

3. Step 3: Compare options

   user:1000:profile and user:1000:settings uses colons consistently for namespacing and clarity.

4. Final Answer:

   user:1000:profile and user:1000:settings -> Option A

5. Quick Check:

   Consistent colon namespacing = user:1000:profile and user:1000:settings [OK]

Hint: Use user:id:data_type format with colons [OK]

Common Mistakes:

• Not using colons for clear separation
• Mixing order of parts inconsistently
• Using ambiguous key names