Why authorization matters in Flask - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Flask class.

Flask

from flask import [1]
app = [1](__name__)

Drag options to blanks, or click blank then click option'

ARequest

Bredirect

Crender_template

DFlask

Attempts:

3 left

💡 Hint

Common Mistakes

Importing Request instead of Flask

Using render_template here

The Flask class is imported to create the app instance.

2fill in blank

medium

Complete the code to protect a route with a login check.

Flask

@app.route('/dashboard')
def dashboard():
    if not user_is_authenticated():
        return [1]('/login')
    return 'Welcome to your dashboard!'

Drag options to blanks, or click blank then click option'

Aredirect

Brender_template

Cabort

Drequest

Attempts:

3 left

💡 Hint

Common Mistakes

Using render_template instead of redirect

Using abort without explanation

Redirect sends the user to the login page if not authenticated.

3fill in blank

hard

Fix the error in the authorization check to abort with 403 if unauthorized.

Flask

from flask import abort

def admin_panel():
    if not current_user.is_admin:
        [1](403)
    return 'Admin content here.'

Drag options to blanks, or click blank then click option'

Alogin_required

Babort

Crender_template

Dredirect

Attempts:

3 left

💡 Hint

Common Mistakes

Using redirect instead of abort

Calling login_required as a function here

abort(403) stops the request and shows a forbidden error.

4fill in blank

hard

Fill both blanks to check if user role is 'editor' and allow access.

Flask

def edit_article():
    if current_user.role [1] 'editor':
        return 'Edit page'
    else:
        return [2](403)

Drag options to blanks, or click blank then click option'

A==

Babort

C!=

Dredirect

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' instead of '=='

Using redirect instead of abort

Use '==' to compare role and abort(403) to deny access.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension filtering users with role 'admin'.

Flask

admins = {user['[1]']: user for user in users if user['[2]'] [3] 'admin'}

Drag options to blanks, or click blank then click option'

Ausername

Brole

C==

Demail

Attempts:

3 left

💡 Hint

Common Mistakes

Using email as key

Using '!=' instead of '=='

The dictionary keys are usernames, filtered by role equal to 'admin'.

Practice

1. Why is authorization important in a Flask web application?

easy

A. It speeds up the app's loading time.

B. It helps with styling the web pages.

C. It controls which users can access certain parts of the app.

D. It automatically fixes bugs in the code.

Solution

1. Step 1: Understand the purpose of authorization

   Authorization is about controlling user access to different parts of an app based on their roles or permissions.

2. Step 2: Compare options with authorization purpose

   Only It controls which users can access certain parts of the app. correctly describes this control. Other options describe unrelated features.

3. Final Answer:

   It controls which users can access certain parts of the app. -> Option C

4. Quick Check:

   Authorization = Access control [OK]

Hint: Authorization means controlling user access rights [OK]

Common Mistakes:

• Confusing authorization with authentication
• Thinking authorization improves speed
• Mixing authorization with UI styling

2. Which Flask code snippet correctly checks if a user has the 'admin' role before allowing access?

easy

A. if current_user.role == 'admin':
return 'Access granted'

B. if current_user == 'admin':
return 'Access granted'

C. if user.role = 'admin':
return 'Access granted'

D. if current_user.role != 'admin':
return 'Access granted'

Solution

1. Step 1: Identify correct role check syntax

   In Flask, to check a user's role, use 'current_user.role == "admin"'.

2. Step 2: Eliminate incorrect syntax and logic

   if current_user == 'admin': return 'Access granted' compares user object to string, incorrect. if user.role = 'admin': return 'Access granted' uses single '=', which is assignment, not comparison. if current_user.role != 'admin': return 'Access granted' grants access if role is not admin, which is wrong logic.

3. Final Answer:

   if current_user.role == 'admin': return 'Access granted' -> Option A

4. Quick Check:

   Correct role check uses '==' and proper attribute [OK]

Hint: Use '==' to compare role strings, not '=' [OK]

Common Mistakes:

• Using '=' instead of '==' for comparison
• Comparing user object directly to string
• Reversing logic with '!=' instead of '=='

3. Given this Flask route code, what will be the output if a user with role 'guest' accesses it?

from flask import abort

@app.route('/admin')
def admin_panel():
    if current_user.role != 'admin':
        abort(403)
    return 'Welcome, admin!'

medium

A. 500 Internal Server Error

B. Welcome, admin!

C. 404 Not Found error page

D. 403 Forbidden error page

Solution

1. Step 1: Analyze role check condition

   The code aborts with 403 error if the user's role is not 'admin'. A 'guest' role triggers this condition.

2. Step 2: Determine output for guest user

   Since 'guest' != 'admin', abort(403) runs, showing a 403 Forbidden error page.

3. Final Answer:

   403 Forbidden error page -> Option D

4. Quick Check:

   Non-admin user triggers abort(403) [OK]

Hint: abort(403) means access denied error [OK]

Common Mistakes:

• Thinking non-admin sees welcome message
• Confusing 403 with 404 error
• Assuming server error instead of access error

4. Identify the error in this Flask authorization code snippet:

@app.route('/dashboard')
def dashboard():
    if current_user.role = 'admin':
        return 'Admin dashboard'
    else:
        return 'User dashboard'

medium

A. Using '=' instead of '==' in the if condition

B. Missing return statement in else block

C. Incorrect route decorator syntax

D. No error, code is correct

Solution

1. Step 1: Check the if condition syntax

   The condition uses '=' which is assignment, not comparison. It should be '=='.

2. Step 2: Verify other parts of the code

   Else block has a return, route decorator syntax is correct, so no other errors.

3. Final Answer:

   Using '=' instead of '==' in the if condition -> Option A

4. Quick Check:

   Comparison needs '==' not '=' [OK]

Hint: Use '==' for comparisons, '=' is assignment [OK]

Common Mistakes:

• Confusing assignment '=' with comparison '=='
• Assuming missing return in else block
• Thinking route decorator is wrong

5. You want to protect a Flask route so only users with roles 'admin' or 'manager' can access it. Which code correctly implements this authorization check?

@app.route('/reports')
def reports():
    if current_user.role in ['admin', 'manager']:
        return 'Reports page'
    else:
        abort(403)

hard

A. if current_user.role == 'admin' or 'manager':
return 'Reports page'
else:
abort(403)

B. if current_user.role in ['admin', 'manager']:
return 'Reports page'
else:
abort(403)

C. if current_user.role == 'admin' and current_user.role == 'manager':
return 'Reports page'
else:
abort(403)

D. if current_user.role != 'admin' or current_user.role != 'manager':
return 'Reports page'
else:
abort(403)

Solution

1. Step 1: Understand role check for multiple roles

   To allow access for either 'admin' or 'manager', use 'in' with a list of roles.

2. Step 2: Evaluate each option's logic

   if current_user.role in ['admin', 'manager']: return 'Reports page' else: abort(403) correctly uses 'in' to check if role is in the list. if current_user.role == 'admin' or 'manager': return 'Reports page' else: abort(403) always returns true because 'or "manager"' is always truthy. if current_user.role == 'admin' and current_user.role == 'manager': return 'Reports page' else: abort(403) requires role to be both 'admin' and 'manager' simultaneously, impossible. if current_user.role != 'admin' or current_user.role != 'manager': return 'Reports page' else: abort(403) logic is inverted and incorrect.

3. Final Answer:

   if current_user.role in ['admin', 'manager']: return 'Reports page' else: abort(403) -> Option B

4. Quick Check:

   Use 'in' to check multiple roles [OK]

Hint: Use 'in' to check if role is in a list [OK]

Common Mistakes:

• Using 'or' incorrectly causing always true
• Using 'and' requiring impossible dual roles
• Inverting logic with '!=' causing wrong access