Why persistence matters in Redis - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is persistence important in Redis?

Redis is an in-memory database. What is the main reason to enable persistence in Redis?

A To save data to disk so it is not lost if the server restarts or crashes

B To speed up data retrieval by caching data in memory

C To allow multiple clients to connect simultaneously

D To encrypt data for security purposes

💡 Hint

Think about what happens if the server loses power suddenly.

Persistence saves data to disk so Redis can recover data after a restart or crash. Without persistence, all data in memory would be lost.

❓ query_result

intermediate

What happens to data without persistence?

Assume Redis is running without any persistence enabled. You add a key-value pair user:1 -> 'Alice'. Then the server crashes and restarts. What will be the result of GET user:1 after restart?

A It returns an empty string because the key exists but has no value

B It returns null because data was lost after restart

C It returns an error because the key is corrupted

D It returns 'Alice' because data is stored in memory

💡 Hint

Consider what happens to in-memory data when the server restarts without saving it.

Without persistence, Redis only keeps data in memory. On restart, memory is cleared, so keys are lost and GET returns null.

📝 Syntax

advanced

Which Redis command enables snapshot persistence?

Which command configures Redis to save snapshots of the dataset to disk at regular intervals?

A SAVE

B PERSIST

C BGSAVE

D CONFIG SET save

💡 Hint

Think about how to configure automatic snapshot intervals.

CONFIG SET save sets the snapshotting intervals in Redis configuration. SAVE and BGSAVE trigger immediate snapshots. PERSIST removes expiration from keys.

❓ optimization

advanced

Choosing persistence for performance and durability

You want Redis to persist data but minimize performance impact. Which persistence method balances durability and speed best?

A RDB snapshots only

B No persistence, rely on replication

C AOF with fsync every second

D AOF (Append Only File) with fsync always

💡 Hint

Consider how often data is written to disk and its effect on speed.

AOF with fsync every second writes data asynchronously, providing good durability with less performance cost than fsync always. RDB snapshots are faster but less durable. No persistence risks data loss.

🔧 Debug

expert

Why does Redis lose data despite persistence enabled?

You enabled both RDB snapshots and AOF persistence in Redis. However, after a server crash, some recent writes are missing. What is the most likely cause?

A AOF fsync policy is set to 'no' causing delayed writes to disk

B RDB snapshots overwrite AOF file causing data loss

C Redis does not support combining RDB and AOF persistence

D The server crashed before Redis could start

💡 Hint

Check how often Redis flushes AOF data to disk.

If AOF fsync is set to 'no', Redis buffers writes in memory and writes to disk less frequently, risking data loss on crash. RDB and AOF can be combined safely. Server crash timing matters.