Job priorities and queues in Ruby on Rails - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the queue name for a job.

Ruby on Rails

class MyJob < ApplicationJob
  queue_as :[1]

  def perform(*args)
    # job code here
  end
end

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

Adefault

Burgent

Clow_priority

Dmailers

Attempts:

3 left

💡 Hint

Common Mistakes

Using a queue name that is not defined in the system.

Forgetting to set the queue name when needed.

The queue_as method sets the queue name for the job. Here, default is the standard queue name.

2fill in blank

medium

Complete the code to enqueue a job with high priority queue.

Ruby on Rails

MyJob.set(queue: :[1]).perform_later(user_id)

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

Adefault

Burgent

Clow_priority

Dmailers

Attempts:

3 left

💡 Hint

Common Mistakes

Using the default queue when a specific priority is needed.

Misspelling the queue name.

Using set(queue: :urgent) enqueues the job to the 'urgent' queue, which is for high priority jobs.

3fill in blank

hard

Fix the error in the job class to correctly set the queue name.

Ruby on Rails

class ReportJob < ApplicationJob
  queue_as [1]

  def perform(report_id)
    # generate report
  end
end

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

A"reports"

B'reports'

Creports

D:reports

Attempts:

3 left

💡 Hint

Common Mistakes

Using strings instead of symbols for queue names.

Omitting the colon before the queue name.

The queue_as method expects a symbol for the queue name, so :reports is correct.

4fill in blank

hard

Fill both blanks to create a job that retries 5 times and uses the 'critical' queue.

Ruby on Rails

class CriticalJob < ApplicationJob
  queue_as [1]
  retry_on [2], attempts: 5

  def perform(task_id)
    # critical task
  end
end

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

A:critical

BStandardError

CRuntimeError

D:default

Attempts:

3 left

💡 Hint

Common Mistakes

Using string queue names instead of symbols.

Using incorrect error classes for retry.

The job uses the :critical queue and retries on StandardError up to 5 times.

5fill in blank

hard

Fill all three blanks to define a job that uses the 'mailers' queue, discards after 3 attempts, and performs with a user email.

Ruby on Rails

class UserMailerJob < ApplicationJob
  queue_as [1]
  discard_on [2], attempts: 3

  def perform([3])
    # send email
  end
end

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

A:mailers

BStandardError

Cemail

D:default

Attempts:

3 left

💡 Hint

Common Mistakes

Using strings instead of symbols for queue names.

Using wrong error classes for discard.

Incorrect parameter names in perform method.

The job uses the :mailers queue, discards on StandardError after 3 attempts, and takes email as a parameter.

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