Serializers for data conversion in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this serializer's data?

Given the Django REST Framework serializer below, what will be the output of serializer.data when serializing the user instance?

Django

from rest_framework import serializers

class UserSerializer(serializers.Serializer):
    id = serializers.IntegerField()
    username = serializers.CharField(max_length=100)
    is_active = serializers.BooleanField(default=True)

user = type('User', (), {'id': 1, 'username': 'alice', 'is_active': False})()
serializer = UserSerializer(user)

A {'id': 1, 'username': 'alice', 'is_active': False}

B {'id': '1', 'username': 'alice', 'is_active': False}

C {'id': 1, 'username': 'alice', 'is_active': True}

D Raises AttributeError because user is not a model instance

💡 Hint

Look at the values assigned to the user instance attributes and how the serializer reads them.

The serializer reads the attributes from the user object as they are. Since is_active is set to False on the user, the output reflects that value. The serializer does not change the values, it just converts them to the specified types.

📝 Syntax

intermediate

Which serializer code will correctly validate nested data?

You want to create a serializer that validates a nested dictionary for a blog post with an author. Which option correctly defines the nested serializer?

Django

from rest_framework import serializers

class AuthorSerializer(serializers.Serializer):
    name = serializers.CharField(max_length=100)

class PostSerializer(serializers.Serializer):
    title = serializers.CharField(max_length=200)
    author = ???  # Fill this line correctly

A author = serializers.Serializer()

B author = serializers.DictField()

C author = serializers.CharField()

D author = AuthorSerializer()

💡 Hint

Think about how to embed one serializer inside another for nested validation.

To validate nested data, you embed one serializer inside another by assigning the nested serializer as a field. Using AuthorSerializer() inside PostSerializer allows validation of the nested author dictionary.

🔧 Debug

advanced

Why does this serializer raise a ValidationError?

Consider this serializer and data. Why does calling serializer.is_valid() raise a ValidationError?

Django

from rest_framework import serializers

class ProductSerializer(serializers.Serializer):
    name = serializers.CharField(max_length=50)
    price = serializers.DecimalField(max_digits=5, decimal_places=2)

input_data = {'name': 'Pen', 'price': '12.345'}
serializer = ProductSerializer(data=input_data)
serializer.is_valid(raise_exception=True)

A Price has more decimal places than allowed (3 instead of 2)

B Name exceeds max length of 50 characters

C Missing required field 'price'

D Price is a string, should be a float

💡 Hint

Check the decimal places allowed in the DecimalField and the input value.

The price field allows only 2 decimal places, but the input has 3 decimal places ('12.345'). This causes a validation error.

❓ state_output

advanced

What is the value of serializer.validated_data after validation?

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

Django

from rest_framework import serializers

class CommentSerializer(serializers.Serializer):
    text = serializers.CharField()
    likes = serializers.IntegerField(default=0)

input_data = {'text': 'Nice post!'}
serializer = CommentSerializer(data=input_data)
serializer.is_valid()

A {'text': 'Nice post!'}

B {'text': 'Nice post!', 'likes': None}

C {'text': 'Nice post!', 'likes': 0}

D Raises ValidationError because 'likes' is missing

💡 Hint

Consider how default values work in serializers when fields are missing in input.

The likes field has a default value of 0, so if it is missing in input data, the serializer adds it with the default value in validated_data.

🧠 Conceptual

expert

Which statement about serializer create() method is true?

In Django REST Framework, when you override the create() method in a serializer, which statement is correct?

A It automatically saves data to the database without needing to call <code>save()</code>

B It must return the created model instance after saving the validated data

C It is called before <code>is_valid()</code> to prepare data

D It is only used for updating existing instances, not creating new ones

💡 Hint

Think about the role of create() in the serializer lifecycle during object creation.

The create() method is responsible for creating and returning a new model instance using the validated data. It is called by serializer.save() after validation.