Why data modeling differs in Redis - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does Redis data modeling differ from traditional relational databases?

Redis is a key-value store with different data structures than relational databases. Which reason best explains why data modeling in Redis differs?

A Redis supports various data structures like lists, sets, and hashes, requiring different modeling approaches.

B Redis uses tables and rows like relational databases, so modeling is the same.

C Redis stores data as simple strings only, so complex models are impossible.

D Redis automatically converts all data into JSON format, so modeling is standardized.

💡 Hint

Think about the types of data Redis can store beyond simple strings.

Redis supports multiple data structures such as lists, sets, sorted sets, and hashes. This flexibility means data modeling must consider these structures rather than just tables and rows.

❓ query_result

intermediate

What is the output of this Redis command sequence?

Given the following Redis commands, what is the output of LRANGE mylist 0 -1?

LPUSH mylist "apple"
LPUSH mylist "banana"
LPUSH mylist "cherry"

A ["banana", "apple", "cherry"]

B ["apple", "banana", "cherry"]

C ["cherry", "banana", "apple"]

D []

💡 Hint

Remember that LPUSH adds elements to the head (left) of the list.

LPUSH adds elements to the start of the list, so the last pushed element is first. The list order is cherry, banana, apple.

📝 Syntax

advanced

Which Redis command syntax correctly adds a member to a set?

Choose the correct Redis command syntax to add the member "orange" to the set "fruits".

A SET fruits orange

B LPUSH fruits orange

C ADD fruits orange

D SADD fruits orange

💡 Hint

Sets in Redis use a specific command to add members.

The SADD command adds one or more members to a set. ADD and SET are invalid commands for sets, and LPUSH is for lists.

❓ optimization

advanced

How to optimize Redis data modeling for fast retrieval of user sessions?

You want to store user session data in Redis for quick access. Which data modeling approach is best for fast retrieval by session ID?

A Store each session as a separate key with a hash containing session fields.

B Store all sessions in a single large list and scan it to find sessions.

C Store sessions as JSON strings in a sorted set with timestamps as scores.

D Store sessions in a Redis stream and read all entries sequentially.

💡 Hint

Consider how to quickly access a session by its unique ID.

Storing each session as a separate key with a hash allows direct access by session ID, which is fast. Lists and streams require scanning, which is slower.

🔧 Debug

expert

Why does this Redis Lua script fail to update a hash field?

Given this Lua script run in Redis, why does the field "count" not update as expected?

local key = KEYS[1]
local field = ARGV[1]
local increment = tonumber(ARGV[2])
local current = redis.call('HGET', key, field)
if not current then
  current = 0
else
  current = tonumber(current)
end
redis.call('HSET', key, field, current + increment)

A The script does not return any value, so the update is not saved.

B The script does not handle the case when the existing field value is non-numeric correctly.

C The script uses HSET instead of HINCRBY, causing the update to fail.

D The variable 'current' is not converted to a number before addition.

💡 Hint

Check what happens if the field exists but contains a non-numeric value.

If 'current' is nil, the script sets it to 0 as a number, which is correct. However, if 'current' is a string that cannot convert to number, tonumber(current) returns nil, causing an error in addition.