Why patterns guide Redis usage - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is it important to follow usage patterns in Redis?

Redis is a fast, in-memory database. Why do developers follow specific usage patterns when working with Redis?

A Because patterns make Redis slower but more secure.

B Because Redis only supports one data type and patterns help simulate others.

C Because Redis automatically fixes bad usage without patterns.

D Because Redis requires patterns to optimize memory and speed effectively.

💡 Hint

Think about how Redis stores data and what affects its performance.

Redis is designed for speed and efficiency. Using recommended patterns helps use memory wisely and keeps operations fast.

❓ query_result

intermediate

What is the output of this Redis command sequence?

Given these Redis commands executed in order:

SET user:1 "Alice"
HSET user:1:stats visits 5
HINCRBY user:1:stats visits 1
GET user:1
HGET user:1:stats visits

What are the values returned by the GET and HGET commands?

A "Alice" and "5"

B "Alice" and "6"

C nil and "6"

D nil and nil

💡 Hint

Remember that HINCRBY increases the integer value of a hash field by 1.

The GET user:1 returns "Alice" because it was set. The HGET returns "6" because HINCRBY increased the visits from 5 to 6.

📝 Syntax

advanced

Which Redis command syntax correctly adds multiple members to a set?

Choose the correct Redis command to add members 'apple', 'banana', and 'cherry' to the set 'fruits'.

A SADD fruits apple banana cherry

B ADD fruits apple banana cherry

C SADD fruits ['apple', 'banana', 'cherry']

D SET fruits apple banana cherry

💡 Hint

Recall the command used to add members to a set in Redis.

SADD is the correct command to add one or more members to a set. The other commands are invalid or incorrect.

❓ optimization

advanced

How can you optimize Redis memory usage when storing user sessions?

You want to store user sessions in Redis efficiently. Which approach optimizes memory usage best?

A Store each session as a JSON string in a Redis string key.

B Use Redis sorted sets with session IDs as members and timestamps as scores.

C Use Redis hashes to store session fields separately under one key per session.

D Store all sessions in a single Redis list key.

💡 Hint

Think about how Redis hashes store multiple fields efficiently.

Redis hashes are memory efficient for storing many small fields per key, making them ideal for session data.

🔧 Debug

expert

Why does this Redis Lua script cause an error?

Consider this Lua script run in Redis:

local count = redis.call('INCR', KEYS[1])
if count == 1 then
  redis.call('EXPIRE', KEYS[1], ARGV[1])
end
return count

When running with redis-cli --eval script.lua , 10, it returns an error. What is the cause?

A The script uses KEYS[1] but no keys were passed to the command.

B EXPIRE requires the key to exist before setting expiration.

C INCR cannot be used inside Lua scripts.

D ARGV[1] is a string and must be converted to number before EXPIRE.

💡 Hint

Check how keys and arguments are passed to Redis Lua scripts.

The error occurs because the script expects a key in KEYS[1], but the command line did not pass any keys, only arguments. The correct usage requires keys before the comma.