Blueprint best practices in Flask - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Flask blueprint named 'auth'.

Flask

from flask import Blueprint

auth = Blueprint('[1]', __name__)

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

Aauth

Bapp

Cmain

Duser

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different name than the variable name causes confusion.

Leaving the name blank or misspelled.

The blueprint name should be 'auth' to match the variable name and purpose.

2fill in blank

medium

Complete the code to register the 'auth' blueprint with the Flask app.

Flask

from flask import Flask
app = Flask(__name__)

app.[1](auth, url_prefix='/auth')

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

Aregister_blueprint

Battach_blueprint

Cinclude_blueprint

Dadd_blueprint

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-existent method like 'add_blueprint'.

Forgetting to register the blueprint causes routes not to work.

Use register_blueprint to add a blueprint to the Flask app.

3fill in blank

hard

Fix the error in the blueprint route definition to return 'Hello Auth!'.

Flask

from flask import Blueprint

auth = Blueprint('auth', __name__)

@auth.route('/hello')
def [1]():
    return 'Hello Auth!'

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

Aauth

Bhello

Cindex

Dhome

Attempts:

3 left

💡 Hint

Common Mistakes

Using a function name unrelated to the route can confuse readers.

Leaving the function name blank or using reserved words.

The function name should match the route handler, here 'hello' matches the route '/hello'.

4fill in blank

hard

Fill both blanks to create a blueprint with a URL prefix and import it in the app.

Flask

from flask import Flask
from [1] import auth

app = Flask(__name__)
app.[2](auth, url_prefix='/auth')

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

Aauth_blueprint

Bregister_blueprint

Cblueprints

Dadd_blueprint

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong module names or method names.

Forgetting the URL prefix when registering the blueprint.

Import the blueprint from the module named 'blueprints' and register it with register_blueprint.

5fill in blank

hard

Fill all three blanks to define a blueprint, add a route, and register it with the app.

Flask

from flask import Flask, Blueprint

app = Flask(__name__)

api = Blueprint('[1]', __name__)

@api.route('/status')
def [2]():
    return 'API is running'

app.[3](api, url_prefix='/api')

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

Aapi

Bstatus

Cregister_blueprint

Drun

Attempts:

3 left

💡 Hint

Common Mistakes

Using inconsistent names for blueprint and variable.

Using wrong method to register the blueprint.

Naming the route function unrelated to the route.

The blueprint is named 'api', the route function is 'status', and the blueprint is registered with register_blueprint.

Practice

1. What is the main purpose of using a Blueprint in a Flask application?

easy

A. To organize routes and views into reusable components

B. To connect Flask with a database

C. To handle user authentication automatically

D. To serve static files like images and CSS

Solution

1. Step 1: Understand Blueprint role

   A Blueprint helps split a Flask app into smaller parts for better organization.

2. Step 2: Compare options

   Only To organize routes and views into reusable components describes organizing routes and views, which is the Blueprint's purpose.

3. Final Answer:

   To organize routes and views into reusable components -> Option A

4. Quick Check:

   Blueprint = organize routes [OK]

Hint: Blueprints group routes for modular apps [OK]

Common Mistakes:

• Confusing Blueprints with database connectors
• Thinking Blueprints handle authentication
• Assuming Blueprints serve static files

2. Which of the following is the correct way to register a Blueprint named auth with a URL prefix /auth in a Flask app?

easy

A. auth.register_blueprint(app, url_prefix='/auth')

B. app.register_blueprint('/auth', auth)

C. app.add_blueprint(auth, prefix='/auth')

D. app.register_blueprint(auth, url_prefix='/auth')

Solution

1. Step 1: Recall Blueprint registration syntax

   The correct method is app.register_blueprint(blueprint, url_prefix='...').

2. Step 2: Match options

   Only app.register_blueprint(auth, url_prefix='/auth') uses the correct method and argument order.

3. Final Answer:

   app.register_blueprint(auth, url_prefix='/auth') -> Option D

4. Quick Check:

   Register Blueprint with url_prefix = C [OK]

Hint: Use app.register_blueprint(blueprint, url_prefix=...) [OK]

Common Mistakes:

• Swapping argument order in register_blueprint
• Using non-existent methods like add_blueprint
• Calling register_blueprint on the Blueprint instead of app

3. Given this Blueprint code:

from flask import Blueprint
bp = Blueprint('bp', __name__, url_prefix='/items')

@bp.route('/')
def list_items():
    return 'List of items'

What URL path will show the text 'List of items' when this Blueprint is registered with app.register_blueprint(bp)?

medium

A. /bp/

B. /

C. /items/

D. /items/list_items

Solution

1. Step 1: Understand url_prefix effect

   The Blueprint has url_prefix='/items', so all routes start with '/items'.

2. Step 2: Check route decorator

   The route is @bp.route('/'), so it adds '/' after the prefix.

3. Final Answer:

   /items/ -> Option C

4. Quick Check:

   url_prefix + route = /items/ [OK]

Hint: URL = url_prefix + route path [OK]

Common Mistakes:

• Ignoring url_prefix and using route path alone
• Using Blueprint name as URL prefix
• Assuming function name affects URL path

4. What is wrong with this Blueprint registration code?

from flask import Flask, Blueprint
app = Flask(__name__)
bp = Blueprint('bp', __name__)

@bp.route('/hello')
def hello():
    return 'Hello!'

app.register_blueprint(bp, url_prefix='/greet')

if __name__ == '__main__':
    app.run()

medium

A. Nothing is wrong; the code works correctly

B. The Blueprint must be registered before defining routes

C. The url_prefix argument is invalid for register_blueprint

D. The Blueprint name 'bp' conflicts with the app name

Solution

1. Step 1: Check Blueprint usage

   The Blueprint is created, routes defined, then registered with url_prefix correctly.

2. Step 2: Validate code correctness

   All syntax and order are valid; no conflicts or errors exist.

3. Final Answer:

   Nothing is wrong; the code works correctly -> Option A

4. Quick Check:

   Blueprint registration order and syntax = correct [OK]

Hint: Define routes before registering Blueprint [OK]

Common Mistakes:

• Trying to register Blueprint before defining routes
• Misusing url_prefix argument
• Assuming Blueprint name conflicts with app

5. You have two Blueprints, admin_bp with url_prefix='/admin' and user_bp with url_prefix='/user'. Both define a route @bp.route('/dashboard'). What is the best practice to avoid URL conflicts and keep your app organized?

hard

A. Merge both Blueprints into one to avoid route duplication

B. Use distinct url_prefixes for each Blueprint and register both in the main app

C. Remove url_prefix and use unique route names instead

D. Register only one Blueprint to prevent conflicts

Solution

1. Step 1: Understand route conflicts

   Both Blueprints have the same route path '/dashboard', which would conflict if url_prefixes overlap or are missing.

2. Step 2: Use url_prefix to separate routes

   Assigning distinct url_prefixes like '/admin' and '/user' keeps routes separate and organized.

3. Step 3: Register both Blueprints in main app

   Registering both with their prefixes activates their routes without conflict.

4. Final Answer:

   Use distinct url_prefixes for each Blueprint and register both in the main app -> Option B

5. Quick Check:

   Distinct url_prefixes prevent route conflicts [OK]

Hint: Separate routes with unique url_prefixes [OK]

Common Mistakes:

• Merging Blueprints unnecessarily
• Removing url_prefix causing route clashes
• Registering only one Blueprint losing functionality