Why validation prevents bad data in FastAPI - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the FastAPI class.

FastAPI

from fastapi import [1]
app = [1]()

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

AResponse

BRequest

CFastAPI

DDepends

Attempts:

3 left

💡 Hint

Common Mistakes

Importing Request or Response instead of FastAPI.

Forgetting to create the app instance.

The FastAPI class is imported to create the app instance.

2fill in blank

medium

Complete the code to define a Pydantic model for user input validation.

FastAPI

from pydantic import BaseModel

class User([1]):
    name: str
    age: int

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

ABaseModel

BModel

CSchema

DValidator

Attempts:

3 left

💡 Hint

Common Mistakes

Using Model or Schema which are not Pydantic base classes.

Forgetting to inherit from any class.

Pydantic models inherit from BaseModel to enable validation.

3fill in blank

hard

Fix the error in the route decorator to accept POST requests.

FastAPI

@app.[1]("/users")
async def create_user(user: User):
    return user

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

Adelete

Bget

Cput

Dpost

Attempts:

3 left

💡 Hint

Common Mistakes

Using GET instead of POST for data creation.

Using PUT or DELETE which are for update or removal.

The POST method is used to send data to the server for creation.

4fill in blank

hard

Fill both blanks to validate user input and return a success message.

FastAPI

from fastapi import [1]

@app.post("/users")
async def create_user(user: [2]):
    return {"message": f"User {user.name} created"}

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

AFastAPI

BUser

CRequest

DResponse

Attempts:

3 left

💡 Hint

Common Mistakes

Using Request or Response instead of User model for input.

Not importing FastAPI.

FastAPI is imported to create the app, and User is the Pydantic model for validation.

5fill in blank

hard

Fill all three blanks to create a validated POST endpoint that returns the user's age doubled.

FastAPI

from fastapi import [1]
from pydantic import BaseModel

app = [2]()

class User(BaseModel):
    name: str
    age: int

@app.post("/double-age")
async def double_age(user: [3]):
    return {"double_age": user.age * 2}

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

AFastAPI

CUser

DBaseModel

Attempts:

3 left

💡 Hint

Common Mistakes

Using BaseModel instead of User for the parameter.

Not creating the app instance correctly.

FastAPI is imported and used to create the app instance. The User model validates input.

Practice

1. Why does FastAPI use validation on incoming data?

easy

A. To make the app run slower

B. To ignore user input errors

C. To ensure data is correct before using it

D. To skip checking data types

Solution

1. Step 1: Understand the purpose of validation

   Validation checks if the data matches expected rules before the app uses it.

2. Step 2: Identify the benefit in FastAPI

   FastAPI uses validation to catch bad data early and avoid errors later.

3. Final Answer:

   To ensure data is correct before using it -> Option C

4. Quick Check:

   Validation = Ensures correct data [OK]

Hint: Validation means checking data before use [OK]

Common Mistakes:

• Thinking validation slows the app down
• Believing validation ignores errors
• Assuming validation skips data checks

2. Which of these is the correct way to declare a Pydantic model field with validation in FastAPI?

easy

A. name = str(min_length=3)

B. name: str = Field(min_length=3)

C. name: Field = str(min_length=3)

D. Field(name: str, min_length=3)

Solution

1. Step 1: Recall Pydantic field syntax

   Fields are declared with type hints and Field() for validation, like name: str = Field(...).

2. Step 2: Match correct syntax

   name: str = Field(min_length=3) uses name: str = Field(min_length=3), which is correct.

3. Final Answer:

   name: str = Field(min_length=3) -> Option B

4. Quick Check:

   Field syntax = type hint + Field() [OK]

Hint: Use type hint plus Field() for validation [OK]

Common Mistakes:

• Putting validation inside type hint
• Calling Field() without assignment
• Using wrong order of parameters

3. Given this FastAPI endpoint using a Pydantic model with age: int = Field(gt=0), what happens if a client sends {"age": -5}?

medium

A. The request succeeds and age is set to -5

B. The server crashes with an exception

C. The age field is ignored and set to 0

D. FastAPI returns a validation error response

Solution

1. Step 1: Understand the validation rule

   The field age must be greater than 0 (gt=0).

2. Step 2: Check input against rule

   Input -5 violates this rule, so validation fails.

3. Final Answer:

   FastAPI returns a validation error response -> Option D

4. Quick Check:

   Invalid data triggers validation error [OK]

Hint: Invalid data triggers error response [OK]

Common Mistakes:

• Assuming invalid data is accepted
• Thinking invalid fields get default values
• Believing server crashes on validation failure

4. What is wrong with this FastAPI Pydantic model if it does not reject empty strings for a required username: str field?

class User(BaseModel):
    username: str

medium

A. Missing validation to prevent empty strings

B. Field type should be int, not str

C. BaseModel is not imported

D. username should be Optional[str]

Solution

1. Step 1: Analyze the model field

   The field username: str accepts any string, including empty ones.

2. Step 2: Identify missing validation

   To reject empty strings, add validation like min_length=1 in Field().

3. Final Answer:

   Missing validation to prevent empty strings -> Option A

4. Quick Check:

   Empty strings need explicit validation [OK]

Hint: Add min_length to reject empty strings [OK]

Common Mistakes:

• Assuming str type rejects empty strings
• Changing type to int incorrectly
• Making field optional instead of validating

5. You want to prevent bad data by validating a nested Pydantic model in FastAPI. Which approach correctly ensures the nested data is validated?

hard

A. Use a Pydantic model as a field type inside another model

B. Use a plain dict type for nested data without a model

C. Validate nested data manually after receiving it

D. Skip validation for nested data to improve speed

Solution

1. Step 1: Understand nested model validation

   FastAPI validates nested models automatically if you use Pydantic models as field types.

2. Step 2: Compare options

   Using a Pydantic model inside another model ensures nested validation, unlike plain dict or manual checks.

3. Final Answer:

   Use a Pydantic model as a field type inside another model -> Option A

4. Quick Check:

   Nested Pydantic models validate nested data [OK]

Hint: Nest Pydantic models for automatic validation [OK]

Common Mistakes:

• Using dict instead of model for nested data
• Skipping nested validation for speed
• Validating nested data manually outside model