Why advanced patterns solve real problems 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'

ARequest

BDepends

CResponse

DFastAPI

Attempts:

3 left

💡 Hint

Common Mistakes

Importing Request instead of FastAPI

Using Response to create app

The FastAPI class is used to create the app instance.

2fill in blank

medium

Complete the code to define a GET endpoint that returns a greeting.

FastAPI

@app.[1]("/")
async def read_root():
    return {"message": "Hello World"}

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

Aget

Bput

Cpost

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Using post decorator for GET endpoint

Misspelling the decorator name

The @app.get decorator defines a GET HTTP method endpoint.

3fill in blank

hard

Fix the error in the dependency injection by completing the code.

FastAPI

from fastapi import Depends

def common_parameters(q: str = None):
    return {"q": q}

@app.get("/items/")
async def read_items(params: dict = [1](common_parameters)):
    return params

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

AResponse

BRequest

CDepends

DBody

Attempts:

3 left

💡 Hint

Common Mistakes

Using Request or Response instead of Depends

Forgetting to import Depends

The Depends function is used to declare dependencies in FastAPI.

4fill in blank

hard

Fill both blanks to create a reusable router and include it in the main app.

FastAPI

from fastapi import APIRouter

router = [1]()

@router.get("/users")
async def get_users():
    return ["Alice", "Bob"]

app.[2](router)

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

AAPIRouter

BDepends

Cinclude_router

Dadd_route

Attempts:

3 left

💡 Hint

Common Mistakes

Using Depends instead of APIRouter

Using add_route instead of include_router

APIRouter() creates a router instance. app.include_router() adds it to the main app.

5fill in blank

hard

Fill all three blanks to create a Pydantic model, use it in a POST endpoint, and return the data.

FastAPI

from pydantic import BaseModel
from fastapi import FastAPI

app = FastAPI()

class Item([1]):
    name: str
    price: float

@app.post("/items/")
async def create_item(item: [2]):
    return {"item_name": item.[3]

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

ABaseModel

BItem

Cname

DFastAPI

Attempts:

3 left

💡 Hint

Common Mistakes

Using FastAPI instead of BaseModel

Returning item.price instead of item.name

The model class inherits from BaseModel. The endpoint parameter uses the model Item. The returned value accesses the name attribute.

Practice

1. Why do advanced patterns in FastAPI help developers build better applications?

easy

A. They organize code to be clearer and easier to maintain.

B. They make the app run faster by skipping validation.

C. They remove the need for any testing.

D. They automatically fix bugs without developer input.

Solution

1. Step 1: Understand the role of advanced patterns

   Advanced patterns help organize code logically and clearly, making it easier to read and maintain.

2. Step 2: Compare options with this understanding

   Options describing automatic bug fixes, skipping validation, and removing testing are unrealistic or incorrect, while the one about organizing code correctly states the main advantage.

3. Final Answer:

   They organize code to be clearer and easier to maintain. -> Option A

4. Quick Check:

   Code clarity = D [OK]

Hint: Think: How does better code structure help? [OK]

Common Mistakes:

• Assuming advanced patterns speed up runtime directly
• Believing patterns remove need for testing
• Thinking patterns auto-fix bugs

2. Which of the following is the correct way to use a dependency injection pattern in FastAPI?

easy

A. Use the Depends function inside the path operation function parameters.

B. Call the dependency function directly inside the route handler without Depends.

C. Define dependencies only in global variables outside FastAPI app.

D. Use @app.dependency() decorator on dependency functions.

Solution

1. Step 1: Recall FastAPI dependency injection syntax

   FastAPI uses Depends in function parameters to inject dependencies automatically.

2. Step 2: Evaluate each option

   Using the Depends function inside the path operation function parameters matches the correct pattern. Calling the dependency directly skips Depends, defining dependencies only in global variables is incorrect usage, and @app.dependency() is not a valid decorator.

3. Final Answer:

   Use the Depends function inside the path operation function parameters. -> Option A

4. Quick Check:

   Depends usage = B [OK]

Hint: Remember: Dependencies go in parameters with Depends() [OK]

Common Mistakes:

• Calling dependencies directly without Depends
• Trying to decorate dependencies with non-existent decorators
• Defining dependencies only as global variables

3. Given this FastAPI code snippet, what will be the output when accessing /items/42?

from fastapi import FastAPI, Depends

app = FastAPI()

def get_query(q: str = None):
    return q or "default"

@app.get("/items/{item_id}")
async def read_item(item_id: int, query: str = Depends(get_query)):
    return {"item_id": item_id, "query": query}

medium

A. {"item_id": 42, "query": null}

B. {"item_id": 42, "query": "default"}

C. 404 Not Found error

D. 500 Internal Server Error

Solution

1. Step 1: Understand dependency behavior

   The get_query function returns the query parameter if provided; otherwise, it returns "default".

2. Step 2: Analyze the request URL and parameters

   The URL /items/42 provides item_id=42 but no query parameter, so q is None, triggering the default value.

3. Final Answer:

   {"item_id": 42, "query": "default"} -> Option B

4. Quick Check:

   Missing query param returns default = A [OK]

Hint: No query param? Dependency returns default [OK]

Common Mistakes:

• Assuming missing query param is null instead of default
• Expecting an error without query param
• Confusing path and query parameters

4. What is the main issue with this FastAPI code snippet?

from fastapi import FastAPI, Depends

app = FastAPI()

def get_user(user_id: int):
    return {"user_id": user_id}

@app.get("/users/")
async def read_user(user: dict = Depends(get_user)):
    return user

medium

A. The dependency function returns a dict instead of a Pydantic model.

B. The route path is missing a required path parameter.

C. The dependency function requires a parameter but none is provided by FastAPI.

D. The route handler is missing the async keyword.

Solution

1. Step 1: Check dependency function parameters

   The get_user function requires user_id as an argument, but FastAPI cannot provide it automatically here.

2. Step 2: Analyze route and dependency usage

   The route /users/ does not provide user_id, so FastAPI will raise an error due to missing dependency argument.

3. Final Answer:

   The dependency function requires a parameter but none is provided by FastAPI. -> Option C

4. Quick Check:

   Missing dependency argument = C [OK]

Hint: Dependencies needing args must get them from path or query [OK]

Common Mistakes:

• Ignoring missing dependency parameters
• Thinking dict return type causes error
• Assuming async missing is an error

5. You want to create a reusable service in FastAPI that fetches user data and caches results to improve performance. Which advanced pattern best solves this real problem?

hard

A. Avoid caching and always fetch fresh data to keep code simple.

B. Write all fetching logic directly inside each route handler to avoid complexity.

C. Use global variables to store cached data and access them in routes.

D. Use dependency injection with a singleton service class that caches data internally.

Solution

1. Step 1: Identify the need for code reuse and caching

   To improve performance and reuse code, a service class with caching is ideal.

2. Step 2: Match the pattern to FastAPI features

   Dependency injection allows injecting a singleton service that manages caching cleanly and efficiently.

3. Final Answer:

   Use dependency injection with a singleton service class that caches data internally. -> Option D

4. Quick Check:

   Reusable cached service = A [OK]

Hint: Singleton service + Depends = reusable cached logic [OK]

Common Mistakes:

• Putting logic in every route duplicates code
• Using global variables risks bugs and is hard to maintain
• Skipping caching loses performance benefits