Development server with debug mode in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when Flask debug mode is enabled?

Consider a Flask app started with debug mode enabled. What is the main behavior you will observe during development?

Flask

from flask import Flask
app = Flask(__name__)

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

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

A The server disables the debugger and requires manual restarts on code changes.

B The server automatically reloads on code changes and shows detailed error messages in the browser.

C The server runs in production mode with caching enabled.

D The server runs slower but disables all error messages for security.

💡 Hint

Think about what debug mode helps developers do easily.

Debug mode in Flask enables the interactive debugger and automatic reloads when code changes, making development faster and easier.

📝 Syntax

intermediate

Which code correctly enables debug mode in Flask?

Select the code snippet that correctly starts a Flask app with debug mode enabled.

A app.run(debug='True')

B app.run(debug=1)

C app.run(debug='yes')

D app.run(debug=True)

💡 Hint

Debug expects a boolean value, not a string.

The debug parameter expects a boolean True or False. Passing a string or integer may not work as intended.

🔧 Debug

advanced

What error occurs if you run Flask with debug=True but forget to set __name__ == '__main__'?

Given this code snippet, what error or behavior will occur? from flask import Flask app = Flask(__name__) @app.route('/') def home(): return 'Hi' app.run(debug=True)

Flask

from flask import Flask
app = Flask(__name__)

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

app.run(debug=True)

A RuntimeError: The server is running but debug mode causes multiple reloads and crashes.

B The server starts but immediately crashes with RuntimeError about working outside the main thread.

C The server starts but runs the app twice due to the reloader causing duplicate output.

D The server starts normally but debug mode is ignored and no auto-reload happens.

💡 Hint

Think about how Flask's reloader works when not protected by the main guard.

Without the if __name__ == '__main__' guard, the app.run(debug=True) causes the reloader to spawn a child process, running the code twice.

❓ state_output

advanced

What is the output when Flask debug mode triggers an error in a route?

If a route function raises an exception while Flask is running with debug=True, what will the user see in the browser?

Flask

from flask import Flask
app = Flask(__name__)

@app.route('/')
def home():
    raise ValueError('Oops!')

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

A A detailed interactive debugger page showing the error and stack trace.

B A plain 500 Internal Server Error page with no details.

C The browser shows a blank page with no response.

D The server crashes and stops running immediately.

💡 Hint

Debug mode helps developers see what went wrong directly in the browser.

With debug=True, Flask shows an interactive debugger with error details and stack trace in the browser when exceptions occur.

🧠 Conceptual

expert

Why should Flask debug mode never be enabled in production?

Select the best reason why running Flask with debug=True is unsafe in a production environment.

A Debug mode enables an interactive debugger that can execute arbitrary code, exposing the server to attacks.

B Debug mode disables all security features, allowing anyone to access the server files.

C Debug mode slows down the server drastically, causing denial of service.

D Debug mode automatically deletes logs and user data after each request.

💡 Hint

Think about what the interactive debugger allows a user to do.

The interactive debugger allows code execution from the browser, which is a major security risk if exposed publicly.

Practice

1. What does setting debug=True in app.run() do in a Flask app?

easy

A. It hides all error messages from the user.

B. It disables the server from running.

C. It makes the app run faster in production.

D. It shows detailed error messages and reloads the server on code changes.

Solution

1. Step 1: Understand debug mode purpose

   Debug mode helps developers by showing detailed error messages and automatically restarting the server when code changes.

2. Step 2: Check what debug=True does in app.run()

   Passing debug=True enables this helpful behavior during development.

3. Final Answer:

   It shows detailed error messages and reloads the server on code changes. -> Option D

4. Quick Check:

   Debug mode = detailed errors + auto reload [OK]

Hint: Debug mode shows errors and reloads automatically [OK]

Common Mistakes:

• Thinking debug mode speeds up production
• Believing debug mode hides errors
• Confusing debug mode with disabling the server

2. Which of the following is the correct way to start a Flask development server with debug mode enabled?

easy

A. app.run(debug=True)

B. app.run(debug=1)

C. app.run(mode='debug')

D. app.run(enable_debug=True)

Solution

1. Step 1: Recall Flask run method parameters

   The app.run() method accepts a debug parameter as a boolean to enable debug mode.

2. Step 2: Identify correct syntax

   Using app.run(debug=True) is the standard and correct way to enable debug mode.

3. Final Answer:

   app.run(debug=True) -> Option A

4. Quick Check:

   Correct debug syntax = debug=True [OK]

Hint: Use debug=True exactly in app.run() [OK]

Common Mistakes:

• Using incorrect parameter names like mode or enable_debug
• Passing debug as a string or number instead of boolean
• Confusing debug with other run parameters

3. What will happen when you run this Flask code?

from flask import Flask
app = Flask(__name__)

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

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

medium

A. The server will not start because the route is missing a template.

B. The server starts but debug mode is off, so no error details are shown.

C. The server starts with debug mode, showing errors and auto-reloading on code changes.

D. The code will raise a syntax error because debug=True is invalid here.

Solution

1. Step 1: Analyze the code structure

   The code defines a Flask app with a simple route returning 'Hello!'. The server is started with debug=True.

2. Step 2: Understand effect of debug=True

   Passing debug=True enables debug mode, so errors show detailed info and the server reloads on code changes.

3. Final Answer:

   The server starts with debug mode, showing errors and auto-reloading on code changes. -> Option C

4. Quick Check:

   app.run(debug=True) = debug mode active [OK]

Hint: debug=True means errors show and server reloads [OK]

Common Mistakes:

• Thinking debug=True causes syntax errors
• Assuming debug mode is off by default
• Believing routes need templates to start server

4. You wrote this code but the Flask server does not reload on code changes:

from flask import Flask
app = Flask(__name__)

@app.route('/')
def index():
    return 'Hi'

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

What is the likely fix?

medium

A. Change app = Flask(__name__) to app = Flask().

B. Add debug=True to app.run() to enable auto-reload.

C. Add reload=True parameter to app.run().

D. Remove the if __name__ == '__main__' guard.

Solution

1. Step 1: Identify missing debug mode

   The code calls app.run() without debug=True, so debug mode and auto-reload are off.

2. Step 2: Enable debug mode for auto-reload

   Adding debug=True to app.run() activates debug mode, enabling error messages and auto-reload on code changes.

3. Final Answer:

   Add debug=True to app.run() to enable auto-reload. -> Option B

4. Quick Check:

   Missing debug=True disables auto-reload [OK]

Hint: Add debug=True to app.run() for auto-reload [OK]

Common Mistakes:

• Trying to use reload=True which is invalid
• Removing the main guard which is unrelated
• Changing Flask app initialization unnecessarily

5. You want to run your Flask app with debug mode but only on your local machine, not in production. Which code snippet correctly achieves this?

hard

A. if __name__ == '__main__':
app.run(debug=True)

B. app.run(debug=True) # runs debug mode always

C. if __name__ == '__main__':
app.run() # debug mode off

D. app.run() # debug mode on by default

Solution

1. Step 1: Understand the main guard usage

   The if __name__ == '__main__' block ensures the server runs only when the script is executed directly, typically local development.

2. Step 2: Enable debug mode only inside main guard

   Placing app.run(debug=True) inside this block enables debug mode only locally, avoiding debug mode in production.

3. Step 3: Check other options

   Running app.run(debug=True) outside the guard runs debug mode always, which is unsafe for production.

4. Final Answer:

   if __name__ == '__main__': app.run(debug=True) -> Option A

5. Quick Check:

   Main guard + debug=True = safe local debug [OK]

Hint: Use main guard with debug=True for local only [OK]

Common Mistakes:

• Running debug mode outside main guard risks production
• Assuming debug mode is off by default
• Not using main guard and causing unwanted server start