Why data modeling differs in Redis - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set a string value in Redis.

Redis

SET mykey [1]

Drag options to blanks, or click blank then click option'

A123

B"Hello"

CHello

Dnil

Attempts:

3 left

💡 Hint

Common Mistakes

Using quotes around string values causes errors.

Using nil which is not a valid value.

In Redis, string values do not need to be enclosed in quotes when setting them as literals in commands.

2fill in blank

medium

Complete the code to add a member to a Redis set.

Redis

SADD myset [1]

Drag options to blanks, or click blank then click option'

Amyvalue

B123

C"myvalue"

Dnil

Attempts:

3 left

💡 Hint

Common Mistakes

Adding quoted strings unnecessarily.

Using nil which is not a valid member.

Redis commands accept string arguments without quotes unless they contain spaces or special characters.

3fill in blank

hard

Fix the error in the command to get a hash field value.

Redis

HGET myhash [1]

Drag options to blanks, or click blank then click option'

Afield1

Bnil

C1

D"field1"

Attempts:

3 left

💡 Hint

Common Mistakes

Using quoted field names unnecessarily.

Using numeric or nil values incorrectly.

Hash field names in Redis commands do not need to be quoted strings unless they contain spaces or special characters.

4fill in blank

hard

Fill both blanks to create a sorted set with a member and score.

Redis

ZADD myzset [1] [2]

Drag options to blanks, or click blank then click option'

A10

B"member1"

Cmember1

Dscore

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping score and member order.

Quoting the member string unnecessarily.

ZADD requires the score first (a number), then the member (a string without quotes unless it contains spaces).

5fill in blank

hard

Fill all three blanks to create a Redis hash with a field and value.

Redis

HSET [1] [2] [3]

Drag options to blanks, or click blank then click option'

Amyhash

B"field1"

C"value1"

Dfield1

Attempts:

3 left

💡 Hint

Common Mistakes

Quoting field unnecessarily.

Using unquoted value with spaces causing errors.

HSET command syntax: key, field (string), and value (string). Field and value do not need quotes unless they contain spaces or special characters.

Practice

1. Why does data modeling in Redis differ from traditional relational databases?

easy

A. Because Redis uses SQL queries for data access

B. Because Redis stores data in memory using simple data types, not tables

C. Because Redis requires complex joins for data retrieval

D. Because Redis stores data only on disk

Solution

1. Step 1: Understand Redis data storage

   Redis stores data in memory using simple data types like strings, lists, sets, hashes, and sorted sets instead of tables.

2. Step 2: Compare with relational databases

   Relational databases store data in tables and use SQL for complex queries, which is different from Redis's in-memory key-value approach.

3. Final Answer:

   Because Redis stores data in memory using simple data types, not tables -> Option B

4. Quick Check:

   Redis data model = simple in-memory types [OK]

Hint: Remember Redis uses keys and simple types, not tables [OK]

Common Mistakes:

• Thinking Redis uses SQL queries
• Assuming Redis stores data on disk only
• Believing Redis requires complex joins

2. Which of the following is the correct way to set a string value in Redis?

easy

A. SET key value

B. INSERT INTO key VALUES value

C. ADD key value

D. CREATE key value

Solution

1. Step 1: Recall Redis command for setting string

   The Redis command to set a string value is SET key value.

2. Step 2: Eliminate incorrect SQL-like commands

   Commands like INSERT INTO, ADD, and CREATE are not valid Redis commands.

3. Final Answer:

   SET key value -> Option A

4. Quick Check:

   Redis string set = SET key value [OK]

Hint: Use SET command to store strings in Redis [OK]

Common Mistakes:

• Using SQL syntax like INSERT INTO
• Confusing ADD with SET
• Trying to CREATE keys like tables

3. Given the Redis commands:
LPUSH fruits apple
LPUSH fruits banana
LRANGE fruits 0 -1
What is the output of the LRANGE command?

medium

A. ["apple", "banana"]

B. ["apple"]

C. ["banana", "apple"]

D. Syntax error

Solution

1. Step 1: Understand LPUSH behavior

   LPUSH adds elements to the head (left) of the list. First 'apple' is pushed, then 'banana' is pushed before it.

2. Step 2: Check LRANGE output order

   LRANGE 0 -1 returns all elements from start to end, so the list is ["banana", "apple"].

3. Final Answer:

   ["banana", "apple"] -> Option C

4. Quick Check:

   LPUSH adds left, so newest first [OK]

Hint: LPUSH adds to front; LRANGE shows list from front [OK]

Common Mistakes:

• Assuming LPUSH adds to the end
• Confusing order of elements in LRANGE
• Expecting syntax error from correct commands

4. You run the command HSET user:1 name "Alice" age 30 in Redis but get an error. What is the likely cause?

medium

A. The command syntax is correct; error is elsewhere

B. HSET does not accept multiple field-value pairs in one command

C. The age value must be a string, not a number

D. HSET requires field-value pairs, but age is not quoted

Solution

1. Step 1: Verify HSET syntax

   HSET accepts a key followed by field-value pairs (multiple allowed). Unquoted integers like 30 are valid and stored as strings "30". No syntax error here.

2. Step 2: Identify likely error sources

   Errors could stem from connection issues, insufficient permissions, Redis server not running, or client-specific parsing problems.

3. Final Answer:

   The command syntax is correct; error is elsewhere -> Option A

4. Quick Check:

   HSET user:1 name "Alice" age 30 [OK]

Hint: HSET supports multiple pairs; unquoted numbers OK [OK]

Common Mistakes:

• Thinking numbers must be quoted in HSET
• Believing HSET rejects multiple field-value pairs
• Overlooking connection or permission issues

5. You want to model a user profile in Redis with fast access to username, email, and a list of friends. Which data modeling approach is best?

hard

A. Store all data as a single JSON string in a Redis string key

B. Create a relational table in Redis for user profiles

C. Use multiple Redis lists for each field

D. Use a Redis hash for username and email, and a Redis set for friends

Solution

1. Step 1: Identify data types for each field

   Username and email are simple key-value pairs, best stored in a Redis hash for grouped access. Friends are a collection, best stored in a Redis set for uniqueness and fast membership checks.

2. Step 2: Evaluate other options

   Storing all data as JSON string loses Redis data type benefits. Multiple lists for each field is inefficient. Redis does not support relational tables.

3. Final Answer:

   Use a Redis hash for username and email, and a Redis set for friends -> Option D

4. Quick Check:

   Hashes for objects, sets for unique collections [OK]

Hint: Use hashes for objects and sets for unique lists [OK]

Common Mistakes:

• Storing everything as JSON string
• Using lists for unique friend sets
• Expecting relational tables in Redis