Context lifecycle execution in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

Flask request context availability

In a Flask app, what will be the output of this code snippet when accessing the '/' route?

from flask import Flask, request
app = Flask(__name__)

@app.route('/')
def index():
    return f"Method used: {request.method}"

Flask

from flask import Flask, request
app = Flask(__name__)

@app.route('/')
def index():
    return f"Method used: {request.method}"

A Method used: None

B Method used: GET

C RuntimeError: Working outside of request context.

D Method used: POST

💡 Hint

Think about the default HTTP method when you visit a URL in a browser.

When you visit a route in a browser, the HTTP method is GET by default. Flask's request context is active during the route function, so accessing request.method returns 'GET'.

❓ lifecycle

intermediate

Order of Flask context teardown

Which of the following statements correctly describes when Flask's teardown_request functions are called?

A After the response is sent to the client, even if an exception occurred during request handling.

B Before the request function is called, to prepare the context.

C Only if the request function completes without exceptions.

D Only when the Flask app is shutting down.

💡 Hint

Think about cleanup tasks that must run regardless of errors.

teardown_request functions run after the response is returned, even if an error happened, to clean up resources.

🔧 Debug

advanced

Identifying context errors in Flask

What error will this Flask code raise when executed outside a request?

from flask import request
print(request.method)

Flask

from flask import request
print(request.method)

A NameError: name 'request' is not defined

B AttributeError: 'LocalProxy' object has no attribute 'method'

C RuntimeError: Working outside of request context.

D TypeError: 'method' is not callable

💡 Hint

Flask's request object requires an active request context to work.

Accessing request attributes outside a request context raises a RuntimeError indicating the context is missing.

❓ state_output

advanced

Flask application context variable behavior

Given this Flask code, what will be printed?

from flask import Flask, g
app = Flask(__name__)

with app.app_context():
    g.value = 10
    print(g.value)

try:
    print(g.value)
except Exception as e:
    print(type(e).__name__)

Flask

from flask import Flask, g
app = Flask(__name__)

with app.app_context():
    g.value = 10
    print(g.value)

try:
    print(g.value)
except Exception as e:
    print(type(e).__name__)

A

10
RuntimeError

B

10
AttributeError

C

10
10

D

RuntimeError
RuntimeError

💡 Hint

Consider when the application context is active and when it ends.

Inside the app context, g.value is set and printed as 10. Outside, accessing g.value raises RuntimeError because the context ended.

🧠 Conceptual

expert

Understanding Flask context locals

Which statement best explains why Flask uses context locals like request and g instead of global variables?

A To prevent any data from being stored during a request lifecycle.

B To improve performance by caching data globally across all requests.

C To allow global variables to be shared between different Flask apps in the same process.

D To ensure each request has its own separate data, avoiding conflicts in concurrent requests.

💡 Hint

Think about what happens when many users use the app at the same time.

Flask uses context locals to keep data isolated per request, so concurrent users do not interfere with each other's data.