path function for routes in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Django URL pattern matching?

Given the following URL pattern and a request to '/blog/42/', what view will be called and what will be the value of the captured parameter?

Django

from django.urls import path
from . import views

urlpatterns = [
    path('blog/<int:post_id>/', views.post_detail, name='post_detail'),
]

# Assume views.post_detail is defined to accept post_id as argument.

A The view 'post_detail' is called with post_id='blog/42/'

B The view 'post_detail' is called with post_id='42/'

C No view is called because the URL does not match

D The view 'post_detail' is called with post_id=42

💡 Hint

Look at how the path converter works in the URL pattern.

The path function captures the integer part after 'blog/' and passes it as an integer argument named post_id to the view.

📝 Syntax

intermediate

Which option correctly defines a path with a string parameter named 'username'?

Select the correct Django path function usage to capture a string parameter 'username' from the URL '/user//'

A path('user/<str:username>/', views.profile, name='profile')

B path('user/<username>/', views.profile, name='profile')

C path('user/<int:username>/', views.profile, name='profile')

D path('user/<slug:username>/', views.profile, name='profile')

💡 Hint

Remember the syntax for path converters in Django's path function.

The correct syntax to capture a string parameter is . Omitting the converter defaults to str but is not recommended. Using int or slug changes the expected format.

🔧 Debug

advanced

Why does this URL pattern cause a runtime error?

Examine the following urlpatterns list and identify why it causes an error when Django starts.

Django

from django.urls import path

urlpatterns = [
    path('article/<int:id>/', views.article_detail),
    path('article/<int:id>/', views.article_edit),
]

A Missing 'name' argument in path causes runtime error.

B The views module is not imported, causing NameError.

C Duplicate URL patterns with the same path cause ambiguity and Django raises an error.

D The variable name 'id' is reserved and causes error.

💡 Hint

Check if all referenced modules are imported.

The code references 'views.article_detail' and 'views.article_edit' without importing the 'views' module, causing a NameError when Django loads the URL configuration.

❓ state_output

advanced

What is the value of 'kwargs' passed to the view for this path?

Given the URL pattern and a request to '/shop/electronics/123/', what is the kwargs dictionary passed to the view?

Django

path('shop/<slug:category>/<int:item_id>/', views.item_detail, name='item_detail')

A {'category': 'electronics', 'item_id': 123}

B {'category': 'electronics/123', 'item_id': None}

C {'category': 'shop', 'item_id': 'electronics'}

D {} (empty dictionary)

💡 Hint

Look at how multiple path converters capture parts of the URL.

The slug converter captures 'electronics' as category and int converter captures 123 as item_id.

🧠 Conceptual

expert

Which option best explains the difference between path() and re_path() in Django routing?

Choose the most accurate explanation about the difference between path() and re_path() functions in Django URL configuration.

A path() automatically escapes special characters; re_path() does not.

B path() supports only static URLs; re_path() supports dynamic URLs with parameters.

C path() uses simpler, readable converters for common patterns; re_path() uses full regular expressions for complex matching.

D path() is deprecated and replaced by re_path() in modern Django versions.

💡 Hint

Think about the syntax and flexibility differences between path and re_path.

path() provides easy-to-read converters like , , while re_path() allows full regex for advanced patterns.