Event subscribers in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when an event subscriber handles multiple events?

Consider a Laravel event subscriber class that listens to two different events. What will happen when one of those events is fired?

Laravel

class UserEventSubscriber {
    public function onUserLogin($event) {
        logger('User logged in: ' . $event->user->name);
    }

    public function onUserLogout($event) {
        logger('User logged out: ' . $event->user->name);
    }

    public function subscribe($events) {
        $events->listen(LoginEvent::class, [self::class, 'onUserLogin']);
        $events->listen(LogoutEvent::class, [self::class, 'onUserLogout']);
    }
}

// When LoginEvent is fired, what happens?

A Both onUserLogin and onUserLogout methods are called regardless of event type.

B No methods are called unless the subscriber is manually invoked.

C Only the onUserLogin method is called, logging the login message.

D Only the onUserLogout method is called, ignoring the LoginEvent.

💡 Hint

Think about how Laravel matches events to subscriber methods.

Laravel calls only the subscriber method registered for the specific event fired. So when LoginEvent is fired, only onUserLogin runs.

📝 Syntax

intermediate

Which code correctly registers an event subscriber in Laravel?

Choose the correct way to register an event subscriber class in Laravel's EventServiceProvider.

Laravel

class EventServiceProvider extends ServiceProvider {
    protected $subscribe = [
        // Which line is correct here?
    ];
}

A 'UserEventSubscriber',

B UserEventSubscriber::class,

C new UserEventSubscriber(),

D UserEventSubscriber

💡 Hint

Look for the syntax that references the class name as a string with ::class.

Laravel expects the subscriber class name with ::class in the $subscribe array for automatic registration.

🔧 Debug

advanced

Why does this subscriber method not get called?

Given this subscriber method, why might it never be triggered when the event fires?

Laravel

class UserEventSubscriber {
    public function onUserRegistered($event) {
        logger('User registered: ' . $event->user->email);
    }

    public function subscribe($events) {
        $events->listen('UserRegistered', [self::class, 'onUserRegistered']);
    }
}

// Event fired as: event(new UserRegistered($user));

A The event is fired incorrectly using event() instead of dispatch().

B The method onUserRegistered is private and cannot be called.

C The subscriber class is not registered in EventServiceProvider.

D The event name string 'UserRegistered' does not match the event class name with namespace.

💡 Hint

Check how Laravel matches event names to classes.

Laravel expects the full class name including namespace for event listeners. Using just 'UserRegistered' string causes no match.

❓ state_output

advanced

What is the output after firing multiple events handled by one subscriber?

Given this subscriber and these events fired in order, what will be logged?

Laravel

class OrderEventSubscriber {
    public function onOrderPlaced($event) {
        logger('Order placed: ' . $event->order->id);
    }

    public function onOrderShipped($event) {
        logger('Order shipped: ' . $event->order->id);
    }

    public function subscribe($events) {
        $events->listen(OrderPlaced::class, [self::class, 'onOrderPlaced']);
        $events->listen(OrderShipped::class, [self::class, 'onOrderShipped']);
    }
}

// Events fired:
event(new OrderPlaced($order));
event(new OrderShipped($order));

A Logs 'Order placed: {id}' then 'Order shipped: {id}' in that order.

B Logs only 'Order placed: {id}' and ignores the shipped event.

C Logs only 'Order shipped: {id}' and ignores the placed event.

D No logs appear because subscriber methods are not called automatically.

💡 Hint

Think about how Laravel calls subscriber methods for each event fired.

Each event triggers its corresponding subscriber method, so both logs appear in order.

🧠 Conceptual

expert

Why use event subscribers instead of individual listeners in Laravel?

Which reason best explains why you might choose an event subscriber class over separate listener classes?

A To group related event handling methods in one class for better organization and reuse.

B Because subscribers automatically queue events without extra setup.

C Subscribers run before middleware, unlike listeners which run after.

D Subscribers can listen to events from other applications automatically.

💡 Hint

Think about code organization and grouping related logic.

Subscribers let you group multiple event handlers in one class, making code cleaner and easier to maintain.