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

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when Django matches a URL pattern?

When a user visits a URL, Django tries to find a matching pattern in the URL configuration. What is the next step after Django finds a matching URL pattern?

A Django immediately renders the template without calling any view.

B Django calls the associated view function or class to handle the request.

C Django sends a 404 error response to the user.

D Django directly queries the database for data.

💡 Hint

Think about what Django does to process the request after matching the URL.

After matching a URL pattern, Django calls the view function or class linked to that pattern. The view handles the request and prepares a response.

❓ state_output

intermediate

What does a Django view typically return?

Consider a simple Django view function. What is the usual type of object that a Django view returns to complete the request?

Django

def my_view(request):
    # some logic here
    return ???

A A Python dictionary with data only.

B A URL string to redirect the user.

C An HttpResponse object containing the content to send back to the browser.

D A database query set.

💡 Hint

Think about what Django needs to send back to the browser.

Django views return an HttpResponse object that holds the content (like HTML) to display in the browser.

📝 Syntax

advanced

Identify the correct way to render a template in a Django view

Which of the following code snippets correctly renders a template named 'home.html' with a context dictionary in a Django view?

A return render(request, 'home.html', {'name': 'Alice'})

B return render_to_response('home.html', {'name': 'Alice'})

C return HttpResponse('home.html', {'name': 'Alice'})

D return render_template('home.html', {'name': 'Alice'})

💡 Hint

Look for the modern Django shortcut function that takes request, template name, and context.

The render function is the recommended way to render templates in Django views. It takes the request, template name, and context dictionary.

🔧 Debug

advanced

Why does this Django view raise a TemplateDoesNotExist error?

Given this view code, why does Django raise a TemplateDoesNotExist error when accessing the URL? ```python def my_view(request): return render(request, 'dashboard.html') ``` Assuming 'dashboard.html' exists in the templates folder.

Django

def my_view(request):
    return render(request, 'dashboard.html')

A The templates folder is not configured correctly in settings.py.

B The view forgot to pass a context dictionary to render.

C The URL pattern is missing for this view.

D The render function is missing the request argument.

💡 Hint

Check if Django knows where to find templates.

If Django cannot find the template file, it usually means the templates directory is not set up properly in the settings.py under TEMPLATES configuration.

🧠 Conceptual

expert

Order of Django request processing steps

Put these Django request processing steps in the correct order from when a user sends a request to when the response is sent back:

A 3,1,2,4

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about the natural flow from URL to view to template to response.

The correct order is: Django matches the URL, the view processes the request, the template renders the data, and finally Django sends the response.

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