Debug mode error pages in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when Flask debug mode is enabled and an error occurs?

Consider a Flask app running with debug mode enabled. What will the user see if the app raises an unhandled exception during a request?

Flask

from flask import Flask
app = Flask(__name__)
app.debug = True

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

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

A A detailed interactive error page with the traceback and the ability to execute code in the browser.

B The app crashes and stops running immediately.

C The app silently ignores the error and returns a blank page.

D A generic 500 Internal Server Error page with no details shown.

💡 Hint

Debug mode shows detailed error information to help developers fix bugs.

When Flask debug mode is enabled, it shows a detailed interactive error page with the full traceback and a console to run Python code. This helps developers diagnose issues quickly.

📝 Syntax

intermediate

Which code snippet correctly enables debug mode in Flask?

You want to enable debug mode in your Flask app to see detailed error pages during development. Which of the following code snippets correctly enables debug mode?

A

app = Flask(__name__)
app.debug = True
app.run()

B

app = Flask(__name__)
app.run(debug=False)

C

app = Flask(__name__)
app.debug = False
app.run()

D

app = Flask(__name__)
app.run(debug=True)

💡 Hint

The debug parameter in app.run controls debug mode.

Passing debug=True to app.run enables debug mode and shows detailed error pages. Setting app.debug = True alone does not always enable debug mode unless app.run is called accordingly.

🔧 Debug

advanced

What error occurs if you try to enable debug mode in production with Flask's built-in server?

You accidentally run your Flask app with debug=True on a public server. What error or warning will Flask show or raise?

Flask

from flask import Flask
app = Flask(__name__)

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

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

A Warning: Do not use debug mode in production! The server will refuse to start.

B RuntimeError: Debugger PIN required for remote access

C No error; the app runs normally with debug mode enabled on all interfaces.

D ValueError: Host '0.0.0.0' is not allowed with debug mode.

💡 Hint

Flask protects the interactive debugger from remote access with a PIN.

When debug mode is enabled and the app is accessible remotely, Flask requires a PIN to access the debugger to prevent unauthorized access. It raises a RuntimeError if the PIN is not provided.

❓ state_output

advanced

What is the output when Flask debug mode is disabled and an error occurs?

Given this Flask app with debug mode off, what will the user see if an unhandled exception is raised?

Flask

from flask import Flask
app = Flask(__name__)
app.debug = False

@app.route('/')
def index():
    raise Exception('Error!')

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

A The error is ignored and the page loads normally.

B A detailed interactive error page with traceback and debugger.

C A simple 500 Internal Server Error page with no traceback details.

D The app crashes and stops running.

💡 Hint

Without debug mode, Flask hides error details from users.

When debug mode is off, Flask shows a generic 500 error page without any traceback or debugging info to protect sensitive details.

🧠 Conceptual

expert

Why is it unsafe to run Flask with debug mode enabled on a public server?

Select the best explanation for why Flask's debug mode should never be enabled on a public-facing server.

A Because the interactive debugger allows remote code execution, exposing the server to security risks.

B Because debug mode slows down the server significantly, causing performance issues.

C Because debug mode disables HTTPS, making data insecure.

D Because debug mode automatically deletes all user data on errors.

💡 Hint

Think about what the interactive debugger can do if accessed by attackers.

Flask's debug mode includes an interactive debugger that can execute arbitrary Python code. If exposed publicly, attackers can run harmful commands on the server.

Practice

1. What does enabling debug mode in a Flask app do?

easy

A. Disables all error messages

B. Automatically fixes bugs in the code

C. Shows detailed error pages with debugging information

D. Prevents the app from restarting on code changes

Solution

1. Step 1: Understand debug mode purpose

   Debug mode helps developers by showing detailed error pages when something goes wrong.

2. Step 2: Compare options with debug mode behavior

   Only Shows detailed error pages with debugging information correctly describes that debug mode shows detailed error pages with debugging info.

3. Final Answer:

   Shows detailed error pages with debugging information -> Option C

4. Quick Check:

   Debug mode = detailed error pages [OK]

Hint: Debug mode shows detailed errors, not hides them [OK]

Common Mistakes:

• Thinking debug mode hides errors
• Believing debug mode fixes bugs automatically
• Confusing debug mode with production mode

2. Which of the following is the correct way to enable debug mode in Flask?

easy

A. app.run(debug=False)

B. app.debug = True

C. app.debug = False

D. app.config['DEBUG'] = False

Solution

1. Step 1: Recall how to enable debug mode

   Debug mode can be enabled by setting app.debug = True or app.config['DEBUG'] = True.

2. Step 2: Identify the correct option

   Only app.debug = True sets debug mode to True correctly.

3. Final Answer:

   app.debug = True -> Option B

4. Quick Check:

   Enable debug = app.debug = True [OK]

Hint: Set app.debug = True to enable debug mode [OK]

Common Mistakes:

• Setting debug to False instead of True
• Confusing app.run debug argument with app.debug property
• Using incorrect config keys

3. Given this Flask code snippet, what will you see if an error occurs?

from flask import Flask
app = Flask(__name__)
app.debug = True

@app.route('/')
def home():
    return 1 / 0  # This will cause an error

app.run()

medium

A. A detailed error page showing the division by zero traceback

B. A blank page with no error message

C. A generic 500 Internal Server Error page without details

D. The app will crash and stop running

Solution

1. Step 1: Analyze debug mode effect on errors

   With app.debug = True, Flask shows detailed error pages including tracebacks.

2. Step 2: Understand the error in the code

   The route causes a division by zero error, triggering the debug error page.

3. Final Answer:

   A detailed error page showing the division by zero traceback -> Option A

4. Quick Check:

   Debug mode shows detailed error page on exceptions [OK]

Hint: Debug True shows detailed error pages on exceptions [OK]

Common Mistakes:

• Expecting a generic error page in debug mode
• Thinking the app crashes completely
• Assuming no error message is shown

4. What is wrong with this Flask app code if you want to see debug error pages?

from flask import Flask
app = Flask(__name__)
app.config['DEBUG'] = False

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

app.run()

medium

A. Flask apps cannot handle division by zero errors

B. The route function is missing a return statement

C. app.run() is missing the debug=True argument

D. Debug mode is disabled, so detailed error pages won't show

Solution

1. Step 1: Check debug mode setting

   The code sets app.config['DEBUG'] = False, which disables debug mode.

2. Step 2: Understand effect on error pages

   With debug disabled, Flask shows generic error pages, not detailed ones.

3. Final Answer:

   Debug mode is disabled, so detailed error pages won't show -> Option D

4. Quick Check:

   Debug False = no detailed error pages [OK]

Hint: Check if debug is True to get detailed error pages [OK]

Common Mistakes:

• Thinking app.run() debug argument is required if app.config['DEBUG'] is set
• Believing Flask cannot handle division by zero
• Confusing missing return with debug mode issues

5. You want to enable debug mode only during development but disable it in production. Which approach is best?

import os
from flask import Flask
app = Flask(__name__)

if os.getenv('FLASK_ENV') == 'development':
    app.debug = True
else:
    app.debug = False

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

app.run()

hard

A. Use environment variable to toggle debug mode as shown

B. Always set app.debug = True regardless of environment

C. Set app.debug = False and never change it

D. Remove app.debug and rely on app.run(debug=True)

Solution

1. Step 1: Understand environment-based debug control

   Using an environment variable like FLASK_ENV to toggle debug mode is a common and safe practice.

2. Step 2: Evaluate the code logic

   The code sets debug True only if environment is 'development', otherwise disables it, which is correct.

3. Final Answer:

   Use environment variable to toggle debug mode as shown -> Option A

4. Quick Check:

   Env variable controls debug mode safely [OK]

Hint: Use env vars to enable debug only in development [OK]

Common Mistakes:

• Leaving debug always on in production
• Not using environment variables for config
• Relying only on app.run debug argument