Why persistence matters in Redis - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to save the current Redis database state to disk immediately.

Redis

redis-cli [1]

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

ASAVE

BFLUSHDB

CGET

DDEL

Attempts:

3 left

💡 Hint

Common Mistakes

Using FLUSHDB deletes data instead of saving it.

Using GET or DEL does not save data.

The SAVE command forces Redis to save the dataset to disk immediately, ensuring data persistence.

2fill in blank

medium

Complete the code to enable Redis to save snapshots every 60 seconds if at least 1000 keys changed.

Redis

save [1] 1000

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

A30

B120

C300

D60

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a time interval too short or too long for the requirement.

The configuration save 60 1000 tells Redis to save a snapshot every 60 seconds if 1000 keys changed, helping persistence.

3fill in blank

hard

Fix the error in the command to rewrite the AOF file for persistence.

Redis

redis-cli [1]

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

ABGREWRITEAOF

BAPPENDAOF

CAOFAPPEND

DBGSAVE

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent commands like APPENDAOF or AOFAPPEND.

Confusing with BGSAVE which saves RDB snapshots.

The correct command to rewrite the Append Only File (AOF) in the background is BGREWRITEAOF. It helps maintain persistence efficiently.

4fill in blank

hard

Fill both blanks to configure Redis to use AOF persistence and disable RDB preamble in AOF files.

Redis

appendonly [1]
aof-use-rdb-preamble [2]

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

Ayes

Bno

Ceverysec

Dalways

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing fsync policy with aof-use-rdb-preamble setting.

Using 'everysec' or 'always' for boolean options.

Setting appendonly yes enables AOF persistence. Setting aof-use-rdb-preamble no disables RDB preamble in AOF files.

5fill in blank

hard

Fill all three blanks to create a Redis configuration snippet that enables AOF, sets fsync policy to every second, and disables RDB snapshots.

Redis

appendonly [1]
appendfsync [2]
save [3]

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

Ayes

Beverysec

C""

Dno

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'no' to enable AOF.

Setting fsync to 'always' instead of 'everysec'.

Not disabling RDB snapshots properly.

Enable AOF with appendonly yes, set fsync to every second with appendfsync everysec, and disable RDB snapshots by setting save "".

Practice

1. Why is persistence important in Redis?

easy

A. It encrypts data for security during transmission.

B. It speeds up data retrieval by caching in memory.

C. It saves data to disk to prevent data loss after a restart.

D. It automatically deletes old data to free memory.

Solution

1. Step 1: Understand persistence purpose

   Persistence means saving data to disk so it is not lost when Redis restarts or crashes.

2. Step 2: Compare options

   Only the option stating 'It saves data to disk to prevent data loss after a restart.' describes saving data to disk to prevent loss. Others describe caching, deleting, or encryption, which are unrelated to persistence.

3. Final Answer:

   It saves data to disk to prevent data loss after a restart. -> Option C

4. Quick Check:

   Persistence = saving data safely [OK]

Hint: Persistence means saving data to disk to avoid loss [OK]

Common Mistakes:

• Confusing persistence with caching
• Thinking persistence deletes data
• Mixing persistence with encryption

2. Which Redis configuration option controls how often data is saved to disk?

easy

A. save

B. maxmemory-policy

C. appendonly

D. timeout

Solution

1. Step 1: Identify persistence settings

   Redis uses the save option to specify intervals for saving snapshots to disk.

2. Step 2: Eliminate other options

   maxmemory-policy controls eviction, appendonly enables AOF persistence, and timeout sets client timeout, not snapshot frequency.

3. Final Answer:

   save -> Option A

4. Quick Check:

   save = snapshot frequency setting [OK]

Hint: Remember 'save' sets snapshot intervals in Redis config [OK]

Common Mistakes:

• Confusing appendonly with save
• Thinking maxmemory-policy controls saving
• Mixing timeout with persistence

3. Given this Redis config snippet:

save 900 1
save 300 10
save 60 10000

What does this configuration mean?

medium

A. Save data every 900 seconds if at least 1 key changed, every 300 seconds if 10 keys changed, and every 60 seconds if 10000 keys changed.

B. Save data every 900 seconds regardless of changes, every 300 seconds if 10 keys changed, and every 60 seconds if 10000 keys changed.

C. Save data only once after 900 seconds, ignoring key changes.

D. Save data every 900 seconds if 900 keys changed, every 300 seconds if 300 keys changed, and every 60 seconds if 60 keys changed.

Solution

1. Step 1: Understand Redis save syntax

   Each line means: save after X seconds if at least Y keys changed. For example, save 900 1 means save after 900 seconds if 1 or more keys changed.

2. Step 2: Match lines to meaning

   Lines specify different intervals and minimum changed keys: 900s/1 key, 300s/10 keys, 60s/10000 keys.

3. Final Answer:

   Save data every 900 seconds if at least 1 key changed, every 300 seconds if 10 keys changed, and every 60 seconds if 10000 keys changed. -> Option A

4. Quick Check:

   save X Y means save after X seconds if Y keys changed [OK]

Hint: Remember save X Y means save after X seconds if Y keys changed [OK]

Common Mistakes:

• Ignoring the minimum changed keys condition
• Assuming save happens regardless of changes
• Mixing seconds and keys numbers

4. You set appendonly yes in Redis config but data is not saved after restart. What is the likely problem?

medium

A. The appendfsync setting is set to 'no', so AOF is disabled.

B. The Redis server was not restarted after changing the config.

C. The save option must be enabled for AOF to work.

D. The appendonly.aof file is missing or corrupted.

Solution

1. Step 1: Understand AOF persistence

   Setting appendonly yes enables AOF persistence, which logs every write operation to a file.

2. Step 2: Identify why data might not persist

   If the AOF file is missing or corrupted, Redis cannot restore data on restart, causing data loss despite the setting.

3. Final Answer:

   The appendonly.aof file is missing or corrupted. -> Option D

4. Quick Check:

   AOF file missing = no data restored [OK]

Hint: Check if AOF file exists and is valid when appendonly is yes [OK]

Common Mistakes:

• Thinking appendfsync 'no' disables AOF (it controls fsync frequency)
• Assuming save option affects AOF
• Forgetting to restart Redis after config changes

5. You want to ensure Redis never loses more than 5 minutes of data after a crash. Which persistence setup is best?

hard

A. Enable RDB snapshots every 900 seconds and disable AOF.

B. Enable both RDB snapshots every 300 seconds and AOF with appendfsync 'everysec'.

C. Enable AOF with appendfsync set to 'everysec' and disable RDB snapshots.

D. Disable both RDB and AOF to improve performance.

Solution

1. Step 1: Understand persistence options

   RDB snapshots save data at intervals (e.g., every 300 seconds). AOF logs every write and can fsync every second.

2. Step 2: Match requirement to config

   To lose no more than 5 minutes (300 seconds) of data, snapshots alone are risky. Combining snapshots every 300s with AOF fsync every second minimizes data loss.

3. Step 3: Evaluate options

   The option to enable both RDB snapshots every 300 seconds and AOF with appendfsync 'everysec' enables both methods with appropriate intervals, ensuring minimal data loss. Others either save less often or disable persistence.

4. Final Answer:

   Enable both RDB snapshots every 300 seconds and AOF with appendfsync 'everysec'. -> Option B

5. Quick Check:

   Combine snapshots + AOF for best data safety [OK]

Hint: Use both snapshots and AOF for minimal data loss [OK]

Common Mistakes:

• Relying on snapshots alone for short data loss windows
• Disabling persistence to improve speed
• Setting appendfsync to 'no' or 'always' incorrectly