Headers exchange in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Understanding headers exchange binding behavior

Given a headers exchange with a queue bound using headers {"x-match": "all", "format": "pdf", "type": "report"}, what happens when a message with headers {"format": "pdf", "type": "report"} is published?

A The message is routed to the queue because all headers match.

B The message is routed only if the message has an additional header 'x-match'.

C The message is not routed because the x-match header is missing in the message.

D The message is not routed because headers exchanges ignore the 'all' match type.

💡 Hint

Remember that 'x-match' defines how headers are matched between binding and message.

Headers exchange routes messages based on matching headers. When 'x-match' is 'all', all specified headers must match exactly for routing.

🧠 Conceptual

intermediate

Headers exchange matching modes

Which statement correctly describes the difference between 'x-match' set to 'any' and 'all' in a headers exchange binding?

A 'all' ignores header values; 'any' matches header values exactly.

B 'any' requires all headers to match; 'all' requires at least one header to match.

C 'all' requires all headers to match; 'any' requires at least one header to match.

D 'any' matches only the first header; 'all' matches only the last header.

💡 Hint

Think about how strict the matching should be for routing.

'x-match' controls how headers are matched: 'all' means every header must match, 'any' means at least one header must match for routing.

❓ Configuration

advanced

Binding a queue with headers exchange using rabbitmqctl

Which rabbitmqctl command correctly binds a queue named 'reports' to a headers exchange 'docs_exchange' with headers {"x-match": "any", "format": "pdf", "type": "summary"}?

A rabbitmqctl set_binding docs_exchange reports '{"x-match":"any","format":"pdf","type":"summary"}'

B rabbitmqctl set_binding --queue=reports --exchange=docs_exchange --arguments='{"x-match":"any","format":"pdf","type":"summary"}' --type=headers

C rabbitmqctl bind_queue reports docs_exchange '{"x-match":"any","format":"pdf","type":"summary"}'

D rabbitmqctl set_binding --queue=reports --exchange=docs_exchange --arguments='{"x-match":"any","format":"pdf","type":"summary"}'

💡 Hint

Headers exchange requires specifying the exchange type and arguments correctly.

The correct command uses set_binding with --queue, --exchange, --arguments for headers, and specifies the exchange type as headers.

❓ Troubleshoot

advanced

Diagnosing message routing failure in headers exchange

A message with headers {"format": "pdf", "type": "report"} is published to a headers exchange. The queue is bound with headers {"x-match": "all", "format": "pdf", "type": "summary"}. Why is the message not routed to the queue?

A The queue is not bound to the exchange properly.

B The message lacks the 'x-match' header, so it is rejected.

C Headers exchange only routes messages with 'x-match' set to 'any'.

D The message headers do not match the binding headers exactly; 'type' differs.

💡 Hint

Check the values of each header key carefully.

With 'x-match' set to 'all', every header must match exactly. Here, 'type' is 'report' in the message but 'summary' in the binding, so no routing occurs.

🔀 Workflow

expert

Sequence to configure and test headers exchange routing

Arrange the steps in the correct order to configure a headers exchange and verify message routing for a queue bound with headers {"x-match": "any", "format": "json", "priority": "high"}.

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about the logical order: create exchange, bind queue, publish message, verify reception.

First create the exchange, then bind the queue with headers, publish a message with matching headers, and finally check if the queue received it.

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'