Event Dispatcher & Subscribers Session

Question 1 of 12

What is the primary role of the Event Dispatcher component in Symfony?

To manage database connections. To implement the Model-View-Controller (MVC) architecture. To provide a mechanism for components to communicate with each other in a decoupled manner. To handle HTTP requests and responses.

Question 2 of 12

Which interface must a class implement to be considered an Event Subscriber in Symfony?

Symfony\Component\EventDispatcher\EventInterface

Symfony\Component\EventDispatcher\EventSubscriberInterface

Symfony\Contracts\EventDispatcher\EventDispatcherInterface

Symfony\Component\EventDispatcher\EventDispatcherInterface

Question 3 of 12

What method must be implemented in an Event Subscriber class to define which events it listens to?

getSubscribedEvents()

handleEvent()

subscribe()

getEvents()

Question 4 of 12

How do you dispatch an event in Symfony using the Event Dispatcher?

$eventDispatcher->trigger('event.name', $event);

$eventDispatcher->notify('event.name', $event);

$eventDispatcher->dispatch($event, 'event.name');

$eventDispatcher->fire('event.name', $event);

Question 5 of 12

What is the purpose of defining priorities for event listeners/subscribers?

To specify which events should be handled first. To optimize event dispatching performance. To determine the order in which listeners are executed. To define the level of importance of an event.

Question 6 of 12

If multiple listeners are subscribed to the same event, which listener is executed first by default?

The listener that was registered last. The listener with the lowest priority number. The order is random and unpredictable. The listener with the highest priority number.

Question 7 of 12

How can you stop the propagation of an event to subsequent listeners?

By calling

$event->stopPropagation()

in the listener. By returning

false

from the listener. By throwing an exception in the listener. By unregistering the remaining listeners.

Question 8 of 12

What is the difference between an Event Listener and an Event Subscriber in Symfony?

Event Subscribers can listen to multiple events, while Event Listeners typically listen to only one. Event Listeners are classes, while Event Subscribers are functions. Event Listeners use annotations, while Event Subscribers use YAML configuration. Event Listeners are automatically registered, while Event Subscribers need manual registration.

Question 9 of 12

How can you access the Event Dispatcher service within a Symfony controller?

By injecting it as a dependency using constructor injection or autowiring. By calling

$this->get('event_dispatcher')

. By using the

EventDispatcher::getInstance()

static method. It's not possible to access the Event Dispatcher directly from a controller.

Question 10 of 12

What is the purpose of the

Event

class in Symfony's Event Dispatcher?

It's a marker interface for all event classes. It defines the structure for passing data related to the event to listeners. It's a base class for all event dispatcher implementations. It's used to register event listeners.

Symfony | Event Dispatcher & Subscribers