ModelSerializer for model-backed APIs in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this ModelSerializer validation?

Given the following serializer and input data, what will serializer.is_valid() return?

Django

from rest_framework import serializers
from myapp.models import Product

class ProductSerializer(serializers.ModelSerializer):
    class Meta:
        model = Product
        fields = ['id', 'name', 'price']

input_data = {'name': 'Book', 'price': -10}
serializer = ProductSerializer(data=input_data)
valid = serializer.is_valid()

A False, because price cannot be negative

B True, because ModelSerializer does not validate field values by default

C Raises a ValidationError immediately on is_valid() call

D True, but serializer.errors will contain the price error

💡 Hint

Think about how ModelSerializer uses model field validators automatically.

ModelSerializer uses the model's field validators, so negative price (assuming model has positive constraint) causes is_valid() to return False.

📝 Syntax

intermediate

Which option correctly defines a ModelSerializer for a model with a read-only field?

Choose the correct ModelSerializer code that makes the created_at field read-only.

Django

from rest_framework import serializers
from myapp.models import Event

A

class EventSerializer(serializers.ModelSerializer):
    class Meta:
        model = Event
        fields = ['id', 'name']
        read_only_fields = ['created_at']

B

class EventSerializer(serializers.ModelSerializer):
    class Meta:
        model = Event
        fields = ['id', 'name', 'created_at']
        read_only_fields = ['created_at']

C

class EventSerializer(serializers.ModelSerializer):
    created_at = serializers.ReadOnlyField()
    class Meta:
        model = Event
        fields = ['id', 'name', 'created_at']

D

class EventSerializer(serializers.ModelSerializer):
    class Meta:
        model = Event
        fields = ['id', 'name', 'created_at']
    created_at = serializers.ReadOnlyField()

💡 Hint

Check how to specify read-only fields in Meta class.

The read_only_fields attribute inside Meta is the standard way to mark model fields as read-only in ModelSerializer.

🔧 Debug

advanced

Why does this ModelSerializer raise a ValidationError on validation?

Consider this serializer and model. Why does calling serializer.is_valid(raise_exception=True) raise a ValidationError?

Django

class UserSerializer(serializers.ModelSerializer):
    class Meta:
        model = User
        fields = ['username', 'email', 'password']

serializer = UserSerializer(data={'username': 'alice', 'email': '[e-mail]'})
serializer.is_valid(raise_exception=True)
serializer.save()

A Because is_valid() was not called before save()

B Because serializer.save() requires an explicit commit argument

C Because 'password' is missing in input data and is required by the model

D Because the model User does not have an email field

💡 Hint

Check which fields are required and if they are provided.

The serializer expects all fields listed in fields. Missing 'password' causes ValidationError on is_valid().

❓ state_output

advanced

What is the value of serializer.validated_data after is_valid()?

Given this serializer and input, what will serializer.validated_data contain after is_valid()?

Django

class ArticleSerializer(serializers.ModelSerializer):
    class Meta:
        model = Article
        fields = ['title', 'content', 'author']

input_data = {'title': 'Hello', 'content': 'World', 'author': 5}
serializer = ArticleSerializer(data=input_data)
serializer.is_valid()
result = serializer.validated_data

A Empty dict because is_valid() was not called with raise_exception=True

B {'title': 'Hello', 'content': 'World', 'author': <User instance with id=5>}

C Raises ValidationError because author must be a User object

D {'title': 'Hello', 'content': 'World', 'author': 5}

💡 Hint

Recall the default serializer field used for model ForeignKey fields in ModelSerializer.

ModelSerializer uses PrimaryKeyRelatedField by default for foreign key relations, so validated_data contains the primary key value (5), not a model instance.

🧠 Conceptual

expert

Which statement about ModelSerializer behavior is true?

Choose the correct statement about how ModelSerializer handles nested writable relationships.

A You must override <code>create()</code> and <code>update()</code> to handle writable nested serializers

B Nested serializers are always read-only in ModelSerializer

C ModelSerializer automatically supports writable nested serializers without extra code

D ModelSerializer does not support nested serializers at all

💡 Hint

Think about how nested data is saved in DRF.

Writable nested serializers require custom create() and update() methods to save nested data properly.

Practice

1. What is the main purpose of Django's ModelSerializer in API development?

easy

A. To replace Django models with a new database system.

B. To automatically create serializers based on Django models, reducing manual code.

C. To handle user authentication in Django REST APIs.

D. To generate HTML forms from models automatically.

Solution

1. Step 1: Understand what ModelSerializer does

   ModelSerializer automatically creates serializer classes based on Django models, saving time and effort.

2. Step 2: Compare options with this purpose

   Only To automatically create serializers based on Django models, reducing manual code. correctly describes this purpose; others describe unrelated features.

3. Final Answer:

   To automatically create serializers based on Django models, reducing manual code. -> Option B

4. Quick Check:

   ModelSerializer = automatic serializer creation [OK]

Hint: ModelSerializer = auto serializer from model fields [OK]

Common Mistakes:

• Confusing ModelSerializer with authentication classes
• Thinking it generates HTML forms
• Believing it replaces models

2. Which of the following is the correct way to define a ModelSerializer for a model named Book?

easy

A. class BookSerializer(serializers.ModelSerializer):
class Meta:
model = Book
fields = '__all__'

B. class BookSerializer(serializers.Serializer):
model = Book
fields = '__all__'

C. class BookSerializer(serializers.ModelSerializer):
model = Book
fields = ['title', 'author']

D. class BookSerializer(serializers.ModelSerializer):
class Meta:
fields = ['title', 'author']

Solution

1. Step 1: Recall ModelSerializer syntax

   ModelSerializer requires a nested Meta class specifying the model and fields.

2. Step 2: Check each option

   class BookSerializer(serializers.ModelSerializer): class Meta: model = Book fields = '__all__' correctly uses Meta with model and fields. class BookSerializer(serializers.Serializer): model = Book fields = '__all__' uses Serializer, not ModelSerializer. class BookSerializer(serializers.ModelSerializer): model = Book fields = ['title', 'author'] misses Meta class. class BookSerializer(serializers.ModelSerializer): class Meta: fields = ['title', 'author'] misses model in Meta.

3. Final Answer:

   class BookSerializer(serializers.ModelSerializer): class Meta: model = Book fields = '__all__' -> Option A

4. Quick Check:

   Meta class with model and fields = correct syntax [OK]

Hint: ModelSerializer needs Meta with model and fields [OK]

Common Mistakes:

• Omitting the Meta class
• Using serializers.Serializer instead of ModelSerializer
• Not specifying the model inside Meta

3. Given the model and serializer below, what will serializer.data output for a Book instance with title='Django Basics' and author='Alice'?

class Book(models.Model):
    title = models.CharField(max_length=100)
    author = models.CharField(max_length=100)

class BookSerializer(serializers.ModelSerializer):
    class Meta:
        model = Book
        fields = ['title', 'author']

book = Book(title='Django Basics', author='Alice')
serializer = BookSerializer(book)

medium

A. {'author': 'Alice'}

B. {'title': 'Django Basics'}

C. {'title': 'Django Basics', 'author': 'Alice'}

D. Raises a TypeError because the instance is not saved

Solution

1. Step 1: Understand ModelSerializer output

   ModelSerializer outputs a dictionary with the fields specified in Meta for the given instance.

2. Step 2: Check fields and instance data

   Fields are 'title' and 'author', instance has both values set, so output includes both.

3. Final Answer:

   {'title': 'Django Basics', 'author': 'Alice'} -> Option C

4. Quick Check:

   Serializer fields match instance data [OK]

Hint: Serializer outputs all fields listed in Meta for instance [OK]

Common Mistakes:

• Assuming unsaved instance causes error
• Expecting partial fields output
• Confusing serializer.data with serializer.validated_data

4. What is wrong with this ModelSerializer definition?

class AuthorSerializer(serializers.ModelSerializer):
    class Meta:
        model = Author
        fields = 'name' 'email'

medium

A. Fields should be a list or tuple inside brackets, not separate strings.

B. ModelSerializer cannot serialize Author model.

C. Meta class must be outside the serializer class.

D. Fields must include '__all__' instead of specific names.

Solution

1. Step 1: Check fields syntax

   Fields must be a list or tuple, e.g. ['name', 'email'] or ('name', 'email'), not separate strings without brackets.

2. Step 2: Verify other options

   ModelSerializer can serialize any model, Meta must be nested, and fields can be specific names.

3. Final Answer:

   Fields should be a list or tuple inside brackets, not separate strings. -> Option A

4. Quick Check:

   Fields syntax requires brackets [OK]

Hint: Fields must be list or tuple with brackets [OK]

Common Mistakes:

• Writing fields as comma-separated strings without brackets
• Placing Meta class outside serializer
• Thinking '__all__' is mandatory

5. You want to create a ModelSerializer for a Product model but exclude the created_at and updated_at fields from the API output. Which is the best way to do this?

hard

A. Use fields = '__all__' and override to_representation to remove those fields.

B. Remove those fields from the model definition.

C. Manually list all fields except those two in fields.

D. Use exclude = ['created_at', 'updated_at'] in the Meta class.

Solution

1. Step 1: Understand ModelSerializer field exclusion

   ModelSerializer Meta supports an exclude attribute to omit fields easily.

2. Step 2: Evaluate options

   Use exclude = ['created_at', 'updated_at'] in the Meta class. uses exclude correctly. Use fields = '__all__' and override to_representation to remove those fields. is more complex and unnecessary. Manually list all fields except those two in fields. is error-prone and verbose. Remove those fields from the model definition. changes the model, which is not desired.

3. Final Answer:

   Use exclude = ['created_at', 'updated_at'] in the Meta class. -> Option D

4. Quick Check:

   Exclude fields via Meta.exclude [OK]

Hint: Use Meta.exclude to omit fields easily [OK]

Common Mistakes:

• Overriding methods unnecessarily
• Listing all fields manually
• Changing the model instead of serializer