Pipeline concept and behavior in Redis - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ query_result

intermediate

What is the output of this Redis pipeline?

Consider the following Redis pipeline commands executed in sequence:

1. SET key1 10
2. INCR key1
3. GET key1
4. DEL key1
5. GET key1

What is the output returned by the pipeline?

Redis

pipeline = redis_client.pipeline()
pipeline.set('key1', '10')
pipeline.incr('key1')
pipeline.get('key1')
pipeline.delete('key1')
pipeline.get('key1')
results = pipeline.execute()

A [True, 11, b'11', 1, None]

B [True, 11, b'11', 1, b'0']

C [True, 10, b'10', 1, None]

D [True, 11, b'11', 0, None]

💡 Hint

Remember that INCR increments the string value stored at the key and returns the new value. DEL returns the number of keys removed. GET returns None if the key does not exist.

The SET command returns True on success. INCR increments '10' to 11 and returns 11. GET returns the byte string b'11'. DEL removes the key and returns 1 (number of keys deleted). The final GET returns None because the key no longer exists.

🧠 Conceptual

intermediate

Why use Redis pipelines?

Which of the following best explains the main advantage of using Redis pipelines?

A Pipelines reduce network round trips by sending multiple commands at once, improving performance.

B Pipelines automatically retry failed commands to ensure reliability.

C Pipelines encrypt data sent between client and server for security.

D Pipelines allow commands to run in parallel on multiple Redis servers.

💡 Hint

Think about how network communication affects command execution speed.

Pipelines batch multiple commands and send them together, reducing the number of network round trips and thus improving performance. They do not provide automatic retries, encryption, or parallel execution across servers.

📝 Syntax

advanced

Identify the syntax error in this Redis pipeline code

Which option contains a syntax error that will cause the pipeline execution to fail?

Redis

pipeline = redis_client.pipeline()
pipeline.set('count', 5)
pipeline.incr('count')
pipeline.get('count')
results = pipeline.execute()

A

pipeline.set('count', 5)
pipeline.incr('count')
pipeline.get('count')
results = pipeline.execute()

B

pipeline.set('count', 5)
pipeline.incr('count')
pipeline.get('count')
pipeline.execute

C

pipeline.set('count', 5)
pipeline.incr('count')
pipeline.get('count')
pipeline.execute()

D

)(etucexe.enilepip = stluser
)'tnuoc'(teg.enilepip
)'tnuoc'(rcni.enilepip
)5 ,'tnuoc'(tes.enilepip

💡 Hint

Check how the execute method is called.

Option B misses the parentheses after execute, so it references the method without calling it, causing results to be a method object instead of the command results. This will cause errors if results are used as data.

❓ optimization

advanced

Optimizing multiple Redis commands with pipelines

You want to increment 100 keys named 'counter1' to 'counter100' by 1 each. Which approach is the most efficient?

A Run 100 separate INCR commands one by one without pipeline.

B Use MULTI/EXEC transaction with 100 INCR commands.

C Use a Redis pipeline to queue 100 INCR commands and execute once.

D Use Lua scripting to increment all keys in one script.

💡 Hint

Consider network overhead and atomicity requirements.

Using a pipeline batches commands reducing network overhead and improves performance. MULTI/EXEC provides atomicity but has similar network overhead. Lua scripting can be efficient but requires scripting knowledge and may be more complex. Running commands one by one is slow due to many round trips.

🔧 Debug

expert

Why does this Redis pipeline return unexpected results?

Given this pipeline code:

pipeline.set('x', '5')
pipeline.incr('x')
pipeline.get('x')
pipeline.set('x', 'hello')
pipeline.incr('x')
results = pipeline.execute()

What will happen and why?

Redis

pipeline = redis_client.pipeline()
pipeline.set('x', '5')
pipeline.incr('x')
pipeline.get('x')
pipeline.set('x', 'hello')
pipeline.incr('x')
results = pipeline.execute()

A The pipeline returns [True, 6, b'6', True, None] because the last INCR returns no value.

B The pipeline returns [True, 6, b'6', True, 7] because INCR converts strings automatically.

C The pipeline executes successfully but the last GET returns b'hello'.

D The pipeline raises an error on the second INCR because 'hello' is not an integer.

💡 Hint

What happens if you try to increment a key holding a non-numeric string?

The first INCR increments '5' to 6 successfully. The GET returns b'6'. Then the key is set to 'hello'. The next INCR tries to increment 'hello', which is not a number, causing a Redis error. The pipeline execution raises a Redis error at that command.