Management plugin and HTTP API in RabbitMQ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the RabbitMQ Management Plugin?

The RabbitMQ Management Plugin is a tool that provides a web-based user interface and HTTP API to monitor and manage RabbitMQ servers easily.

beginner

How do you enable the RabbitMQ Management Plugin?

You enable it by running the command: rabbitmq-plugins enable rabbitmq_management. This activates the plugin and starts the web UI and HTTP API.

beginner

What is the default URL to access the RabbitMQ Management web UI?

The default URL is http://localhost:15672/. You open this in a browser to see the management dashboard.

intermediate

What can you do with the RabbitMQ HTTP API?

You can use the HTTP API to programmatically check server status, list queues, exchanges, users, and perform management tasks like creating or deleting resources.

beginner

Which port does the RabbitMQ Management Plugin use by default for HTTP API and web UI?

It uses port 15672 by default for both the HTTP API and the web UI.

How do you enable the RabbitMQ Management Plugin?

A rabbitmq-plugins enable rabbitmq_management

B rabbitmqctl start_management

C service rabbitmq-management start

D rabbitmq-management enable

The correct command to enable the management plugin is rabbitmq-plugins enable rabbitmq_management.

What is the default port for accessing the RabbitMQ Management web UI?

A 5672

B 15672

C 8080

D 4369

Port 15672 is the default port for the RabbitMQ Management web UI and HTTP API.

Which of the following is NOT a feature of the RabbitMQ HTTP API?

A Running RabbitMQ server updates

B Creating and deleting users

C Listing queues and exchanges

D Checking server status

The HTTP API does not handle server software updates; it manages RabbitMQ resources and status.

After enabling the management plugin, where do you access the web UI?

A http://localhost:5672/

B http://localhost:8080/

C http://localhost:4369/

D http://localhost:15672/

The web UI is accessible at http://localhost:15672/ by default.

What command disables the RabbitMQ Management Plugin?

A service rabbitmq-management stop

B rabbitmqctl stop_management

C rabbitmq-plugins disable rabbitmq_management

D rabbitmq-management disable

To disable the plugin, use rabbitmq-plugins disable rabbitmq_management.

Explain how to enable and access the RabbitMQ Management Plugin and its web UI.

Think about the command to enable and the URL to open.

Describe the main uses of the RabbitMQ HTTP API provided by the Management Plugin.

Focus on what tasks the API helps automate.

Practice

1. What is the primary purpose of the RabbitMQ management plugin?

easy

A. To backup RabbitMQ data

B. To improve message delivery speed

C. To provide a web UI and HTTP API for managing RabbitMQ

D. To encrypt messages automatically

Solution

1. Step 1: Understand the management plugin role

   The management plugin adds a web interface and HTTP API to control RabbitMQ easily.

2. Step 2: Compare options with plugin features

   Only To provide a web UI and HTTP API for managing RabbitMQ matches the plugin's purpose; others describe unrelated features.

3. Final Answer:

   To provide a web UI and HTTP API for managing RabbitMQ -> Option C

4. Quick Check:

   Management plugin = Web UI + HTTP API [OK]

Hint: Management plugin = web UI + API for RabbitMQ control [OK]

Common Mistakes:

• Confusing management plugin with performance features
• Thinking it encrypts messages automatically
• Assuming it handles backups

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. rabbitmq-management enable

Solution

1. Step 1: Recall the correct command syntax

   The official command to enable plugins is 'rabbitmq-plugins enable <plugin_name>'.

2. Step 2: Match the plugin name

   The management plugin is named '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 = rabbitmq-plugins enable rabbitmq_management [OK]

Hint: Use 'rabbitmq-plugins enable rabbitmq_management' to enable plugin [OK]

Common Mistakes:

• Using rabbitmqctl instead of rabbitmq-plugins
• Wrong plugin name or command syntax
• Trying to start plugin instead of enabling

3. After enabling the management plugin, which port is the default for accessing the RabbitMQ web UI?

medium

A. 5672

B. 15672

C. 8080

D. 4369

Solution

1. Step 1: Identify default ports used by RabbitMQ components

   Port 5672 is for AMQP protocol, 4369 for Erlang distribution, 8080 is common for web apps but not default here.

2. Step 2: Recall management plugin default port

   The management plugin's web UI listens on port 15672 by default.

3. Final Answer:

   15672 -> Option B

4. Quick Check:

   Management UI port = 15672 [OK]

Hint: Management UI default port is 15672, not AMQP port 5672 [OK]

Common Mistakes:

• Confusing AMQP port 5672 with management UI port
• Assuming common web port 8080 is used
• Mixing Erlang port 4369 with HTTP API port

4. You try to access the RabbitMQ management HTTP API but get a 401 Unauthorized error. What is the most likely cause?

medium

A. The HTTP API port is blocked by firewall

B. The management plugin is not enabled

C. RabbitMQ server is not running

D. Incorrect username or password for basic authentication

Solution

1. Step 1: Understand 401 Unauthorized meaning

   A 401 error means authentication failed, usually due to wrong credentials.

2. Step 2: Check other options

   If the plugin was not enabled, the API wouldn't respond or connection would fail, not 401. Server down causes no response. Firewall blocks cause timeout, not 401.

3. Final Answer:

   Incorrect username or password for basic authentication -> Option D

4. Quick Check:

   401 Unauthorized = Bad credentials [OK]

Hint: 401 error means wrong username/password, not plugin or server down [OK]

Common Mistakes:

• Assuming plugin is disabled when getting 401
• Confusing 401 with connection refused or timeout
• Ignoring authentication in HTTP API

5. You want to list all queues using the RabbitMQ HTTP API. Which HTTP method and endpoint should you use with basic authentication?

hard

A. GET /api/queues

B. POST /api/queues

C. GET /api/list_queues

D. PUT /api/queues

Solution

1. Step 1: Identify HTTP method for retrieving data

   GET is used to fetch or list resources; POST and PUT modify data.

2. Step 2: Recall correct API endpoint

   The RabbitMQ management HTTP API uses '/api/queues' to list all queues.

3. Final Answer:

   GET /api/queues -> Option A

4. Quick Check:

   List queues = GET /api/queues [OK]

Hint: Use GET method on /api/queues to list queues [OK]

Common Mistakes:

• Using POST or PUT instead of GET for listing
• Wrong endpoint like /api/list_queues
• Forgetting basic authentication