When signals are appropriate vs not in Django - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

When should Django signals be used?

Which scenario is the best use case for Django signals?

A Writing raw SQL queries to update related tables.

B Directly querying the database for user data in a view.

C Automatically updating a user's profile when the user model is saved.

D Manually calling a function after saving a model in the same view.

💡 Hint

Think about when you want to react to changes without changing the original code flow.

Django signals are best for decoupling actions that should happen automatically after certain events, like saving a model.

❓ component_behavior

intermediate

What happens if a signal handler raises an exception?

Consider a Django signal handler connected to the post_save signal. What happens if the handler raises an exception?

A The exception stops the save operation and propagates up, possibly causing a server error.

B The exception is silently ignored and the save operation completes normally.

C The signal handler retries automatically until it succeeds.

D The signal handler logs the error and continues without affecting the save.

💡 Hint

Think about how exceptions affect the flow of code execution.

If a signal handler raises an exception, it interrupts the save operation unless caught, causing errors.

📝 Syntax

advanced

Identify the correct way to connect a Django signal

Which code snippet correctly connects a post_save signal to a handler function?

Django

from django.db.models.signals import post_save
from django.dispatch import receiver
from myapp.models import MyModel

# Handler function here

A

@receiver(post_save, sender=MyModel)
def my_handler(sender, instance, **kwargs):
    print('Saved!')

B

post_save.connect(my_handler)
def my_handler(sender, instance, **kwargs):
    print('Saved!')

C

@receiver(post_save)
def my_handler(sender, instance, **kwargs):
    print('Saved!')

D

post_save.connect(my_handler, sender=MyModel)
def my_handler(sender, instance):
    print('Saved!')

💡 Hint

Remember the decorator syntax and required parameters for signal handlers.

The @receiver decorator with sender specified is the cleanest and correct way to connect signals.

🔧 Debug

advanced

Why is a Django signal handler not called?

Given this code, why might the my_handler function not be called after saving MyModel?

Django

from django.db.models.signals import post_save
from django.dispatch import receiver
from myapp.models import MyModel

@receiver(post_save, sender=MyModel)
def my_handler(sender, instance, **kwargs):
    print('Saved!')

# In another file
obj = MyModel()
obj.save()

A The signal handler function has the wrong parameters and raises an error silently.

B The signal handler file is not imported anywhere, so the connection never happens.

C The model instance is not saved properly because save() is missing parentheses.

D The post_save signal does not work with MyModel instances.

💡 Hint

Think about how Django loads signal handlers and when connections are made.

If the file defining the signal handler is not imported, Django never registers the handler, so it won't be called.

🧠 Conceptual

expert

When are Django signals NOT appropriate?

Which situation is NOT a good use case for Django signals?

A Updating a cache when a related model changes.

B Sending a notification email immediately after a user registers.

C Logging model changes for audit purposes automatically.

D Performing complex business logic that requires multiple database queries and transactions.

💡 Hint

Consider the complexity and side effects of the task inside a signal handler.

Signals should be lightweight and fast. Complex logic with multiple queries can cause performance and debugging issues.