WSGI concept overview in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main role of WSGI in a Flask application?

WSGI is a key part of how Flask works. What does WSGI do in a Flask app?

A It stores the application's data in a database automatically.

B It provides a graphical user interface for the Flask app.

C It acts as a bridge between the web server and the Flask application, handling requests and responses.

D It compiles Python code into machine code for faster execution.

💡 Hint

Think about how the web server talks to your Flask code.

WSGI stands for Web Server Gateway Interface. It connects the web server to the Flask app, letting them communicate by passing requests and responses.

❓ component_behavior

intermediate

What output does this Flask WSGI app produce when accessed?

Consider this simple Flask app code. What will the browser show when you visit the root URL?

Flask

from flask import Flask
app = Flask(__name__)

@app.route('/')
def home():
    return 'Hello from WSGI!'

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

A Hello from WSGI!

B 404 Not Found

C 500 Internal Server Error

D Flask app running

💡 Hint

Look at the route and the return value of the function.

The route '/' is linked to the function home(), which returns the string 'Hello from WSGI!'. Flask sends this string as the response body.

❓ lifecycle

advanced

Which step correctly describes the WSGI request handling lifecycle in Flask?

Put these steps in the correct order for how WSGI handles a request in Flask.

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,2,1,4

💡 Hint

Think about the flow from client to server and back.

The web server first gets the request, then WSGI passes it to Flask. Flask processes and returns a response, which WSGI sends back through the web server to the client.

📝 Syntax

advanced

What error does this WSGI Flask app code produce when run?

Examine this Flask app snippet. What error will it raise?

Flask

from flask import Flask
app = Flask(__name__)

@app.route('/')
def home():
    return 'Hello WSGI!'

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

A TypeError

B IndentationError

C NameError

D No error, runs fine

💡 Hint

Check the indentation of the function body.

The return statement inside the function is not indented properly, causing an IndentationError.

🔧 Debug

expert

Why does this Flask WSGI app return a 500 error on request?

Look at this Flask app code. When accessed, it returns a 500 Internal Server Error. What is the cause?

Flask

from flask import Flask
app = Flask(__name__)

@app.route('/')
def home():
    return undefined_variable

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

A The app.run() call is outside the main guard.

B The route decorator is missing parentheses.

C Flask app is missing the secret key configuration.

D The variable 'undefined_variable' is not defined, causing a NameError.

💡 Hint

Check the return statement inside the route function.

The function tries to return a variable that does not exist, causing a NameError and resulting in a 500 error response.

Practice

1. What is the main role of WSGI in a Flask web application?

easy

A. It acts as a bridge between the web server and the Python application.

B. It stores the application's database connections.

C. It manages user sessions and cookies.

D. It handles the frontend HTML and CSS rendering.

Solution

1. Step 1: Understand WSGI's purpose

   WSGI stands for Web Server Gateway Interface and connects web servers with Python apps.

2. Step 2: Identify WSGI's role in Flask

   Flask apps use WSGI to receive requests from servers and send responses back.

3. Final Answer:

   It acts as a bridge between the web server and the Python application. -> Option A

4. Quick Check:

   WSGI = bridge between server and app [OK]

Hint: WSGI connects server and Python app like a translator [OK]

Common Mistakes:

• Confusing WSGI with frontend rendering
• Thinking WSGI manages databases
• Assuming WSGI handles user sessions

2. Which of the following is the correct signature of a WSGI application callable?

easy

A. def app(request, response):

B. def app():

C. def app(request):

D. def app(environ, start_response):

Solution

1. Step 1: Recall WSGI callable signature

   A WSGI app is a function that takes two arguments: environ and start_response.

2. Step 2: Match the correct function signature

   Only def app(environ, start_response): matches the required parameters for a WSGI callable.

3. Final Answer:

   def app(environ, start_response): -> Option D

4. Quick Check:

   WSGI callable = (environ, start_response) [OK]

Hint: WSGI apps always take environ and start_response [OK]

Common Mistakes:

• Using request and response instead of environ and start_response
• Missing one or both parameters
• Defining a function with no parameters

3. Given this WSGI app snippet, what will be the response body sent to the client?

def app(environ, start_response):
    start_response('200 OK', [('Content-Type', 'text/plain')])
    return [b'Hello, WSGI!']

medium

A. An empty response with status 200

B. A server error due to missing return type

C. The text 'Hello, WSGI!' displayed in the browser

D. A response with HTML content

Solution

1. Step 1: Analyze start_response call

   The status is '200 OK' and content type is 'text/plain', so plain text will be sent.

2. Step 2: Check the return value

   The app returns a list with a byte string containing 'Hello, WSGI!'. This is the response body.

3. Final Answer:

   The text 'Hello, WSGI!' displayed in the browser -> Option C

4. Quick Check:

   Return byte string with 'Hello, WSGI!' = The text 'Hello, WSGI!' displayed in the browser [OK]

Hint: Return a byte string list for response body in WSGI [OK]

Common Mistakes:

• Returning a string instead of bytes
• Not calling start_response before returning
• Expecting HTML content without setting content-type

4. Identify the error in this WSGI application code:

def app(environ, start_response):
    start_response('200 OK')
    return [b'Hello']

medium

A. The function should not take any parameters.

B. Missing the headers argument in start_response call.

C. The return value should be a string, not bytes.

D. start_response should be called after returning the response.

Solution

1. Step 1: Check start_response usage

   start_response requires two arguments: status and headers list. Here headers are missing.

2. Step 2: Validate return type and function signature

   Return type is correct as a list of bytes, and parameters are correct.

3. Final Answer:

   Missing the headers argument in start_response call. -> Option B

4. Quick Check:

   start_response needs headers list [OK]

Hint: start_response needs status and headers list [OK]

Common Mistakes:

• Omitting headers argument in start_response
• Returning string instead of bytes
• Calling start_response after return

5. You want to create a WSGI app that returns 'Welcome!' only if the URL path is '/home', otherwise returns 'Not Found' with status 404. Which code correctly implements this?

hard

A. def app(environ, start_response):
if environ['PATH_INFO'] == '/home':
start_response('200 OK', [('Content-Type', 'text/plain')])
return [b'Welcome!']
else:
start_response('404 Not Found', [('Content-Type', 'text/plain')])
return [b'Not Found']

B. def app(environ, start_response):
if environ['PATH_INFO'] == '/home':
return [b'Welcome!']
else:
start_response('404 Not Found', [('Content-Type', 'text/plain')])
return [b'Not Found']

C. def app(environ, start_response):
start_response('200 OK', [('Content-Type', 'text/plain')])
return [b'Welcome!']

D. def app(environ, start_response):
start_response('404 Not Found')
return [b'Not Found']

Solution

1. Step 1: Check URL path handling

   Use environ['PATH_INFO'] to check the requested path; only '/home' returns 'Welcome!'.

2. Step 2: Verify start_response calls and return values

   Both cases call start_response with correct status and headers, and return byte strings in a list.

3. Final Answer:

   The code that checks environ['PATH_INFO'] == '/home' and calls start_response in both branches. -> Option A

4. Quick Check:

   Check PATH_INFO and call start_response properly [OK]

Hint: Always call start_response before returning response [OK]

Common Mistakes:

• Not calling start_response in all branches
• Returning bytes without start_response
• Ignoring PATH_INFO for routing