Shovel and Federation for multi-DC in RabbitMQ - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a shovel that moves messages from source to destination.

RabbitMQ

rabbitmqctl set_parameter shovel my_shovel '{"src-uri": "amqp://", "src-queue": "source_queue", "dest-uri": "amqp://", "dest-queue": "[1]"}'

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

Atemp_queue

Bdestination_queue

Cbackup_queue

Dsource_queue

Attempts:

3 left

💡 Hint

Common Mistakes

Using the source queue name as the destination queue.

Misspelling the queue name.

The shovel moves messages to the destination_queue, so the destination queue name must be set correctly.

2fill in blank

medium

Complete the command to enable federation plugin in RabbitMQ.

RabbitMQ

rabbitmq-plugins [1] rabbitmq_federation

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

Astatus

Bdisable

Clist

Denable

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'disable' instead of 'enable'.

Using 'list' which only shows plugins.

To use federation, the rabbitmq_federation plugin must be enabled with enable.

3fill in blank

hard

Fix the error in the federation upstream declaration by completing the missing URI.

RabbitMQ

rabbitmqctl set_parameter federation-upstream my-upstream '{"uri": "[1]", "expires": 3600000}'

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

Aftp://remote-host

Bhttp://remote-host

Camqp://user:pass@remote-host

Damqp://localhost

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTP or FTP protocols which are invalid.

Using localhost instead of remote host.

The federation upstream URI must use the AMQP protocol with correct user credentials and remote host.

4fill in blank

hard

Fill both blanks to declare a federation upstream-set with the correct upstream and policy.

RabbitMQ

rabbitmqctl set_parameter federation-upstream-set my-upstream-set '{"upstreams": ["[1]"]}'
rabbitmqctl set_policy federate-me '^fed\.' '{"federation-upstream-set": "[2]"}' --apply-to exchanges

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

Amy-upstream

Bmy-upstream-set

Cdefault-upstream

Dfederate-me

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing upstream and upstream-set names.

Using policy name instead of upstream-set name.

The upstream-set must include the upstream name my-upstream, and the policy must reference the upstream-set my-upstream-set.

5fill in blank

hard

Fill all three blanks to create a shovel configuration with correct source URI, destination URI, and acknowledgement mode.

RabbitMQ

rabbitmqctl set_parameter shovel my-shovel '{"src-uri": "[1]", "src-queue": "queue1", "dest-uri": "[2]", "dest-queue": "queue2", "ack-mode": "[3]"}'

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

Aamqp://user:pass@source-dc

Bamqp://user:pass@dest-dc

Con-confirm

Dno-ack

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping source and destination URIs.

Using 'no-ack' which risks message loss.

The shovel needs the correct source URI amqp://user:pass@source-dc, destination URI amqp://user:pass@dest-dc, and the acknowledgement mode on-confirm for reliable delivery.