📖 Scenario: You are managing a Redis server for a small online store. To ensure data safety, you want to configure Redis to save snapshots of the database at specific intervals.
🎯 Goal: Set up Redis RDB save intervals so that the database saves snapshots after a certain number of seconds and changes.
📋 What You'll Learn
Create a Redis configuration dictionary named redis_config with default settings.
Add a save interval configuration variable named save_intervals.
Use the save_intervals to set the save key in redis_config with specific time and change thresholds.
Complete the configuration by adding a dbfilename key with the value dump.rdb.
💡 Why This Matters
🌍 Real World
Redis is widely used for caching and fast data storage. Configuring RDB save intervals helps balance performance and data durability.
💼 Career
Understanding Redis configuration is important for roles like backend developer, DevOps engineer, and database administrator.
Progress0 / 4 steps
1
Create the initial Redis configuration dictionary
Create a dictionary called redis_config with these exact entries: "appendonly": "no" and "maxmemory": "256mb".
Redis
Hint
Use curly braces to create a dictionary with the keys and values exactly as shown.
2
Add the save intervals configuration variable
Create a list called save_intervals with these exact tuples: (900, 1), (300, 10), and (60, 10000).
Redis
Hint
Create a list with tuples representing seconds and changes for save intervals.
3
Set the save intervals in the Redis configuration
Add a key "save" to the redis_config dictionary. Set its value to a list of strings formatted as "seconds changes" for each tuple in save_intervals. Use a list comprehension with variables seconds and changes to create this list.
Redis
Hint
Use a list comprehension to convert each tuple to a string with a space between the numbers.
4
Complete the Redis configuration with the database filename
Add a key "dbfilename" to the redis_config dictionary and set its value to "dump.rdb".
Redis
Hint
Simply assign the string "dump.rdb" to the key "dbfilename" in the dictionary.
Practice
(1/5)
1. What does the Redis save configuration option control?
easy
A. The port Redis listens on
B. The maximum memory Redis can use
C. When Redis automatically saves snapshots of the dataset
D. The password required to connect to Redis
Solution
Step 1: Understand the purpose of save in Redis
The save option defines intervals for automatic snapshot saving.
Step 2: Identify what save controls
It controls when Redis saves data snapshots based on time and changes.
Final Answer:
When Redis automatically saves snapshots of the dataset -> Option C
Quick Check:
RDB save intervals = automatic snapshot timing [OK]
Hint: Remember: save sets snapshot save timing [OK]
Common Mistakes:
Confusing save with memory limits
Thinking save sets connection ports
Assuming save controls authentication
2. Which of the following is the correct syntax to save Redis data every 300 seconds if at least 10 keys changed?
easy
A. save 10 300
B. save 300 10
C. save 300,10
D. save 10;300
Solution
Step 1: Recall Redis save syntax
The syntax is save <seconds> <changes> without commas or semicolons.
Step 2: Match the correct order
Time in seconds comes first, then number of changes.
Final Answer:
save 300 10 -> Option B
Quick Check:
Correct syntax = save seconds changes [OK]
Hint: Syntax is: save seconds changes (space separated) [OK]
Common Mistakes:
Swapping seconds and changes order
Using commas or semicolons instead of spaces
Omitting one of the two required values
3. Given the Redis config lines: save 900 1 save 300 10 What happens if 5 keys change within 400 seconds?
medium
A. Redis does not save a snapshot because 10 changes were not reached
B. Redis saves a snapshot after 300 seconds because 10 changes are needed
C. Redis saves a snapshot immediately after 5 changes
D. Redis saves a snapshot after 900 seconds because 1 change triggers it
Solution
Step 1: Analyze each save interval
First interval: save every 900 seconds if at least 1 change. Second interval: save every 300 seconds if at least 10 changes.
Step 2: Check conditions for 5 changes in 400 seconds
5 changes < 10, so second interval not triggered. 900 seconds not reached yet, so first interval not triggered either.
Final Answer:
Redis does not save a snapshot because 10 changes were not reached -> Option A
Quick Check:
5 changes in 400s does not meet any save condition [OK]
Hint: Check each interval separately for time and changes [OK]
Common Mistakes:
Assuming 5 changes triggers 10-change interval
Ignoring the time condition for the first interval
Thinking Redis saves immediately after changes
4. You wrote this Redis config line: save 60,5 Why does Redis ignore this setting?
medium
A. Because commas are invalid; spaces must separate values
B. Because 5 changes is too low to trigger saving
C. Because 60 is not a valid time value
D. Because save intervals must be in milliseconds
Solution
Step 1: Check syntax of save line
Redis requires space-separated values, not commas.
Step 2: Understand why commas cause ignoring
Commas make the line invalid, so Redis skips it.
Final Answer:
Because commas are invalid; spaces must separate values -> Option A
Quick Check:
Use spaces, not commas in save intervals [OK]
Hint: Use spaces, never commas, between save parameters [OK]
Common Mistakes:
Thinking commas are allowed separators
Believing time must be in milliseconds
Assuming low changes disables saving
5. You want Redis to save a snapshot if either: - 5 keys changed in 60 seconds - OR 100 keys changed in 900 seconds Which configuration lines achieve this?
hard
A. save 900 5\nsave 60 100
B. save 5 60\nsave 100 900
C. save 60 100\nsave 900 5
D. save 60 5\nsave 900 100
Solution
Step 1: Match time and changes correctly
Format is save <seconds> <changes>. So 60 seconds and 5 changes is save 60 5. 900 seconds and 100 changes is save 900 100.
Step 2: Verify both conditions are separate lines
Each condition must be on its own save line.
Final Answer:
save 60 5
save 900 100 -> Option D
Quick Check:
Time first, changes second per line [OK]
Hint: Write each interval on its own line: save seconds changes [OK]
Common Mistakes:
Swapping seconds and changes
Putting both intervals on one line
Using commas or semicolons instead of spaces
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.