Dispatching jobs in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a job is dispatched synchronously?

Consider a Laravel job dispatched using dispatchSync(). What is the behavior of the application during this dispatch?

Laravel

MyJob::dispatchSync($data);

A The job is queued and runs later asynchronously.

B The job is dispatched to a remote server automatically.

C The job is ignored if the queue worker is not running.

D The job runs immediately in the current process before moving on.

💡 Hint

Think about what dispatchSync() means compared to dispatch().

dispatchSync() runs the job immediately in the current process, blocking until it finishes. It does not queue the job.

❓ state_output

intermediate

What is the queue name used when dispatching a job with ->onQueue('emails')?

Given the code below, what queue will the job be sent to?

MyJob::dispatch($data)->onQueue('emails');

Laravel

MyJob::dispatch($data)->onQueue('emails');

A The job will be sent to a queue named 'default_emails'.

B The job will be sent to the default queue regardless of 'emails'.

C The job will be sent to the 'emails' queue.

D The job will fail to dispatch due to invalid queue name.

💡 Hint

Check how onQueue() affects the job dispatch.

The onQueue('emails') method sets the queue name to 'emails' for the dispatched job.

📝 Syntax

advanced

Which code snippet correctly dispatches a job with a delay of 10 minutes?

Select the correct Laravel code to dispatch MyJob with a 10-minute delay.

A MyJob::dispatch()->delay(now()->addMinutes(10));

B MyJob::dispatch()->delay(10);

C dispatch((new MyJob())->delay(now()->addMinutes(10)));

D MyJob::dispatch()->delay('10 minutes');

💡 Hint

Remember the delay method expects a DateTime or Carbon instance.

The delay() method requires a DateTime or Carbon instance. now()->addMinutes(10) correctly creates a 10-minute delay.

🔧 Debug

advanced

Why does this dispatched job never run?

Given the code below, the job never executes. What is the most likely cause?

MyJob::dispatch($data);

The queue worker is running and configured properly.

Laravel

MyJob::dispatch($data);

A The job is dispatched synchronously and finishes instantly.

B The queue connection is set to 'sync' in the config.

C The job class does not implement the ShouldQueue interface.

D The job is missing the handle() method.

💡 Hint

Check the queue connection configuration.

If the queue connection is set to 'sync', jobs run immediately and do not go to the queue, so the queue worker never processes them.

🧠 Conceptual

expert

What is the effect of chaining ->onConnection('redis')->onQueue('emails') when dispatching a job?

Consider the code below:

MyJob::dispatch($data)->onConnection('redis')->onQueue('emails');

What does this chaining do?

A It dispatches the job to the 'emails' queue on the 'redis' connection.

B It dispatches the job to the default queue on the default connection ignoring parameters.

C It causes a runtime error because chaining these methods is invalid.

D It dispatches the job synchronously bypassing the queue.

💡 Hint

Think about what onConnection() and onQueue() specify.

Chaining onConnection('redis') and onQueue('emails') sends the job to the 'emails' queue on the 'redis' queue connection.