Request context in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Flask request context code?

Consider this Flask code snippet that uses the request context to access query parameters. What will be printed when a GET request is made to '/search?q=flask'?

Flask

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

@app.route('/search')
def search():
    return f"Query is: {request.args.get('q')}"

# Assume the server is running and a GET request is made to '/search?q=flask'

A KeyError exception

B Query is: None

C Query is: flask

D Empty string

💡 Hint

Remember that request.args.get('q') fetches the query parameter 'q' from the URL.

The request context allows access to request data like query parameters. Here, 'q=flask' is passed, so request.args.get('q') returns 'flask'.

❓ lifecycle

intermediate

When is the Flask request context available?

In Flask, during which part of the request lifecycle is the request context active and accessible?

A After the response is sent to the client

B Only during the execution of a view function

C Before the server starts

D Only during app initialization

💡 Hint

Think about when Flask processes a request and runs your code.

The request context is pushed before a view function runs and popped after it finishes, so it is only available during the view function execution.

🔧 Debug

advanced

What error occurs if you access 'request' outside a request context?

What happens if you try to access 'flask.request' outside of a request context, for example in a global scope or background thread?

Flask

from flask import request

print(request.method)

A RuntimeError: Working outside of request context.

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

C No error, prints 'GET'

D NameError: name 'request' is not defined

💡 Hint

Flask requires a request context to access request data.

Accessing 'request' outside a request context raises a RuntimeError because Flask cannot find the active request data.

📝 Syntax

advanced

Which code correctly pushes a request context manually?

You want to run code that uses 'request' outside a view function by manually pushing a request context. Which option correctly does this?

Flask

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

with ???:
    print(request.method)

A app.create_request_context('/path')

B app.push_request_context('/path')

C app.request_context('/path')

D app.test_request_context('/path')

💡 Hint

Flask provides a context manager to simulate a request context for testing.

The method 'test_request_context' returns a context manager that pushes a request context for the given path.

🧠 Conceptual

expert

Why does Flask use a request context instead of global variables for request data?

Flask uses a request context to store request-specific data like 'request' and 'session'. Why is this approach better than using global variables?

A Because Flask can handle multiple requests at the same time without data conflicts.

B Because request context makes the code shorter.

C Because global variables cannot store complex data types.

D Because global variables are faster but less secure.

💡 Hint

Think about what happens when many users access the server simultaneously.

Using a request context allows Flask to keep data isolated per request, avoiding conflicts when handling multiple requests concurrently.