stock.*.nyse, which routing key will cause a message to be delivered to the queue?* matches exactly one word in the routing key.The binding key stock.*.nyse matches routing keys with exactly three words where the middle word can be anything. Option A matches this pattern. Option A has only two words, C has four words, and D has the words in the wrong order.
# wildcard represent in a RabbitMQ topic exchange binding key?# can match.The # wildcard matches zero or more words separated by dots in the routing key. It allows flexible matching of multiple words or none.
log.error.system and log.error.application to a queue named ErrorLogs. Which binding keys should you use on the topic exchange to achieve this?The binding key log.error.* matches routing keys starting with log.error. followed by exactly one word. Both log.error.system and log.error.application match this pattern.
sensor.#. Messages with routing key sensor are not delivered to the queue. What is the most likely reason?The binding key sensor.# matches routing keys starting with 'sensor' followed by zero or more words separated by dots. However, the routing key 'sensor' has only one word and no dot, so it does not match the pattern which expects 'sensor.' followed by words.
More specific binding keys with fewer wildcards reduce the number of matches the exchange must check, improving routing performance. Overusing wildcards like '#' can cause more routing overhead.