Blueprint best practices in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

Blueprint URL Prefix Behavior

Consider a Flask Blueprint registered with a URL prefix. What will be the full URL path for a route defined as @bp.route('/dashboard') if the blueprint is registered with url_prefix='/admin'?

Flask

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

@bp.route('/dashboard')
def dashboard():
    return 'Admin Dashboard'

A /admin/dashboard

B /dashboard

C /admin

D /dashboard/admin

💡 Hint

Think about how the url_prefix combines with route paths.

The url_prefix is prepended to all routes in the blueprint. So the route /dashboard becomes /admin/dashboard.

📝 Syntax

intermediate

Correct Blueprint Registration Syntax

Which option correctly registers a blueprint named auth in a Flask app instance app?

Flask

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

# Registration code here

A app.register_blueprint(auth)

B app.register_blueprint('auth')

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

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

💡 Hint

The first argument must be the blueprint object, not a string.

The register_blueprint method requires the blueprint object as the first argument. Option C correctly passes the blueprint and adds a URL prefix.

🔧 Debug

advanced

Blueprint Import Error Debugging

You have a Flask app with multiple blueprints in separate files. When running the app, you get an ImportError related to circular imports. What is the best practice to avoid this issue?

Flask

File structure:
- app.py
- auth.py (defines auth blueprint)
- dashboard.py (defines dashboard blueprint)

Both auth.py and dashboard.py import app.py and each other.

A Import blueprints inside functions or after app creation to avoid circular imports.

B Remove all imports between blueprint files and put all routes in app.py.

C Use global variables to share app instance across files.

D Rename blueprint files to avoid import conflicts.

💡 Hint

Think about when imports happen and how to delay them.

Delaying imports until after app creation or inside functions helps break circular import chains. This is a common best practice in Flask blueprint organization.

❓ state_output

advanced

Blueprint Template Folder Resolution

If a blueprint is created with Blueprint('shop', __name__, template_folder='templates') and the app renders a template with render_template('index.html') inside a blueprint route, where does Flask look for index.html?

Flask

shop = Blueprint('shop', __name__, template_folder='templates')

@shop.route('/')
def home():
    return render_template('index.html')

A In the app's main templates folder only.

B In both the app's templates folder and blueprint's templates folder, app folder takes priority.

C Flask raises a TemplateNotFound error because path is ambiguous.

D In the blueprint's 'templates' folder relative to the blueprint file.

💡 Hint

Blueprints can have their own templates folder.

When a blueprint has a template_folder set, Flask looks inside that folder relative to the blueprint's location for templates used in that blueprint's routes.

🧠 Conceptual

expert

Blueprints and Application Factory Pattern

Why is it a best practice to register blueprints inside the application factory function rather than at the global level in a Flask app?

A It prevents blueprints from being used outside the app context.

B It allows creating multiple app instances with different configurations and avoids circular imports.

C It automatically registers blueprints with URL prefixes without extra code.

D It improves the app's runtime speed by preloading blueprints.

💡 Hint

Think about app creation and flexibility.

Registering blueprints inside the factory function allows creating multiple app instances with different settings and helps avoid circular import problems by delaying registration until app creation.