Production deployment best practices in Redis - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why enable AOF persistence in Redis production?

Redis supports different persistence methods. Why is enabling Append Only File (AOF) recommended for production deployments?

A AOF disables all persistence, making Redis faster but less reliable.

B AOF compresses data to save disk space, improving storage efficiency.

C AOF provides better durability by logging every write operation, reducing data loss risk.

D AOF automatically replicates data to all connected clients for backup.

💡 Hint

Think about how Redis can recover data after a crash.

AOF logs every write operation, so Redis can replay these commands to restore data after a restart, minimizing data loss compared to snapshotting alone.

🧠 Conceptual

intermediate

What is the role of Redis Sentinel in production?

Redis Sentinel is often used in production environments. What is its main purpose?

A Sentinel disables persistence to improve Redis performance.

B Sentinel compresses Redis data to optimize memory usage.

C Sentinel provides a graphical user interface for Redis management.

D Sentinel monitors Redis instances and automatically promotes a replica to master if the master fails.

💡 Hint

Consider how Redis handles failover and high availability.

Redis Sentinel monitors the health of Redis masters and replicas. If the master fails, Sentinel promotes a replica to master automatically to maintain availability.

❓ query_result

advanced

What is the output of the Redis INFO command regarding persistence?

Given a Redis server with AOF enabled and RDB snapshots configured, what will the INFO Persistence section show for aof_enabled and rdb_bgsave_in_progress if a background save is running?

Redis

INFO Persistence

A aof_enabled:1\nrdb_bgsave_in_progress:1

B aof_enabled:0\nrdb_bgsave_in_progress:0

C aof_enabled:0\nrdb_bgsave_in_progress:1

D aof_enabled:1\nrdb_bgsave_in_progress:0

💡 Hint

Check what values indicate enabled features and running processes.

If AOF is enabled, aof_enabled shows 1. If a background RDB save is running, rdb_bgsave_in_progress is 1.

🔧 Debug

advanced

Identify the cause of Redis master-slave replication lag

A Redis slave is lagging behind the master in a production setup. Which of the following is the most likely cause?

A The slave is running Redis in cluster mode, which disables replication.

B The slave has a slow network connection causing delayed replication.

C The master has persistence disabled, causing replication to stop.

D The master is configured with AOF, which disables replication automatically.

💡 Hint

Think about what affects data transfer speed between master and slave.

A slow network connection between master and slave can cause replication lag because data takes longer to reach the slave.

❓ optimization

expert

Best practice to optimize Redis memory usage in production

Which option is the best practice to optimize Redis memory usage for large datasets in production?

A Use Redis <code>maxmemory-policy</code> with an eviction strategy like <code>allkeys-lru</code> to remove least recently used keys when memory is full.

B Disable persistence to save disk space and improve memory usage.

C Increase Redis maxmemory to unlimited to avoid evictions.

D Store all data as strings to simplify memory management.

💡 Hint

Consider how Redis handles memory limits and eviction.

Setting a maxmemory policy with eviction allows Redis to automatically remove less important keys when memory is full, preventing crashes and optimizing usage.

Practice

1. Which of the following is a recommended security practice when deploying Redis in production?

easy

A. Use password protection to restrict access

B. Disable all logging to improve performance

C. Allow open access from any IP address

D. Run Redis without any authentication

Solution

1. Step 1: Understand Redis security basics

   Redis should be protected to prevent unauthorized access, especially in production.

2. Step 2: Identify the best security method

   Using password protection is a simple and effective way to secure Redis.

3. Final Answer:

   Use password protection to restrict access -> Option A

4. Quick Check:

   Security = Password protection [OK]

Hint: Always secure Redis with a password in production [OK]

Common Mistakes:

• Ignoring authentication setup
• Allowing open network access
• Disabling logs reduces security

2. Which Redis configuration directive sets a maximum memory limit to prevent out-of-memory errors?

easy

A. maxmemory

B. appendonly

C. timeout

D. maxclients

Solution

1. Step 1: Identify memory control directives

   Redis uses maxmemory to limit the memory usage.

2. Step 2: Match directive to purpose

   maxmemory sets the max RAM Redis can use to avoid crashes.

3. Final Answer:

   maxmemory -> Option A

4. Quick Check:

   Memory limit = maxmemory [OK]

Hint: Memory limit is set by maxmemory directive [OK]

Common Mistakes:

• Confusing maxclients with memory limit
• Using timeout for memory control
• appendonly is for persistence, not memory

3. Given the Redis config snippet:

maxmemory 100mb
maxmemory-policy allkeys-lru

What will happen when Redis reaches 100mb memory usage?

medium

A. Redis will stop accepting writes and return errors

B. Redis will delete only keys with expiration set

C. Redis will crash due to out-of-memory

D. Redis will evict least recently used keys from all keys to free memory

Solution

1. Step 1: Understand maxmemory and eviction policy

   maxmemory limits Redis memory to 100mb; maxmemory-policy defines eviction behavior.

2. Step 2: Interpret allkeys-lru policy

   allkeys-lru evicts least recently used keys from all keys, not just expired ones.

3. Final Answer:

   Redis will evict least recently used keys from all keys to free memory -> Option D

4. Quick Check:

   Eviction policy allkeys-lru = evict LRU keys [OK]

Hint: allkeys-lru evicts any LRU key when memory full [OK]

Common Mistakes:

• Thinking Redis stops writes on memory full
• Confusing eviction of expired keys only
• Assuming Redis crashes on memory limit

4. You configured Redis with:

save ""
appendonly no

What is the problem with this configuration in production?

medium

A. Redis will save data too frequently, causing performance issues

B. Redis will not persist data, risking data loss on restart

C. Redis will use too much memory due to appendonly being off

D. Redis will reject all client connections

Solution

1. Step 1: Analyze save and appendonly settings

   Setting save "" disables RDB snapshots; appendonly no disables AOF persistence.

2. Step 2: Understand impact on data persistence

   With both disabled, Redis keeps data only in memory, losing it on restart or crash.

3. Final Answer:

   Redis will not persist data, risking data loss on restart -> Option B

4. Quick Check:

   No persistence = data loss risk [OK]

Hint: Disable persistence means data lost on restart [OK]

Common Mistakes:

• Assuming Redis still saves data without persistence
• Confusing appendonly with memory usage
• Thinking Redis rejects connections due to config

5. You want to deploy Redis in production with these goals:
- Secure access
- Limit memory to 500mb
- Evict least recently used keys when full
- Persist data safely

Which configuration snippet best meets these goals?

hard

A. maxclients 1000
maxmemory 500mb
maxmemory-policy noeviction
save ""
appendonly no

B. requirepass mysecret
maxmemory 500mb
maxmemory-policy volatile-lru
save 900 1
appendonly no

C. requirepass mysecret
maxmemory 500mb
maxmemory-policy allkeys-lru
save 900 1
appendonly yes

D. requirepass mysecret
maxmemory 100mb
maxmemory-policy allkeys-lru
save 0 0
appendonly yes

Solution

1. Step 1: Check security and memory limit

   requirepass mysecret maxmemory 500mb maxmemory-policy allkeys-lru save 900 1 appendonly yes uses requirepass for security and sets maxmemory 500mb as required.

2. Step 2: Verify eviction and persistence settings

   requirepass mysecret maxmemory 500mb maxmemory-policy allkeys-lru save 900 1 appendonly yes uses allkeys-lru eviction and enables persistence with save and appendonly yes.

3. Final Answer:

   requirepass mysecret maxmemory 500mb maxmemory-policy allkeys-lru save 900 1 appendonly yes -> Option C

4. Quick Check:

   Security + memory + eviction + persistence = requirepass mysecret maxmemory 500mb maxmemory-policy allkeys-lru save 900 1 appendonly yes [OK]

Hint: Match all goals: password, memory, eviction, persistence [OK]

Common Mistakes:

• Missing password protection
• Wrong eviction policy
• Disabling persistence accidentally