Production deployment best practices in Redis - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start Redis server with a configuration file.

Redis

redis-server [1]

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

A-c

B--config

C/etc/redis/redis.conf

D--start

Attempts:

3 left

💡 Hint

Common Mistakes

Using flags like --config which Redis does not recognize.

Omitting the config file path.

The Redis server is started by specifying the path to the configuration file directly.

2fill in blank

medium

Complete the code to enable Redis persistence by setting the snapshot save interval.

Redis

save [1]

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

A900 1

B900

C900 2

D900 0

Attempts:

3 left

💡 Hint

Common Mistakes

Providing only one value instead of two.

Using zero changes which disables saving.

The 'save' directive requires two values: seconds and changes. '900 1' means save after 900 seconds if at least 1 change occurred.

3fill in blank

hard

Fix the error in the Redis configuration line to require a password for clients.

Redis

requirepass [1]

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

A''

Bnone

Cnull

Dmypassword

Attempts:

3 left

💡 Hint

Common Mistakes

Leaving the password empty disables authentication.

Using 'none' or 'null' which are invalid.

The 'requirepass' directive must be followed by a non-empty password string to enable authentication.

4fill in blank

hard

Fill both blanks to configure Redis to run as a background daemon and log to a file.

Redis

daemonize [1]
logfile [2]

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

Ayes

Bno

C/var/log/redis/redis-server.log

D/tmp/redis.log

Attempts:

3 left

💡 Hint

Common Mistakes

Setting daemonize to 'no' which runs Redis in foreground.

Using invalid or temporary log file paths.

Setting 'daemonize yes' runs Redis in the background. The 'logfile' path specifies where logs are saved.

5fill in blank

hard

Fill all three blanks to configure Redis max memory, eviction policy, and append-only file.

Redis

maxmemory [1]
maxmemory-policy [2]
appendonly [3]

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

A256mb

Ballkeys-lru

Cyes

Dno

Attempts:

3 left

💡 Hint

Common Mistakes

Not setting maxmemory causing Redis to use unlimited memory.

Choosing eviction policies that do not evict keys.

Disabling appendonly which risks data loss.

Setting maxmemory limits Redis memory usage. 'allkeys-lru' evicts least recently used keys when memory is full. 'appendonly yes' enables data durability.