Why replication provides redundancy in Redis - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set up a Redis replica.

Redis

replicaof [1] 6379

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

A0.0.0.0

Blocalhost

C192.168.1.100

D127.0.0.1

Attempts:

3 left

💡 Hint

Common Mistakes

Using an incorrect IP address that does not point to the master.

Using 'localhost' instead of '127.0.0.1' in some Redis configurations.

The replicaof command tells Redis to replicate data from the master at the given IP address. Using 127.0.0.1 means the replica connects to the master on the same machine.

2fill in blank

medium

Complete the command to check the role of a Redis instance.

Redis

info replication | grep [1]

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

Aslave

Bmaster

Crole

Dconnected

Attempts:

3 left

💡 Hint

Common Mistakes

Searching for 'master' or 'slave' directly instead of 'role'.

Using incorrect grep patterns that return no results.

The info replication command shows replication info. Filtering by role shows if the instance is a master or replica.

3fill in blank

hard

Fix the error in the command to promote a replica to master.

Redis

redis-cli [1]

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

Areplicaof noone

Breplicaof no one

Creplicaof none

Dreplicaof no_one

Attempts:

3 left

💡 Hint

Common Mistakes

Writing 'noone' as one word.

Using 'none' or underscores instead of spaces.

The correct command to promote a replica to master is replicaof no one with spaces.

4fill in blank

hard

Fill both blanks to complete the Redis configuration for replication.

Redis

replicaof [1] [2]

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

A192.168.0.10

B6379

C6380

Dlocalhost

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping IP and port positions.

Using wrong port numbers.

The replicaof command requires the master's IP and port. Here, 192.168.0.10 is the master IP and 6379 is the default Redis port.

5fill in blank

hard

Fill all three blanks to create a Redis command that sets a key with replication enabled.

Redis

redis-cli -h [1] -p [2] set [3] "value"

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

A127.0.0.1

B6379

Cmykey

Dlocalhost

Attempts:

3 left

💡 Hint

Common Mistakes

Using IP instead of hostname inconsistently.

Forgetting to specify the key name.

This command connects to Redis at localhost on port 6379 and sets the key mykey with the value "value". Replication will propagate this change to replicas.

Practice

1. Why does replication in Redis provide redundancy?

easy

A. Because it speeds up data processing by using multiple CPUs

B. Because it copies data to multiple servers to prevent data loss

C. Because it compresses data to save storage space

D. Because it deletes old data to free memory

Solution

1. Step 1: Understand replication purpose

   Replication copies data from the main server to other servers.

2. Step 2: Connect replication to redundancy

   This copying creates backups, so if one server fails, data is not lost.

3. Final Answer:

   Because it copies data to multiple servers to prevent data loss -> Option B

4. Quick Check:

   Replication = Data backup [OK]

Hint: Replication means copying data to keep backups safe [OK]

Common Mistakes:

• Thinking replication speeds up processing
• Confusing replication with data compression
• Believing replication deletes old data

2. Which Redis command is used to set up a replica for redundancy?

easy

A. REPLICA

B. REPLICAOF

C. SLAVEOF

D. SET key value

Solution

1. Step 1: Recall Redis replication command

   The command to make a Redis server a replica is SLAVEOF; REPLICAOF is not a valid Redis command.

2. Step 2: Check options for exact syntax

   SLAVEOF <master-ip> <master-port> is the correct command and syntax.

3. Final Answer:

   SLAVEOF <master-ip> <master-port> -> Option C

4. Quick Check:

   Replica setup command = SLAVEOF [OK]

Hint: Remember replica setup uses SLAVEOF command [OK]

Common Mistakes:

• Using the non-existent REPLICAOF
• Confusing SET with replication commands
• Using REPLICA without OF

3. Given a Redis master with key user:1 set to "Alice", what will a replica show after replication?

medium

A. user:1 = "Alice"

B. user:1 = null

C. user:1 = "Bob"

D. user:1 key will be deleted

Solution

1. Step 1: Understand replication data flow

   The replica copies data from the master, so keys and values match.

2. Step 2: Predict replica key value

   Since master has user:1 = "Alice", replica will have the same.

3. Final Answer:

   user:1 = "Alice" -> Option A

4. Quick Check:

   Replica data = Master data [OK]

Hint: Replica always matches master data after sync [OK]

Common Mistakes:

• Assuming replica has no data initially
• Thinking replica changes values independently
• Believing keys get deleted on replica

4. You set up a Redis replica but it never syncs data from the master. What is the likely error?

medium

A. The master server has no data to replicate

B. The replica server has more memory than the master

C. The replica server is running an older Redis version

D. The replica IP or port is incorrect in the SLAVEOF command

Solution

1. Step 1: Identify common replication setup errors

   Incorrect IP or port in SLAVEOF prevents connection to master.

2. Step 2: Analyze other options

   Master having no data doesn't stop syncing; version mismatch usually warns; memory size difference doesn't block replication.

3. Final Answer:

   The replica IP or port is incorrect in the SLAVEOF command -> Option D

4. Quick Check:

   Wrong master address = no sync [OK]

Hint: Check SLAVEOF IP and port carefully [OK]

Common Mistakes:

• Ignoring connection details in SLAVEOF
• Assuming no data means no replication
• Blaming Redis version without checking logs

5. In a Redis setup, why is having multiple replicas important for redundancy beyond just one replica?

hard

A. Because if one replica fails, others still have the data

B. Because multiple replicas speed up writes to the master

C. Because replicas automatically compress data to save space

D. Because replicas prevent the master from crashing

Solution

1. Step 1: Understand redundancy with multiple replicas

   Multiple replicas mean data is copied to several servers, so failure of one replica doesn't cause data loss.

2. Step 2: Evaluate other options

   Replicas do not speed up writes, compress data, or prevent master crashes directly.

3. Final Answer:

   Because if one replica fails, others still have the data -> Option A

4. Quick Check:

   Multiple replicas = higher data safety [OK]

Hint: More replicas mean safer data if one fails [OK]

Common Mistakes:

• Thinking replicas speed up master writes
• Believing replicas compress data automatically
• Assuming replicas protect master from crashes