Why templates separate presentation in Django - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do Django templates separate presentation from logic?

In Django, templates are used to separate the presentation layer from the business logic. What is the main benefit of this separation?

A It prevents any changes to the website layout once the code is written.

B It forces all data processing to happen in templates, improving performance.

C It combines HTML and Python code in one file for faster development.

D It allows designers to work on HTML without touching Python code, making collaboration easier.

💡 Hint

Think about who works on design and who works on code in a team.

Separating templates from logic lets designers focus on HTML and CSS, while developers handle Python code. This clear division improves teamwork and maintainability.

❓ component_behavior

intermediate

What happens if you put complex logic inside a Django template?

Consider a Django template that contains complex data processing logic instead of just displaying data. What is the likely outcome?

A The template becomes hard to read and maintain, making debugging difficult.

B The template runs faster because it handles all logic internally.

C The Django framework automatically moves logic to views for you.

D The template will ignore the logic and only show static content.

💡 Hint

Think about code clarity and who should handle logic.

Templates are meant for presentation. Complex logic in templates makes them messy and hard to maintain. Logic should stay in views or models.

📝 Syntax

advanced

Identify the correct way to pass data to a Django template

Which of the following Django view snippets correctly passes a list of items to a template named 'list.html'?

Django

def item_list(request):
    items = ['apple', 'banana', 'cherry']
    # Fill in the correct return statement below

A return render(request, 'list.html', {'items': items})

B return render('list.html', request, {'items': items})

C return render(request, {'items': items}, 'list.html')

D return render(request, 'list.html', items)

💡 Hint

Check the order of arguments in the render function.

The render function takes the request, template name, then context dictionary. Only option A follows this order correctly.

❓ state_output

advanced

What will the Django template output?

Given the context {'user': {'name': 'Anna', 'age': 30}}, what will this Django template output?

Django

{% if user.age > 18 %}
  <p>Welcome, {{ user.name }}!</p>
{% else %}
  <p>Access denied.</p>
{% endif %}

A <p>Welcome, {{ user.name }}!</p>

B <p>Access denied.</p>

C <p>Welcome, Anna!</p>

D Template error due to invalid syntax

💡 Hint

Check the age condition and how variables are displayed.

The user's age is 30, which is greater than 18, so the first block runs and shows the welcome message with the user's name.

🔧 Debug

expert

Why does this Django template raise an error?

Consider this Django template snippet:

{% for item in items %}
  
{{ item.name }}
{% endfor %}

The view passes {'items': ['apple', 'banana']} as context. Why does this cause an error?

A Because the for loop syntax is incorrect and missing a colon.

B Because strings do not have a 'name' attribute, causing a runtime error.

C Because the template variable 'items' is not defined in the context.

D Because Django templates cannot loop over lists.

💡 Hint

Think about the type of each item in the list and what the template tries to access.

The context 'items' is a list of strings. Strings do not have a 'name' attribute, so {{ item.name }} causes an error.