Why error handling matters in Flask - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Flask class.

Flask

from flask import [1]
app = [1](__name__)

Drag options to blanks, or click blank then click option'

Ajsonify

BFlask

Crender_template

DRequest

Attempts:

3 left

💡 Hint

Common Mistakes

Importing Request instead of Flask

Using jsonify as the app class

The Flask class is imported to create the app instance.

2fill in blank

medium

Complete the code to define a route that returns a simple message.

Flask

@app.route('/')
def home():
    return [1]

Drag options to blanks, or click blank then click option'

AHello World!

Bjsonify(message='Hello World!')

Crender_template('index.html')

D'Hello World!'

Attempts:

3 left

💡 Hint

Common Mistakes

Returning unquoted text

Returning a function call instead of string

The return value must be a string, so it needs quotes.

3fill in blank

hard

Fix the error in the code to handle a 404 error with a custom message.

Flask

@app.errorhandler([1])
def not_found(error):
    return 'Page not found', 404

Drag options to blanks, or click blank then click option'

A404

B403

C500

D400

Attempts:

3 left

💡 Hint

Common Mistakes

Using 500 for server error instead of 404

Using 403 for forbidden

404 is the HTTP status code for 'Not Found'.

4fill in blank

hard

Fill in the blank to create a route that raises a 404 error manually.

Flask

from flask import abort

@app.route('/secret')
def secret():
    [1](404)
    return 'This is a secret page.'

Drag options to blanks, or click blank then click option'

Aabort

Breturn

Craise

Dprint

Attempts:

3 left

💡 Hint

Common Mistakes

Using raise instead of abort

Using return to send error code

The abort function is used to raise HTTP errors in Flask.

5fill in blank

hard

Fill all three blanks to handle errors and return JSON with error info.

Flask

from flask import jsonify

@app.errorhandler([1])
def handle_error(error):
    response = jsonify({'error': str(error)})
    response.status_code = [2]
    return [3]

Drag options to blanks, or click blank then click option'

A404

Bresponse

Cerror.code

D500

Attempts:

3 left

💡 Hint

Common Mistakes

Hardcoding status code incorrectly

Returning error instead of response

The handler catches 404 errors, sets the response code from error.code, and returns the response object.

Practice

1. Why is error handling important in a Flask web application?

easy

A. It hides all errors so developers never see them.

B. It makes the app run faster by skipping checks.

C. It keeps the app stable and shows helpful messages to users.

D. It automatically fixes bugs without developer input.

Solution

1. Step 1: Understand the role of error handling

   Error handling helps prevent the app from crashing and manages unexpected problems gracefully.

2. Step 2: Recognize user experience benefits

   Showing clear messages helps users understand what went wrong instead of seeing confusing errors.

3. Final Answer:

   It keeps the app stable and shows helpful messages to users. -> Option C

4. Quick Check:

   Error handling importance = Stability and clarity [OK]

Hint: Error handling = stability + user clarity [OK]

Common Mistakes:

• Thinking error handling speeds up the app
• Believing errors should be hidden from developers
• Assuming errors fix themselves automatically

2. Which of the following is the correct way to define a custom error handler for 404 errors in Flask?

easy

A. @app.errorhandler(404)\ndef not_found(error):\n return 'Page not found', 404

B. @app.route('/404')\ndef not_found():\n return 'Page not found', 404

C. @app.handle_error(404)\ndef not_found():\n return 'Page not found', 404

D. @app.error(404)\ndef not_found(error):\n return 'Page not found', 404

Solution

1. Step 1: Recall Flask error handler syntax

   Flask uses @app.errorhandler(code) decorator to catch errors by status code.

2. Step 2: Check function signature

   The handler function must accept an error argument to receive error info.

3. Final Answer:

   @app.errorhandler(404)\ndef not_found(error):\n return 'Page not found', 404 -> Option A

4. Quick Check:

   Correct decorator and function signature = @app.errorhandler(404)\ndef not_found(error):\n return 'Page not found', 404 [OK]

Hint: Use @app.errorhandler with error param [OK]

Common Mistakes:

• Using @app.route instead of @app.errorhandler
• Missing the error parameter in handler function
• Using incorrect decorator names like @app.handle_error

3. What will be the output when accessing a missing page if this Flask code is used?

@app.errorhandler(404)
def page_not_found(error):
    return 'Oops! Page missing.', 404

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

medium

A. Oops! Page missing.

B. 404 Not Found default Flask page

C. Internal Server Error

D. Welcome!

Solution

1. Step 1: Identify error handler for 404

   The code defines a custom 404 error handler returning 'Oops! Page missing.' with status 404.

2. Step 2: Understand request to missing page

   Accessing a missing page triggers 404, so Flask calls the custom handler instead of default page.

3. Final Answer:

   Oops! Page missing. -> Option A

4. Quick Check:

   Custom 404 handler output = 'Oops! Page missing.' [OK]

Hint: Custom 404 handler output replaces default page [OK]

Common Mistakes:

• Expecting default Flask 404 page instead of custom message
• Confusing home route output with missing page output
• Assuming server error occurs on missing page

4. Identify the error in this Flask error handler code:

@app.errorhandler(500)
def internal_error():
    return 'Server error occurred', 500

medium

A. Function name must be 'handle_500_error'.

B. Incorrect decorator name; should be @app.handle_error.

C. Return statement should not include status code.

D. Missing error parameter in the handler function.

Solution

1. Step 1: Check error handler function signature

   Flask error handlers must accept an error argument to receive error info.

2. Step 2: Verify decorator correctness

   The decorator @app.errorhandler(500) is correct; function name can be anything.

3. Final Answer:

   Missing error parameter in the handler function. -> Option D

4. Quick Check:

   Error handler needs error param = Missing error parameter in the handler function. [OK]

Hint: Error handlers need an error argument [OK]

Common Mistakes:

• Omitting the error parameter in handler function
• Using wrong decorator names
• Thinking function name is fixed

5. You want to show a custom message for both 404 and 500 errors in your Flask app. Which approach correctly handles both errors without repeating code?

hard

A. Define two separate handlers with identical code for 404 and 500 errors.

B. Use a single function and register it twice with @app.errorhandler(404) and @app.errorhandler(500).

C. Use @app.route for 404 and @app.errorhandler for 500 errors.

D. Handle errors only in the main route function with try-except blocks.

Solution

1. Step 1: Understand code reuse for error handlers

   To avoid repeating code, one function can handle multiple error codes by registering it multiple times.

2. Step 2: Check Flask syntax for multiple error handlers

   Flask allows decorating the same function multiple times with different error codes.

3. Final Answer:

   Use a single function and register it twice with @app.errorhandler(404) and @app.errorhandler(500). -> Option B

4. Quick Check:

   One function, multiple decorators = Use a single function and register it twice with @app.errorhandler(404) and @app.errorhandler(500). [OK]

Hint: Register one function with multiple @app.errorhandler decorators [OK]

Common Mistakes:

• Writing duplicate code in separate handlers
• Using @app.route for error handling
• Trying to catch errors only inside routes