Named URLs for maintainability in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of reversing a named URL?

Given the following Django URL pattern and usage, what will be the output of print(url)?

Django

from django.urls import path, reverse

urlpatterns = [
    path('profile/<int:user_id>/', lambda request: None, name='user-profile'),
]

url = reverse('user-profile', kwargs={'user_id': 42})
print(url)

A user-profile/42/

B /profile/user_id/42/

C /profile/42/

D /profile/<int:user_id>/

💡 Hint

Remember that reverse uses the name and kwargs to build the URL string.

The reverse function uses the named URL pattern and fills in the parameters from kwargs. Here, user_id=42 replaces the placeholder, producing /profile/42/.

📝 Syntax

intermediate

Which option correctly defines a named URL with a slug parameter?

Which of the following Django URL patterns correctly defines a named URL that accepts a slug parameter named post_slug?

A path('post/<slug:post_slug>/', views.post_detail, name='post-detail')

B path('post/<post_slug:slug>/', views.post_detail, name='post-detail')

C path('post/<slug>/', views.post_detail, name='post-detail')

D path('post/<str:post_slug>/', views.post_detail, name='post-detail')

💡 Hint

Check the syntax for path converters in Django URLs.

The correct syntax for a slug parameter is <slug:parameter_name>. Option A uses this correctly.

🔧 Debug

advanced

Why does this reverse call raise NoReverseMatch?

Given the URL pattern and reverse call below, why does the reverse call raise a NoReverseMatch error?

Django

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

url = reverse('article-detail', kwargs={'pk': 5})

A Because the URL pattern name 'article-detail' is misspelled in reverse

B Because the URL pattern expects 'id' but reverse is given 'pk' as the keyword argument

C Because reverse cannot be used with integer parameters

D Because the URL pattern is missing a trailing slash

💡 Hint

Check the parameter names in the URL pattern and reverse call.

The URL pattern expects a parameter named id, but the reverse call provides pk. This mismatch causes NoReverseMatch.

❓ state_output

advanced

What is the rendered output of this template using named URLs?

Given the URL pattern and template snippet below, what will be the rendered HTML output?

Django

{% raw %}
# urls.py
urlpatterns = [
    path('dashboard/', views.dashboard, name='dashboard'),
]

# template.html
<a href="{% url 'dashboard' %}">Go to Dashboard</a>
{% endraw %}

A <a href="/dashboard/">Go to Dashboard</a>

B <a href="dashboard">Go to Dashboard</a>

C <a href="/dashboard">Go to Dashboard</a>

D <a href="/dashboard/index/">Go to Dashboard</a>

💡 Hint

Remember Django adds trailing slashes by default in URLs.

The named URL 'dashboard' corresponds to the path '/dashboard/'. The template tag {% url 'dashboard' %} renders this full path including the trailing slash.

🧠 Conceptual

expert

Why are named URLs important for maintainability in Django projects?

Which of the following best explains why using named URLs improves maintainability in Django projects?

A Named URLs prevent users from accessing URLs without authentication

B Named URLs automatically optimize database queries related to URL routing

C Named URLs enforce strict type checking on URL parameters at runtime

D Named URLs allow changing URL patterns without updating every place the URL is used, by referring to the name instead of the path string

💡 Hint

Think about how URLs are referenced in templates and views.

Named URLs let you change the actual URL path in one place (the URLconf) without changing all the code that links to it. This reduces errors and makes updates easier.