Template-level authorization in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What will this Flask template render when user is not admin?

Consider this Flask Jinja2 template snippet:

{% if current_user.is_admin %}
  
{% else %}
  
You do not have permission to delete posts.
{% endif %}

If current_user.is_admin is False, what will be rendered?

A <p>You do not have permission to delete posts.</p>

B <button>Delete Post</button>

C Nothing will be rendered

D An error will occur because current_user is undefined

💡 Hint

Think about how the {% if %} condition controls what is shown.

The template checks if current_user.is_admin is true. If false, it shows the <p> message. So option A is correct.

📝 Syntax

intermediate

Identify the syntax error in this Jinja2 authorization check

Which option contains a syntax error in this template authorization snippet?

{% if user.is_authenticated and user.is_admin %}
  
Welcome, admin!
{% endif %}

A

{% if user.is_authenticated && user.is_admin %}
  <p>Welcome, admin!</p>
{% endif %}

B

{% if user.is_authenticated and user.is_admin %}
  <p>Welcome, admin!</p>
{% endif %}

C

{% if user.is_authenticated and user.is_admin %}
  <p>Welcome, admin!</p>
{% end %}

D

{% if user.is_authenticated and user.is_admin %}
  <p>Welcome, admin!</p>

💡 Hint

Check the logical operator syntax in Jinja2.

Jinja2 uses and not && for logical AND. Option A uses invalid &&, causing a syntax error.

❓ state_output

advanced

What is the output when user is authenticated but not admin?

Given this Flask template snippet:

{% if user.is_authenticated %}
  {% if user.is_admin %}
    
Admin Panel
  {% else %}
    
User Dashboard
  {% endif %}
{% else %}
  
Please log in.
{% endif %}

If user.is_authenticated is True and user.is_admin is False, what will be rendered?

A <p>Admin Panel</p>

B Nothing will be rendered

C <p>Please log in.</p>

D <p>User Dashboard</p>

💡 Hint

Follow the nested {% if %} conditions carefully.

The user is authenticated but not admin, so the inner {% else %} branch runs, showing User Dashboard.

🔧 Debug

advanced

Why does this template raise an error when user is None?

Consider this template snippet:

{% if user.is_admin %}
  
Admin content
{% else %}
  
Regular content
{% endif %}

If user is None, what error occurs and why?

A TypeError because user is not a boolean

B SyntaxError due to missing endif

C AttributeError because NoneType has no attribute 'is_admin'

D No error, renders 'Regular content'

💡 Hint

Think about what happens when you try to access a property on None.

Accessing user.is_admin when user is None causes an AttributeError because NoneType has no such attribute.

🧠 Conceptual

expert

Which template-level authorization approach prevents unauthorized content rendering best?

In Flask templates, which approach best ensures unauthorized users cannot see admin-only content?

A Render all content and rely on CSS to hide admin sections from unauthorized users

B Use <code>{% if current_user.is_admin %}</code> to conditionally show admin content in templates

C Send all data to the template and use JavaScript to hide admin content on the client side

D Do not check authorization in templates; only check in backend routes

💡 Hint

Think about where content is actually removed versus just hidden.

Using template-level {% if %} checks prevents unauthorized content from being sent to the browser, which is more secure than hiding with CSS or JavaScript. Backend checks alone are not enough if templates render all content.

Practice

1. What is the main purpose of using template-level authorization in a Flask application?

easy

A. To control what content users can see based on their roles or permissions

B. To speed up the loading time of templates

C. To change the style of the webpage dynamically

D. To store user data securely in the database

Solution

1. Step 1: Understand template-level authorization

   Template-level authorization is about controlling visibility of content in templates based on user roles or permissions.

2. Step 2: Identify the main purpose

   The main goal is to restrict or allow content display depending on who the user is.

3. Final Answer:

   To control what content users can see based on their roles or permissions -> Option A

4. Quick Check:

   Authorization controls content visibility [OK]

Hint: Authorization controls content visibility in templates [OK]

Common Mistakes:

• Confusing authorization with styling or performance
• Thinking it stores data instead of controlling view
• Mixing backend data storage with frontend display control

2. Which of the following is the correct way to check a user's role in a Flask Jinja2 template?

easy

A. {{ if user.role == 'admin' }} ... {{ endif }}

B. {% check user.role == 'admin' %} ... {% endcheck %}

C. {% if user.role == 'admin' %} ... {% endif %}

D. <% if user.role == 'admin' %> ... <% endif %>

Solution

1. Step 1: Recall Jinja2 syntax for conditionals

   Jinja2 uses {% if condition %} ... {% endif %} blocks for conditional rendering.

2. Step 2: Match syntax with options

   {% if user.role == 'admin' %} ... {% endif %} uses correct Jinja2 syntax. The other options use invalid or other template syntax.

3. Final Answer:

   {% if user.role == 'admin' %} ... {% endif %} -> Option C

4. Quick Check:

   Jinja2 uses {% if %} ... {% endif %} [OK]

Hint: Use {% if %} ... {% endif %} for conditions in Jinja2 templates [OK]

Common Mistakes:

• Using {{ }} for control flow instead of {% %}
• Confusing Jinja2 with other template languages
• Using incorrect tags like <% %> which are not Jinja2

3. Given this Flask template snippet:

{% if user.is_authenticated and user.role == 'editor' %}
  
Edit content here
{% else %}
  
View only
{% endif %}

What will be displayed if user.is_authenticated is True but user.role is 'viewer'?

medium

A. Edit content here

B. View only

C. Nothing will be displayed

D. Template error occurs

Solution

1. Step 1: Evaluate the condition

   The condition requires user.is_authenticated to be True AND user.role to be 'editor'. Here, role is 'viewer', so condition is False.

2. Step 2: Determine which block runs

   Since condition is False, the else block runs, displaying <p>View only</p>.

3. Final Answer:

   <p>View only</p> -> Option B

4. Quick Check:

   Condition false triggers else block [OK]

Hint: Check both conditions; else block shows if any fail [OK]

Common Mistakes:

• Assuming only one condition matters
• Thinking 'viewer' role passes the 'editor' check
• Expecting no output when else block exists

4. You have this template code:

{% if user.role = 'admin' %}
  
Admin panel
{% endif %}

What is the problem with this code?

medium

A. Using <p> tags inside a template is not allowed

B. Missing else block for non-admin users

C. Incorrect indentation inside the if block

D. Using single equals sign (=) instead of double equals (==) in the if condition

Solution

1. Step 1: Identify the conditional syntax error

   In Jinja2, comparisons use '==' not '='. '=' is assignment and invalid in if conditions.

2. Step 2: Understand the impact

   Using '=' causes a template syntax error and prevents rendering.

3. Final Answer:

   Using single equals sign (=) instead of double equals (==) in the if condition -> Option D

4. Quick Check:

   Use '==' for comparisons in Jinja2 if statements [OK]

Hint: Use '==' for comparisons, '=' causes errors [OK]

Common Mistakes:

• Using '=' instead of '==' in conditions
• Thinking missing else causes syntax error
• Believing HTML tags are disallowed in templates

5. You want to show a special admin menu only if the user is authenticated and has either 'admin' or 'superuser' role. Which template code correctly implements this?

hard

A. {% if user.is_authenticated and user.role in ['admin', 'superuser'] %}
Admin Menu
{% endif %}

B. {% if user.is_authenticated or user.role == 'admin' or user.role == 'superuser' %}
Admin Menu
{% endif %}

C. {% if user.is_authenticated and user.role == 'admin' or 'superuser' %}
Admin Menu
{% endif %}

D. {% if user.is_authenticated and user.role == 'admin' or user.role == 'superuser' %}
Admin Menu
{% endif %}

Solution

1. Step 1: Understand the condition requirements

   User must be authenticated AND have role 'admin' OR 'superuser'.

2. Step 2: Analyze each option

   {% if user.is_authenticated and user.role == 'admin' or user.role == 'superuser' %}
   Admin Menu
   {% endif %} lacks parentheses around the or conditions, resulting in incorrect logic: (is_authenticated and role=='admin') or role=='superuser' due to operator precedence. {% if user.is_authenticated or user.role == 'admin' or user.role == 'superuser' %}
   Admin Menu
   {% endif %} uses or between authentication and roles, allowing unauthenticated users. {% if user.is_authenticated and user.role == 'admin' or 'superuser' %}
   Admin Menu
   {% endif %} has incorrect syntax and logic. {% if user.is_authenticated and user.role in ['admin', 'superuser'] %} <nav>Admin Menu</nav> {% endif %} uses 'in' to check role membership, which is clean and correct.

3. Final Answer:

   {% if user.is_authenticated and user.role in ['admin', 'superuser'] %} <nav>Admin Menu</nav> {% endif %} -> Option A

4. Quick Check:

   Use 'in' for multiple role checks with and for authentication [OK]

Hint: Use 'and' plus 'in' to check multiple roles cleanly [OK]

Common Mistakes:

• Using 'or' instead of 'and' for authentication
• Incorrect syntax for multiple role checks
• Missing parentheses causing logic errors