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.