Headers exchange in RabbitMQ - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a headers exchange named 'logs_headers'.

RabbitMQ

channel.exchange_declare(exchange='logs_headers', exchange_type='[1]')

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

Aheaders

Btopic

Cdirect

Dfanout

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'direct' or 'topic' instead of 'headers' exchange type.

The exchange type for headers exchange is headers.

2fill in blank

medium

Complete the code to bind a queue named 'error_logs' to the headers exchange with header 'x-match' set to 'all'.

RabbitMQ

channel.queue_bind(queue='error_logs', exchange='logs_headers', arguments=[1])

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

A{'x-match': 'all', 'severity': 'error'}

B{'x-match': 'any', 'severity': 'error'}

C{'x-match': 'all', 'type': 'info'}

D{'x-match': 'any', 'type': 'error'}

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'any' instead of 'all' for strict matching.

Binding with 'x-match': 'all' means all headers must match. Here, we want severity 'error'.

3fill in blank

hard

Fix the error in the code to publish a message with headers 'severity' set to 'error' and 'format' set to 'pdf'.

RabbitMQ

channel.basic_publish(exchange='logs_headers', routing_key='', body='Error report', properties=pika.BasicProperties(headers=[1]))

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

A('severity', 'error', 'format', 'pdf')

B['severity', 'error', 'format', 'pdf']

C'severity=error, format=pdf'

D{'severity': 'error', 'format': 'pdf'}

Attempts:

3 left

💡 Hint

Common Mistakes

Using list or string instead of dictionary for headers.

Headers must be a dictionary. Option D correctly uses a dict with keys and values.

4fill in blank

hard

Fill both blanks to declare a headers exchange and bind a queue with 'x-match' set to 'any'.

RabbitMQ

channel.exchange_declare(exchange='logs_headers', exchange_type='[1]')
channel.queue_bind(queue='info_logs', exchange='logs_headers', arguments=[2])

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

Aheaders

B{'x-match': 'all', 'type': 'info'}

C{'x-match': 'any', 'type': 'info'}

Ddirect

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'direct' exchange type or wrong 'x-match' value.

The exchange type must be 'headers'. The binding uses 'x-match' set to 'any' to match any header.

5fill in blank

hard

Fill all three blanks to publish a message with headers and bind a queue with matching headers.

RabbitMQ

channel.basic_publish(exchange='logs_headers', routing_key='', body='Info report', properties=pika.BasicProperties(headers=[1]))
channel.queue_bind(queue='info_logs', exchange='logs_headers', arguments=[2])
channel.exchange_declare(exchange='logs_headers', exchange_type='[3]')

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

A{'severity': 'info', 'format': 'json'}

B{'x-match': 'any', 'severity': 'info'}

Cheaders

D{'x-match': 'all', 'severity': 'error'}

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatch between publish headers and binding headers.

Wrong exchange type.

Publish headers must match binding headers. Exchange type is 'headers'.

Practice

1. What is the main purpose of a headers exchange in RabbitMQ?

easy

A. Route messages based on message headers instead of routing keys

B. Route messages only by exact routing key matches

C. Store messages temporarily before delivery

D. Encrypt messages for secure transmission

Solution

1. Step 1: Understand the role of headers exchange

   A headers exchange routes messages by inspecting the headers attached to the message, not by routing keys.

2. Step 2: Compare with other exchange types

   Unlike direct or topic exchanges that use routing keys, headers exchange uses message headers for routing decisions.

3. Final Answer:

   Route messages based on message headers instead of routing keys -> Option A

4. Quick Check:

   Headers exchange = header-based routing [OK]

Hint: Headers exchange routes by headers, not keys [OK]

Common Mistakes:

• Confusing headers exchange with direct exchange
• Thinking routing keys are used for headers exchange
• Assuming headers exchange stores messages
• Believing headers exchange encrypts messages

2. Which of the following is the correct way to declare a headers exchange named my_headers using RabbitMQ's AMQP protocol?

easy

A. channel.bind_exchange(exchange='my_headers', type='headers')

B. channel.exchange_declare(exchange='my_headers', exchange_type='headers')

C. channel.queue_declare(queue='my_headers', durable=True)

D. channel.exchange_declare(exchange='my_headers', exchange_type='direct')

Solution

1. Step 1: Identify the correct method to declare an exchange

   In RabbitMQ's AMQP, exchange_declare is used to create exchanges.

2. Step 2: Check the exchange type for headers exchange

   The exchange type must be set to headers to create a headers exchange.

3. Final Answer:

   channel.exchange_declare(exchange='my_headers', exchange_type='headers') -> Option B

4. Quick Check:

   Declare headers exchange with exchange_type='headers' [OK]

Hint: Use exchange_type='headers' to declare headers exchange [OK]

Common Mistakes:

• Using queue_declare instead of exchange_declare
• Setting exchange_type to 'direct' or other types
• Trying to bind exchange instead of declaring it
• Misspelling exchange_type parameter

3. Given a headers exchange with a queue bound using headers {'x-match': 'all', 'format': 'pdf', 'type': 'report'}, which message headers will be routed to this queue?

medium

A. {'format': 'doc', 'type': 'report'}

B. {'format': 'pdf', 'type': 'invoice'}

C. {'format': 'pdf', 'priority': 'high'}

D. {'format': 'pdf', 'type': 'report'}

Solution

1. Step 1: Understand the meaning of 'x-match': 'all'

   With x-match set to all, all specified headers must exactly match the message headers.

2. Step 2: Compare each option's headers with the binding headers

   {'format': 'pdf', 'type': 'report'} matches both 'format': 'pdf' and 'type': 'report' exactly. {'format': 'pdf', 'type': 'invoice'} mismatches 'type'. {'format': 'pdf', 'priority': 'high'} misses the required 'type': 'report'. {'format': 'doc', 'type': 'report'} mismatches 'format'.

3. Final Answer:

   {'format': 'pdf', 'type': 'report'} -> Option D

4. Quick Check:

   x-match='all' means all headers must match exactly [OK]

Hint: x-match='all' requires all headers to match exactly [OK]

Common Mistakes:

• Assuming extra headers prevent matching
• Confusing 'all' with 'any' in x-match
• Ignoring missing required headers
• Mixing up header keys and values

4. You have a headers exchange with a queue bound using {'x-match': 'any', 'format': 'pdf', 'type': 'report'}. A message with headers {'format': 'doc', 'type': 'invoice'} is sent. Why does the message not reach the queue?

medium

A. Because the message headers are missing the 'x-match' key

B. Because x-match must be 'all' to match any header

C. Because none of the headers match the binding criteria

D. Because headers exchange only matches routing keys

Solution

1. Step 1: Understand x-match='any' behavior

   With x-match set to any, the message must match at least one of the specified headers.

2. Step 2: Check message headers against binding headers

   The message headers are 'format': 'doc' and 'type': 'invoice'. Neither matches 'format': 'pdf' nor 'type': 'report'. So no header matches.

3. Final Answer:

   Because none of the headers match the binding criteria -> Option C

4. Quick Check:

   x-match='any' requires at least one header match [OK]

Hint: At least one header must match with x-match='any' [OK]

Common Mistakes:

• Thinking x-match='all' is required for any match
• Assuming message needs x-match header
• Confusing headers exchange with routing key matching
• Ignoring header value differences

5. You want to route messages to two different queues from a headers exchange: one queue should receive messages where format is pdf and type is report (both must match), and the other queue should receive messages where either priority is high or department is sales. How should you bind these queues to the headers exchange?

hard

A. Bind queue1 with {'x-match':'all', 'format':'pdf', 'type':'report'} and queue2 with {'x-match':'any', 'priority':'high', 'department':'sales'}

B. Bind queue1 with {'x-match':'any', 'format':'pdf', 'type':'report'} and queue2 with {'x-match':'all', 'priority':'high', 'department':'sales'}

C. Bind both queues with {'x-match':'all', 'format':'pdf', 'type':'report', 'priority':'high', 'department':'sales'}

D. Bind queue1 with {'format':'pdf', 'type':'report'} and queue2 with {'priority':'high', 'department':'sales'} without x-match

Solution

1. Step 1: Determine binding for queue1 requiring both headers

   Since both 'format' and 'type' must match, use x-match: all with those headers.

2. Step 2: Determine binding for queue2 requiring either header

   Since either 'priority' or 'department' must match, use x-match: any with those headers.

3. Step 3: Verify options

   Bind queue1 with {'x-match':'all', 'format':'pdf', 'type':'report'} and queue2 with {'x-match':'any', 'priority':'high', 'department':'sales'} correctly sets x-match for each queue's binding. Bind queue1 with {'x-match':'any', 'format':'pdf', 'type':'report'} and queue2 with {'x-match':'all', 'priority':'high', 'department':'sales'} reverses 'all' and 'any'. Bind both queues with {'x-match':'all', 'format':'pdf', 'type':'report', 'priority':'high', 'department':'sales'} combines all headers with 'all' which is incorrect. Bind queue1 with {'format':'pdf', 'type':'report'} and queue2 with {'priority':'high', 'department':'sales'} without x-match omits x-match which defaults to 'all' but is ambiguous.

4. Final Answer:

   Bind queue1 with {'x-match':'all', 'format':'pdf', 'type':'report'} and queue2 with {'x-match':'any', 'priority':'high', 'department':'sales'} -> Option A

5. Quick Check:

   Use x-match='all' for all headers, 'any' for any header [OK]

Hint: Use x-match='all' for all headers, 'any' for any header [OK]

Common Mistakes:

• Mixing up 'all' and 'any' in bindings
• Not specifying x-match leading to wrong defaults
• Combining unrelated headers in one binding
• Assuming missing x-match means 'any'