Testing forms and POST data in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output when submitting a POST form in Flask?

Consider this Flask route handling a POST form submission:

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

@app.route('/submit', methods=['POST'])
def submit():
    name = request.form.get('name', 'Guest')
    return f'Hello, {name}!'

If a form sends name=Alice in the POST data, what will the response be?

Flask

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

@app.route('/submit', methods=['POST'])
def submit():
    name = request.form.get('name', 'Guest')
    return f'Hello, {name}!'

A Hello, Guest!

B Hello, Alice!

C Error: Missing name

D Hello, None!

💡 Hint

Check how request.form.get works with the given key.

The request.form.get('name', 'Guest') fetches the value of 'name' from the POST data. Since the form sends name=Alice, it returns 'Alice'. So the response is 'Hello, Alice!'.

📝 Syntax

intermediate

Which Flask route decorator correctly accepts POST data?

Which of the following route decorators correctly allows a Flask route to accept POST requests?

A @app.route('/data', methods=['POST'])

B @app.route('/data', method='POST')

C @app.route('/data', methods='POST')

D @app.route('/data', post=True)

💡 Hint

Look at the correct parameter name and its expected type for methods.

The methods parameter expects a list of HTTP methods. So methods=['POST'] is correct. Other options have wrong parameter names or types.

🔧 Debug

advanced

Why does this Flask POST handler raise a KeyError?

Given this Flask route:

@app.route('/login', methods=['POST'])
def login():
    username = request.form['username']
    return f'User: {username}'

When a POST request is sent without the 'username' field, what error occurs and why?

Flask

@app.route('/login', methods=['POST'])
def login():
    username = request.form['username']
    return f'User: {username}'

A ValueError because username is empty string

B TypeError because request.form is not a dict

C No error, returns 'User: None'

D KeyError because 'username' is missing in form data

💡 Hint

Accessing a missing key in a dictionary-like object raises which error?

Using request.form['username'] tries to get the key directly. If the key is missing, it raises a KeyError. To avoid this, use request.form.get('username').

❓ state_output

advanced

What is the value of 'count' after multiple POST requests?

Consider this Flask app snippet:

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

@app.route('/increment', methods=['POST'])
def increment():
    global count
    count += 1
    return str(count)

If three POST requests are sent sequentially to '/increment', what will be the response to the third request?

Flask

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

@app.route('/increment', methods=['POST'])
def increment():
    global count
    count += 1
    return str(count)

A Error: count is not defined

B 0

C 3

D 1

💡 Hint

Think about how global variables behave across requests in a running Flask app.

The variable count is global and increments by 1 on each POST request. After three requests, it will be 3.

🧠 Conceptual

expert

Why is using global variables for POST data state problematic in Flask?

In a Flask app, why is it generally a bad idea to use global variables to store data from POST requests for tracking user state?

A Because Flask runs multiple threads or processes, global variables may not be shared or synchronized, causing inconsistent state

B Because global variables automatically reset after each POST request

C Because POST data cannot be accessed inside functions using global variables

D Because global variables cause syntax errors in Flask routes handling POST data

💡 Hint

Consider how Flask handles multiple users and requests in production.

Flask apps often run with multiple threads or processes. Global variables are local to each process and not synchronized, so using them to store user state can cause inconsistent or lost data. Proper state management uses sessions or databases.