How Django processes a request (URL → View → Template) - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a URL pattern that connects the path 'home/' to the view function.

Django

urlpatterns = [path('home/', [1])]

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

Arender

Bhome_view

CHttpResponse

Dinclude

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'render' or 'HttpResponse' directly in the URL pattern instead of a view function.

Using 'include' which is for including other URL configurations.

The URL pattern connects the URL 'home/' to the view function named home_view.

2fill in blank

medium

Complete the view function to render the 'home.html' template with the request.

Django

def home_view(request):
    return [1](request, 'home.html')

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

Arender

BHttpResponse

Credirect

Dget_object_or_404

Attempts:

3 left

💡 Hint

Common Mistakes

Using HttpResponse directly without rendering a template.

Using redirect which sends a new URL instead of rendering a template.

The render function combines the request and template to create an HttpResponse.

3fill in blank

hard

Fix the error in the view function to correctly pass context data to the template.

Django

def home_view(request):
    context = {'message': 'Hello!'}
    return render(request, 'home.html', [1])

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

Acontext

Brequest

C'message'

Drender

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the request object again instead of context.

Passing a string key instead of the whole context dictionary.

The third argument to render is the context dictionary to pass data to the template.

4fill in blank

hard

Fill both blanks to complete the URL pattern that includes another app's URLs and names the route 'blog-home'.

Django

urlpatterns = [path('blog/', [1]('blog.urls'), name=[2])]

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

Ainclude

B'blog-home'

C'blog_home'

Dpath

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'path' instead of 'include' to include URLs.

Using an invalid name format or missing quotes.

include is used to include another URLconf, and the name is a string identifier for the route.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps each word to its length if the length is greater than 3.

Django

lengths = { [1]: [2] for [3] in words if len([3]) > 3 }

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

Aword

Blen(word)

Ditem

Attempts:

3 left

💡 Hint

Common Mistakes

Using different variable names inconsistently.

Not filtering words by length.

This comprehension creates a dictionary where keys are words and values are their lengths, filtering words longer than 3 characters.

Practice

1. In Django, what is the first step when a user visits a website URL?

easy

A. Django directly renders the template without processing.

B. Django matches the URL to a view using URL patterns.

C. Django sends data to the database.

D. Django executes JavaScript on the client side.

Solution

1. Step 1: Understand URL routing in Django

   Django uses URL patterns defined in urls.py to find which view should handle the request.

2. Step 2: Identify the first action on a request

   The first action is matching the URL to a view, not rendering or database access.

3. Final Answer:

   Django matches the URL to a view using URL patterns. -> Option B

4. Quick Check:

   URL routing = matching URL to view [OK]

Hint: Remember: URL first matches view, then view handles data [OK]

Common Mistakes:

• Thinking template renders before view runs
• Assuming database is accessed before URL matching
• Confusing client-side JavaScript with Django server process

2. Which of the following is the correct way to define a URL pattern in Django's urls.py?

easy

A. path('home/', views.home_view, name='home')

B. url('home/', views.home_view)

C. route('home/', views.home_view)

D. link('home/', views.home_view)

Solution

1. Step 1: Recall Django URL pattern syntax

   Django 3+ uses path() to define URL patterns, with URL string, view function, and optional name.

2. Step 2: Identify correct function name

   url() is deprecated, and route() or link() are invalid.

3. Final Answer:

   path('home/', views.home_view, name='home') -> Option A

4. Quick Check:

   Use path() for URL patterns [OK]

Hint: Use path() in urls.py, not url() or other names [OK]

Common Mistakes:

• Using deprecated url() instead of path()
• Using non-existent functions like route() or link()
• Omitting the view function argument

3. Given this view function, what will be the rendered output if the template displays {{ message }}?

def hello_view(request):
    context = {'message': 'Hello, Django!'}
    return render(request, 'hello.html', context)

medium

A. Hello, Django!

B. context

C. hello.html

D. request

Solution

1. Step 1: Understand context passing in Django views

   The view passes a dictionary with key 'message' and value 'Hello, Django!' to the template.

2. Step 2: Template renders variable from context

   The template uses {{ message }} to display the value 'Hello, Django!'.

3. Final Answer:

   Hello, Django! -> Option A

4. Quick Check:

   Template variable = context value [OK]

Hint: Template {{ var }} shows context['var'] value [OK]

Common Mistakes:

• Confusing template name with output
• Thinking context dictionary prints as string
• Assuming request object is shown in template

4. What is wrong with this Django view function?

def my_view(request):
    return render('my_template.html')

medium

A. The function name must be capitalized.

B. The template name should be a dictionary.

C. The view should return HttpResponseRedirect instead.

D. The render function is missing the request argument.

Solution

1. Step 1: Check render function signature

   render() requires at least two arguments: request and template name.

2. Step 2: Identify missing argument

   The code only passes the template name, missing the request argument.

3. Final Answer:

   The render function is missing the request argument. -> Option D

4. Quick Check:

   render(request, template) needs request first [OK]

Hint: render() always needs request as first argument [OK]

Common Mistakes:

• Forgetting to pass request to render()
• Thinking template name should be a dict
• Confusing render with redirect functions

5. You want to display a list of products on a page. Which sequence correctly describes how Django processes this request? A user visits /products/. The URL pattern matches products_view. The view fetches products from the database and passes them to products.html template. The template shows the product names in a list. Which is the correct order of steps Django follows internally?

hard

A. View fetches data -> URL matches -> Template renders -> Response sent

B. Template renders -> View fetches data -> URL matches -> Response sent

C. URL -> View fetches data -> Template renders with data -> Response sent

D. Response sent -> URL matches -> View fetches data -> Template renders

Solution

1. Step 1: URL matching

   Django first matches the incoming URL to the correct view function using URL patterns.

2. Step 2: View processes request

   The view fetches data (products) from the database and prepares context for the template.

3. Step 3: Template rendering and response

   The template uses the context to render HTML, which Django sends as the HTTP response.

4. Final Answer:

   URL -> View fetches data -> Template renders with data -> Response sent -> Option C

5. Quick Check:

   URL then view then template then response [OK]

Hint: Remember: URL matches first, then view, then template, then response [OK]

Common Mistakes:

• Thinking template renders before URL matching
• Mixing order of view and URL matching
• Assuming response sent before processing