Why production readiness matters in FastAPI - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a basic FastAPI app instance.

FastAPI

from fastapi import [1]

app = [1]()

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

AFastAPI

BRequest

CResponse

DDepends

Attempts:

3 left

💡 Hint

Common Mistakes

Importing Request or Response instead of FastAPI.

Forgetting to add parentheses when creating the app instance.

The FastAPI class is used to create the app instance. This is the starting point for any FastAPI application.

2fill in blank

medium

Complete the code to define a GET endpoint that returns a welcome message.

FastAPI

@app.[1]("/")
async def read_root():
    return {"message": "Welcome to production-ready FastAPI!"}

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

Aget

Bpost

Cput

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Using POST or PUT instead of GET for a simple read endpoint.

Misspelling the decorator name.

The @app.get decorator defines a GET HTTP method endpoint. This is used to read or fetch data.

3fill in blank

hard

Fix the error in the code to correctly run the FastAPI app with Uvicorn.

FastAPI

import uvicorn

if __name__ == "__main__":
    uvicorn.run("main:[1]", host="127.0.0.1", port=8000, reload=True)

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

Aapp_instance

Bapplication

Capp

Dserver

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong app instance name that does not exist.

Forgetting the colon between module and app name.

The string passed to uvicorn.run should be the module name and the FastAPI app instance name separated by a colon. Usually, the app instance is named app.

4fill in blank

hard

Fill both blanks to add middleware that logs requests and responses.

FastAPI

from fastapi.middleware.[1] import [2]

app.add_middleware([2])

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

Alogging

Bcors

CLoggerMiddleware

DCORSMiddleware

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing CORS middleware with logging middleware.

Using middleware class names that don't exist in FastAPI.

Middleware for logging requests is often custom or named LoggerMiddleware. The import path includes 'logging' for this example.

5fill in blank

hard

Fill all three blanks to create a dependency that checks an API key in headers.

FastAPI

from fastapi import Header, HTTPException, [1]

async def verify_api_key(api_key: str = [2](alias="X-API-Key")):
    if api_key != "secret123":
        raise [3](status_code=401, detail="Invalid API Key")

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

ADepends

BHeader

CHTTPException

DRequest

Attempts:

3 left

💡 Hint

Common Mistakes

Using Request instead of Depends for dependency injection.

Not raising HTTPException for unauthorized access.

Dependencies in FastAPI use Depends. The API key is extracted from headers using Header. If invalid, an HTTPException is raised.

Practice

1. Why is production readiness important for a FastAPI application?

easy

A. To allow the app to run only on local machines

B. To make the app look visually appealing

C. To reduce the size of the app's source code

D. To ensure the app runs safely, quickly, and reliably for users

Solution

1. Step 1: Understand the purpose of production readiness

   Production readiness focuses on making an app safe, fast, and reliable for real users.

2. Step 2: Compare options with this purpose

   Only To ensure the app runs safely, quickly, and reliably for users matches this goal; others relate to appearance, code size, or limited use, which are not main goals.

3. Final Answer:

   To ensure the app runs safely, quickly, and reliably for users -> Option D

4. Quick Check:

   Production readiness = safe, fast, reliable [OK]

Hint: Focus on user experience and app stability [OK]

Common Mistakes:

• Confusing production readiness with UI design
• Thinking it only reduces code size
• Assuming it limits app usage to local only

2. Which of the following is a correct way to add multiple workers for production in FastAPI using Uvicorn?

easy

A. uvicorn main:app --worker-count=4

B. uvicorn main:app -workers 4

C. uvicorn main:app --workers 4

D. uvicorn main:app --multi-workers 4

Solution

1. Step 1: Recall Uvicorn's correct syntax for workers

   The correct flag to specify workers is '--workers' followed by the number.

2. Step 2: Match options with correct syntax

   uvicorn main:app --workers 4 uses '--workers 4' which is correct; others use invalid flags.

3. Final Answer:

   uvicorn main:app --workers 4 -> Option C

4. Quick Check:

   Correct flag for workers = --workers [OK]

Hint: Remember Uvicorn uses '--workers' flag for multiple workers [OK]

Common Mistakes:

• Using '-workers' instead of '--workers'
• Adding extra words like 'worker-count'
• Using non-existent flags like '--multi-workers'

3. Given this FastAPI app snippet with logging middleware added, what will happen when a request is made?

from fastapi import FastAPI
from starlette.middleware.base import BaseHTTPMiddleware
import logging

app = FastAPI()

class LogMiddleware(BaseHTTPMiddleware):
    async def dispatch(self, request, call_next):
        logging.info(f"Request path: {request.url.path}")
        response = await call_next(request)
        return response

app.add_middleware(LogMiddleware)

@app.get("/")
async def root():
    return {"message": "Hello"}

medium

A. Logs the request path and returns JSON {"message": "Hello"}

B. Returns JSON {"message": "Hello"} without logging

C. Raises an error because middleware is not supported

D. Logs the request path but returns an empty response

Solution

1. Step 1: Understand middleware behavior

   The middleware logs the request path before passing control to the route handler.

2. Step 2: Check the route response

   The route returns JSON {"message": "Hello"} as usual after logging.

3. Final Answer:

   Logs the request path and returns JSON {"message": "Hello"} -> Option A

4. Quick Check:

   Middleware logs + route returns JSON [OK]

Hint: Middleware runs before route, so logging happens first [OK]

Common Mistakes:

• Assuming middleware blocks response
• Thinking middleware causes errors
• Ignoring the logging effect

4. You added security middleware to your FastAPI app but users report 500 errors. Which mistake likely caused this?

medium

A. Middleware class did not call the next handler in dispatch

B. Middleware was added after route definitions

C. Middleware was added with incorrect import path

D. Middleware was added twice accidentally

Solution

1. Step 1: Identify middleware dispatch requirements

   Middleware must call the next handler (call_next) to continue request processing.

2. Step 2: Analyze error cause

   If dispatch does not call call_next, the request chain breaks causing server errors (500).

3. Final Answer:

   Middleware class did not call the next handler in dispatch -> Option A

4. Quick Check:

   Missing call_next causes 500 errors [OK]

Hint: Always call call_next in middleware dispatch [OK]

Common Mistakes:

• Adding middleware after routes (usually allowed)
• Wrong import causing import errors, not 500
• Adding middleware twice causes warnings, not 500 errors

5. You want to prepare your FastAPI app for production to handle high traffic and improve security. Which combination of steps is best?

hard

A. Use multiple workers but skip security middleware and logging

B. Use multiple Uvicorn workers, add security middleware, enable logging

C. Add only logging, ignore workers and security middleware

D. Use single worker, disable middleware, remove logging for speed

Solution

1. Step 1: Identify production readiness goals

   Goals include handling many users (workers), protecting app (security middleware), and tracking issues (logging).

2. Step 2: Match options with these goals

   Use multiple Uvicorn workers, add security middleware, enable logging includes all key steps; others skip important parts reducing readiness.

3. Final Answer:

   Use multiple Uvicorn workers, add security middleware, enable logging -> Option B

4. Quick Check:

   Workers + security + logging = production ready [OK]

Hint: Combine workers, security, and logging for production [OK]

Common Mistakes:

• Skipping security middleware thinking it's optional
• Using single worker limits performance
• Disabling logging hides important errors