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.

Practice

1. What is the main purpose of setting different job priorities in Rails Active Job?

easy

A. To run more important tasks before less important ones

B. To make jobs run slower

C. To delete jobs automatically

D. To run all jobs at the same time

Solution

1. Step 1: Understand job priorities concept

   Job priorities help decide which jobs run first based on importance.

2. Step 2: Identify the purpose in Rails

   Rails uses priorities to run important jobs before less important ones.

3. Final Answer:

   To run more important tasks before less important ones -> Option A

4. Quick Check:

   Job priorities = run important jobs first [OK]

Hint: Priorities mean important jobs run before others [OK]

Common Mistakes:

• Thinking priorities slow down jobs
• Assuming priorities delete jobs
• Believing all jobs run simultaneously

2. Which syntax correctly sets a queue name for a job class in Rails?

easy

A. queue_as :default

B. queue = :default

C. set_queue :default

D. queue_name = 'default'

Solution

1. Step 1: Recall Rails Active Job syntax

   Rails uses queue_as to set the queue name inside job classes.

2. Step 2: Match correct syntax

   queue_as :default is the correct way to assign the queue.

3. Final Answer:

   queue_as :default -> Option A

4. Quick Check:

   Use queue_as to set queue [OK]

Hint: Use queue_as :name inside job class [OK]

Common Mistakes:

• Using assignment (=) instead of queue_as
• Trying to set queue with unknown methods
• Using string instead of symbol incorrectly

3. Given this job class:

class EmailJob < ApplicationJob
  queue_as :mailers
  def perform(user_id)
    # send email
  end
end

Which queue will this job be added to when enqueued?

medium

A. jobs

B. default

C. emails

D. mailers

Solution

1. Step 1: Check the queue_as setting in the job class

   The job class sets queue_as :mailers, so it uses the 'mailers' queue.

2. Step 2: Understand enqueue behavior

   When enqueued, the job goes to the queue named 'mailers'.

3. Final Answer:

   mailers -> Option D

4. Quick Check:

   queue_as :mailers means queue is 'mailers' [OK]

Hint: queue_as sets the queue name exactly [OK]

Common Mistakes:

• Assuming default queue if queue_as is set
• Confusing queue name with job class name
• Picking similar sounding queue names

4. Identify the error in this job class:

class CleanupJob < ApplicationJob
  queue_as = :low_priority
  def perform
    # cleanup code
  end
end

medium

A. Job class must inherit from ActiveJob::Base

B. perform method must have an argument

C. queue_as should be called as a method, not assigned

D. queue_as must be a string, not a symbol

Solution

1. Step 1: Check how queue_as is set

   queue_as is a method call, not an assignment. Using '=' causes syntax error.

2. Step 2: Correct syntax for queue_as

   It should be queue_as :low_priority without '='.

3. Final Answer:

   queue_as should be called as a method, not assigned -> Option C

4. Quick Check:

   queue_as is a method call, not variable assignment [OK]

Hint: Use queue_as :name, not queue_as = :name [OK]

Common Mistakes:

• Using '=' with queue_as
• Forgetting to inherit from ApplicationJob
• Thinking perform must have arguments always

5. You want to run urgent jobs before normal jobs in Rails. You have two job classes:

class UrgentJob < ApplicationJob
  queue_as :urgent
  def perform
    # urgent task
  end
end

class NormalJob < ApplicationJob
  queue_as :normal
  def perform
    # normal task
  end
end

How can you ensure urgent jobs run before normal jobs when using Sidekiq?

hard

A. Rename UrgentJob to NormalJob

B. Configure Sidekiq to process the 'urgent' queue before the 'normal' queue

C. Set both jobs to the same queue

D. Run urgent jobs manually without Sidekiq

Solution

1. Step 1: Understand queue priority in Sidekiq

   Sidekiq processes queues in the order they are listed in its configuration.

2. Step 2: Set Sidekiq to prioritize 'urgent' queue

   Configure Sidekiq to check the 'urgent' queue before 'normal' to run urgent jobs first.

3. Final Answer:

   Configure Sidekiq to process the 'urgent' queue before the 'normal' queue -> Option B

4. Quick Check:

   Sidekiq queue order controls job priority [OK]

Hint: Set queue order in Sidekiq config for priority [OK]

Common Mistakes:

• Assuming queue_as alone controls priority
• Renaming job classes does not affect queue order
• Running urgent jobs manually is inefficient