Job priorities and queues in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does Active Job handle multiple queues with priorities?

Consider a Rails app using Active Job with two queues: high_priority and low_priority. The worker processes jobs from high_priority first, then low_priority.

What happens if there are many jobs in low_priority but none in high_priority?

A The worker processes all jobs from <code>low_priority</code> queue since <code>high_priority</code> is empty.

B The worker waits indefinitely for jobs in <code>high_priority</code> and ignores <code>low_priority</code> jobs.

C The worker processes jobs from both queues simultaneously without priority.

D The worker processes only <code>high_priority</code> jobs and discards <code>low_priority</code> jobs.

💡 Hint

Think about how priority queues work when the higher priority queue is empty.

When the high priority queue is empty, the worker will process jobs from the low priority queue. Priority means it checks the high priority queue first, but if empty, it moves on.

📝 Syntax

intermediate

Identify the correct way to assign a queue with priority in a Rails job

Which code snippet correctly assigns a job to a high priority queue named critical in Rails Active Job?

A

class MyJob < ApplicationJob
  set_queue :critical
end

B

class MyJob < ApplicationJob
  queue_name :critical
end

C

class MyJob < ApplicationJob
  queue_as :critical
end

D

class MyJob < ApplicationJob
  queue = :critical
end

💡 Hint

Look for the official method to set queue name in Active Job.

The queue_as method is the correct way to assign a queue name in Active Job.

🔧 Debug

advanced

Why does a low priority job run before a high priority job?

Given two jobs enqueued: one in low_priority queue and one in high_priority queue, the low priority job runs first. What is the most likely cause?

A The job in <code>high_priority</code> queue has a scheduling delay set.

B The <code>high_priority</code> queue is paused or blocked, so jobs wait.

C The worker is configured to process <code>low_priority</code> queue before <code>high_priority</code> queue.

D Active Job does not support queue priorities, so order is random.

💡 Hint

Consider job scheduling options that delay execution.

If a job in the high priority queue has a delay (e.g., set(wait: 5.minutes)), it won't run immediately, allowing low priority jobs without delay to run first.

❓ state_output

advanced

What is the order of job execution with multiple queues and priorities?

Assume a worker is configured to process queues in this order: critical, default, low. Jobs are enqueued as follows:

• Job A in default
• Job B in low
• Job C in critical
• Job D in default

What is the order in which the jobs will be executed?

A A, D, C, B

B C, A, D, B

C B, A, D, C

D C, B, A, D

💡 Hint

Remember the worker processes queues in the configured priority order.

The worker processes all jobs in the critical queue first (Job C), then default (Jobs A and D), then low (Job B).

🧠 Conceptual

expert

Why use multiple queues with priorities in a Rails app?

What is the main benefit of configuring multiple queues with different priorities in a Rails application using Active Job?

A To allow jobs to run in parallel on a single queue without any order.

B To automatically retry failed jobs more times based on queue name.

C To reduce the total number of jobs enqueued by merging them into fewer queues.

D To ensure critical jobs run before less important jobs, improving app responsiveness for urgent tasks.

💡 Hint

Think about how prioritizing jobs affects user experience and system performance.

Using multiple queues with priorities lets the system run important jobs first, so urgent tasks finish faster and improve responsiveness.