Why DRF matters for APIs in Django - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Django REST Framework module for serializers.

Django

from rest_framework import [1]

Drag options to blanks, or click blank then click option'

Amodels

Bviews

Cserializers

Dforms

Attempts:

3 left

💡 Hint

Common Mistakes

Importing 'views' instead of 'serializers'

Using 'models' which is a Django core module

The serializers module in DRF helps convert complex data like Django models into JSON format for APIs.

2fill in blank

medium

Complete the code to create a simple API view using DRF's generic views.

Django

from rest_framework import generics

class BookList(generics.[1]):
    queryset = Book.objects.all()
    serializer_class = BookSerializer

Drag options to blanks, or click blank then click option'

AListAPIView

BCreateAPIView

CRetrieveAPIView

DUpdateAPIView

Attempts:

3 left

💡 Hint

Common Mistakes

Using CreateAPIView which is for creating new objects

Using RetrieveAPIView which is for single object detail

ListAPIView provides a read-only endpoint to list all objects, perfect for showing all books.

3fill in blank

hard

Fix the error in the serializer by completing the field declaration.

Django

from rest_framework import serializers

class BookSerializer(serializers.Serializer):
    title = serializers.[1](max_length=100)

Drag options to blanks, or click blank then click option'

AIntegerField

BBooleanField

CDateField

DCharField

Attempts:

3 left

💡 Hint

Common Mistakes

Using IntegerField for text

Using BooleanField which is true/false

CharField is used for text fields like a book's title.

4fill in blank

hard

Fill both blanks to create a view that allows listing and creating books.

Django

from rest_framework import generics

class BookListCreate(generics.[1], generics.[2]):
    queryset = Book.objects.all()
    serializer_class = BookSerializer

Drag options to blanks, or click blank then click option'

AListAPIView

BCreateAPIView

CRetrieveAPIView

DUpdateAPIView

Attempts:

3 left

💡 Hint

Common Mistakes

Using RetrieveAPIView which is for single items

Using UpdateAPIView which is for editing existing items

Combining ListAPIView and CreateAPIView allows the view to list all books and create new ones.

5fill in blank

hard

Fill all three blanks to write a serializer that validates a book's title length and includes an author field.

Django

from rest_framework import serializers

class BookSerializer(serializers.Serializer):
    title = serializers.[1](max_length=100)
    author = serializers.[2](max_length=50)

    def validate_title(self, value):
        if len(value) < [3]:
            raise serializers.ValidationError("Title too short")
        return value

Drag options to blanks, or click blank then click option'

ACharField

C5

DIntegerField

Attempts:

3 left

💡 Hint

Common Mistakes

Using IntegerField for author

Setting minimum length as a string instead of number

Both title and author are text fields, so use CharField. The minimum title length is set to 5.

Practice

1. Why is Django REST Framework (DRF) important when building APIs in Django?

easy

A. It simplifies API development by providing tools like serializers and viewsets.

B. It replaces Django's ORM for database management.

C. It is used only for building web pages, not APIs.

D. It automatically creates frontend user interfaces.

Solution

1. Step 1: Understand DRF's role in API development

   DRF provides serializers and viewsets that help organize API code and handle data conversion.

2. Step 2: Compare DRF with other Django features

   Django's ORM manages databases, but DRF focuses on API creation, not replacing ORM or frontend UI.

3. Final Answer:

   It simplifies API development by providing tools like serializers and viewsets. -> Option A

4. Quick Check:

   DRF simplifies API building = B [OK]

Hint: DRF helps build APIs faster with ready tools [OK]

Common Mistakes:

• Thinking DRF replaces Django ORM
• Confusing DRF with frontend frameworks
• Believing DRF only builds web pages

2. Which of the following is the correct way to import the serializer class from DRF?

easy

A. import rest_framework.Serializer

B. import django.serializers.Serializer

C. from django.rest_framework import Serializer

D. from rest_framework.serializers import Serializer

Solution

1. Step 1: Recall DRF import paths

   DRF's serializers are imported from rest_framework.serializers module.

2. Step 2: Check each option's syntax

   Only from rest_framework.serializers import Serializer uses the correct module path and syntax for importing Serializer.

3. Final Answer:

   from rest_framework.serializers import Serializer -> Option D

4. Quick Check:

   Correct DRF import syntax = A [OK]

Hint: DRF serializers come from rest_framework.serializers [OK]

Common Mistakes:

• Using django instead of rest_framework in import
• Wrong module paths causing ImportError
• Confusing package names

3. Given this DRF viewset code, what will be the output when accessing the API endpoint?

from rest_framework import viewsets
from myapp.models import Item
from myapp.serializers import ItemSerializer

class ItemViewSet(viewsets.ModelViewSet):
    queryset = Item.objects.all()
    serializer_class = ItemSerializer

medium

A. An error because viewsets.ModelViewSet is not valid.

B. A plain text list of Item objects without formatting.

C. A browsable API showing all Item objects with CRUD options.

D. A JSON response with only the first Item object.

Solution

1. Step 1: Understand ModelViewSet behavior

   ModelViewSet provides a full set of API views with list, create, retrieve, update, and delete actions.

2. Step 2: Recognize DRF's browsable API feature

   DRF automatically provides a browsable web interface for API endpoints using ModelViewSet.

3. Final Answer:

   A browsable API showing all Item objects with CRUD options. -> Option C

4. Quick Check:

   ModelViewSet gives browsable API with full CRUD = C [OK]

Hint: ModelViewSet gives full API with browsable interface [OK]

Common Mistakes:

• Thinking ModelViewSet returns plain text
• Assuming it returns only one object
• Believing ModelViewSet is invalid

4. What is wrong with this DRF serializer code?

from rest_framework import serializers

class UserSerializer(serializers.Serializer):
    username = serializers.CharField(max_length=100)
    email = serializers.EmailField()

    def create(self, validated_data):
        return User.objects.create(validated_data)

medium

A. Serializer classes cannot define create methods.

B. The create method should unpack validated_data with ** before passing to create().

C. CharField does not accept max_length argument.

D. EmailField is not a valid serializer field.

Solution

1. Step 1: Review create method usage

   The create method must pass validated_data as keyword arguments using ** to User.objects.create().

2. Step 2: Check other parts for errors

   EmailField and CharField usage are correct; serializers can define create methods.

3. Final Answer:

   The create method should unpack validated_data with ** before passing to create(). -> Option B

4. Quick Check:

   Use **validated_data in create() = D [OK]

Hint: Use ** to unpack validated_data in create() [OK]

Common Mistakes:

• Passing dict directly without unpacking
• Thinking EmailField is invalid
• Believing serializers can't have create methods

5. You want to build an API that returns only active users with their username and email. Which DRF components should you combine to achieve this cleanly and efficiently?

hard

A. Use a ModelViewSet with a serializer that includes username and email fields, and filter queryset for active users.

B. Write raw SQL queries and return plain JSON responses manually.

C. Use Django templates to render user data as HTML pages.

D. Create a custom middleware to filter users and serialize data.

Solution

1. Step 1: Identify DRF components for API

   ModelViewSet provides API endpoints; serializers define which fields to include.

2. Step 2: Apply filtering and field selection

   Filter the queryset to active users and use serializer to include only username and email.

3. Final Answer:

   Use a ModelViewSet with a serializer that includes username and email fields, and filter queryset for active users. -> Option A

4. Quick Check:

   ModelViewSet + filtered queryset + serializer fields = A [OK]

Hint: Combine ModelViewSet, serializer, and queryset filter [OK]

Common Mistakes:

• Using raw SQL instead of DRF tools
• Rendering HTML instead of JSON API
• Trying to filter users in middleware