Why hashes represent objects in Redis - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why are hashes used to represent objects in Redis?

In Redis, hashes are often used to represent objects. Why is this approach beneficial compared to using simple strings for each attribute?

A Because hashes allow grouping multiple fields and values under one key, making it easier to manage related data as a single object.

B Because hashes automatically encrypt the data stored inside, providing security for objects.

C Because hashes consume more memory than strings, which improves performance.

D Because hashes store data in a sorted order, which strings cannot do.

💡 Hint

Think about how you would store a user profile with multiple details in Redis.

Hashes let you store multiple related fields (like name, age, email) under one key. This groups data logically and makes it easier to retrieve or update parts of the object without handling many separate keys.

❓ query_result

intermediate

What does this Redis command output?

Given the following Redis commands executed in order, what is the output of the last command?

HSET user:1 name "Alice" age "30" city "Paris"
HGETALL user:1

Redis

HSET user:1 name "Alice" age "30" city "Paris"
HGETALL user:1

A Error: HGETALL command not found

B ["user:1", "name", "Alice", "age", "30", "city", "Paris"]

C ["name", "Alice"]

D ["name", "Alice", "age", "30", "city", "Paris"]

💡 Hint

HGETALL returns all fields and values in the hash as a list.

The HGETALL command returns all fields and their values stored in the hash as a flat list of alternating keys and values.

📝 Syntax

advanced

Identify the syntax error in this Redis hash command

Which option contains a syntax error when trying to add fields to a Redis hash named 'product:100'?

Redis

HSET product:100 name "Laptop" price 1200 stock 30

A HSET product:100 name "Laptop" price 1200 stock 30

B HSET product:100 name "Laptop" price "1200" stock "30"

C HSET product:100 (name "Laptop" price 1200 stock 30)

D HSET product:100 name Laptop price 1200 stock 30

💡 Hint

Check the use of parentheses in Redis commands.

Redis commands do not use parentheses to group arguments. Option C incorrectly uses parentheses, causing a syntax error.

❓ optimization

advanced

Optimizing storage of user profiles in Redis

You want to store 10,000 user profiles in Redis. Each profile has 5 fields: name, email, age, city, and phone. Which approach is most efficient in terms of memory and access speed?

A Store each field of every user as a separate Redis string key, e.g., user:1:name, user:1:email, etc.

B Store each user profile as a Redis hash with one key per user containing all 5 fields.

C Store all user profiles in a single Redis list, each element a JSON string of the profile.

D Store user profiles as Redis sets with each field as a member.

💡 Hint

Consider grouping related data and efficient retrieval.

Using hashes groups related fields under one key, reducing overhead and allowing efficient access to individual fields without retrieving the entire object or multiple keys.

🔧 Debug

expert

Why does this Redis hash command fail to update the field?

You run the following commands:

HSET user:42 name "Bob" age "25"
HSET age 26
HGET user:42 age

But the last command returns "25" instead of "26". What is the most likely reason?

A The second HSET command is missing the hash key argument, so it does not update the intended hash.

B The Redis server is caching the old value and did not update the field.

C The second HSET command is missing quotes around the key, causing it to create a new key instead of updating.

D The second HSET command is interpreted as setting a new key named 'age' instead of updating the hash.

💡 Hint

Check the number of arguments in the second HSET command.

The second HSET command lacks the hash key argument, so Redis treats 'age' as the key and '26' as the field, not updating the intended hash 'user:42'.