RabbitMQ management UI - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to enable the RabbitMQ management plugin.

RabbitMQ

rabbitmq-plugins [1] rabbitmq_management

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

Astatus

Benable

Clist

Ddisable

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'disable' instead of 'enable' disables the plugin.

Using 'list' only shows available plugins.

Using 'status' shows the plugin status but does not enable it.

The enable command activates the RabbitMQ management plugin, allowing access to the management UI.

2fill in blank

medium

Complete the URL to access the RabbitMQ management UI on the local machine.

RabbitMQ

http://localhost:[1]/

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

A8080

B4369

C5672

D15672

Attempts:

3 left

💡 Hint

Common Mistakes

Using 5672 which is the AMQP protocol port, not the management UI port.

Using 8080 which is a common web port but not for RabbitMQ UI.

Using 4369 which is used by Erlang distribution.

The RabbitMQ management UI listens on port 15672 by default.

3fill in blank

hard

Complete the command to add a new user 'guest' with password 'guest' for RabbitMQ management.

RabbitMQ

rabbitmqctl [1] guest guest

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

Aadd_user

Badd

Cset_user

Duser_add

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'add' which is incorrect syntax.

Using 'set_user' which is not a valid command for adding users.

Using 'user_add' which does not exist.

The correct command is rabbitmqctl add_user guest guest to add a user with username and password.

4fill in blank

hard

Fill both blanks to set permissions for user 'guest' on the virtual host '/'.

RabbitMQ

rabbitmqctl set_permissions -p [1] [2] ".*" ".*" ".*"

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

A/

Bguest

Cadmin

Ddefault

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'admin' or 'default' as user names instead of 'guest'.

Using incorrect virtual host names.

The virtual host is / and the user is guest to set permissions correctly.

5fill in blank

hard

Fill all three blanks to enable the management plugin, start the RabbitMQ server, and open the management UI URL.

RabbitMQ

rabbitmq-plugins [1] rabbitmq_management && systemctl [2] rabbitmq-server && xdg-open http://localhost:[3]/

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

Aenable

Bstart

C15672

Drestart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'disable' instead of 'enable' for the plugin.

Using 'restart' instead of 'start' when the server is not running.

Using wrong port numbers for the UI.

First, enable the plugin, then start the server, and finally open the UI on port 15672.

Practice

1. What is the default URL to access the RabbitMQ management UI after enabling the plugin?

easy

A. http://localhost:5672

B. http://localhost:8080

C. http://localhost:15672

D. http://localhost:15670

Solution

1. Step 1: Understand the default port for RabbitMQ management UI

   The RabbitMQ management UI runs on port 15672 by default.

2. Step 2: Identify the correct URL format

   The URL uses localhost and port 15672, so the full URL is http://localhost:15672.

3. Final Answer:

   http://localhost:15672 -> Option C

4. Quick Check:

   Default management UI URL = http://localhost:15672 [OK]

Hint: Remember management UI runs on port 15672 by default [OK]

Common Mistakes:

• Confusing AMQP port 5672 with management UI port
• Using wrong port like 8080 or 15670
• Forgetting to include http:// in URL

2. Which command correctly enables the RabbitMQ management plugin?

easy

A. rabbitmq-plugins enable rabbitmq_management

B. rabbitmqctl enable_management

C. rabbitmq-plugins start management

D. rabbitmqctl enable rabbitmq_management

Solution

1. Step 1: Recall the correct command structure for enabling plugins

   The command to enable plugins uses 'rabbitmq-plugins enable' followed by the plugin name.

2. Step 2: Match the exact plugin name for management UI

   The plugin name is 'rabbitmq_management', so the full command is 'rabbitmq-plugins enable rabbitmq_management'.

3. Final Answer:

   rabbitmq-plugins enable rabbitmq_management -> Option A

4. Quick Check:

   Enable plugin command = rabbitmq-plugins enable rabbitmq_management [OK]

Hint: Use 'rabbitmq-plugins enable' plus plugin name [OK]

Common Mistakes:

• Using rabbitmqctl instead of rabbitmq-plugins
• Wrong plugin name like 'management' only
• Using 'start' instead of 'enable'

3. After enabling the management plugin and starting RabbitMQ, what will happen if you visit http://localhost:15672 and login with username guest and password guest?

medium

A. You will see an empty page with no content.

B. You will get a 404 Not Found error.

C. You will be prompted to change the guest password immediately.

D. You will see the RabbitMQ management dashboard with queues and exchanges.

Solution

1. Step 1: Understand default access after enabling management plugin

   Once enabled, the management UI is accessible at port 15672 and shows the dashboard after login.

2. Step 2: Recognize default credentials and UI behavior

   The default guest/guest credentials allow login and show the dashboard with queues and exchanges.

3. Final Answer:

   You will see the RabbitMQ management dashboard with queues and exchanges. -> Option D

4. Quick Check:

   Default login shows dashboard = You will see the RabbitMQ management dashboard with queues and exchanges. [OK]

Hint: Default guest login shows dashboard at port 15672 [OK]

Common Mistakes:

• Expecting 404 error after enabling plugin
• Thinking guest user must change password immediately
• Assuming page is empty after login

4. You enabled the management plugin but cannot access http://localhost:15672. Which of these is the most likely cause?

medium

A. The management plugin disables the web UI by default.

B. RabbitMQ server is not running.

C. You used the wrong URL port 5672 instead of 15672.

D. You forgot to install RabbitMQ.

Solution

1. Step 1: Check if RabbitMQ server is running

   If the server is not running, the management UI won't be accessible at any URL.

2. Step 2: Evaluate other options

   RabbitMQ must be installed to enable the plugin, so B is unlikely if plugin enabled. Port 5672 is for AMQP, not UI. The plugin enables, not disables, the UI.

3. Final Answer:

   RabbitMQ server is not running. -> Option B

4. Quick Check:

   Server running = UI accessible [OK]

Hint: Check server status first if UI is unreachable [OK]

Common Mistakes:

• Confusing AMQP port 5672 with management UI port
• Assuming plugin disables UI by default
• Not verifying RabbitMQ server is running

5. You want to allow remote access to the RabbitMQ management UI on a server. Which step is necessary besides enabling the plugin?

hard

A. Configure the server firewall to allow incoming connections on port 15672.

B. Change the management UI port to 5672 in the config file.

C. Disable the guest user to allow remote login.

D. Restart RabbitMQ with the --remote-ui flag.

Solution

1. Step 1: Understand network access requirements

   To access the UI remotely, the server firewall must allow traffic on port 15672.

2. Step 2: Evaluate other options

   Port 5672 is for AMQP, not UI. Disabling guest user alone doesn't enable remote access. There is no --remote-ui flag for RabbitMQ restart.

3. Final Answer:

   Configure the server firewall to allow incoming connections on port 15672. -> Option A

4. Quick Check:

   Open port 15672 in firewall for remote UI access [OK]

Hint: Open port 15672 in firewall for remote UI access [OK]

Common Mistakes:

• Confusing AMQP port 5672 with management UI port
• Thinking guest user must be disabled for remote access
• Believing a special restart flag is needed