Why databases persist data in FastAPI - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do databases persist data?

Which of the following best explains why databases persist data?

A To delete old data automatically after the application closes

B To keep data available even after the application or server stops running

C To speed up the application by storing data only in memory temporarily

D To prevent users from accessing data during server downtime

💡 Hint

Think about what happens to data when the computer or app is turned off.

Databases save data permanently so it is not lost when the app or server stops. This is called persistence.

❓ component_behavior

intermediate

What happens to data stored in a database after server restart?

Consider a FastAPI app connected to a database. What happens to the data stored in the database if the server restarts?

A The data becomes inaccessible until manually restored

B The data is erased and lost after the restart

C The data is moved to a temporary cache and then deleted

D The data remains intact and accessible after the restart

💡 Hint

Think about the purpose of persistent storage.

Databases store data on disk or other permanent storage, so data stays safe even if the server restarts.

📝 Syntax

advanced

Identify the correct FastAPI code snippet to save data persistently

Which FastAPI code snippet correctly saves data to a database so it persists?

FastAPI

from fastapi import FastAPI
from sqlalchemy.orm import Session
from models import Item

app = FastAPI()

@app.post('/items/')
async def create_item(item: Item, db: Session):
    # Save item to database
    ...

A

db.insert(item)
db.save()
return item

B

db.save(item)
return item

C

db.add(item)
db.commit()
return item

D

db.push(item)
db.commit()
return item

💡 Hint

Look for the standard SQLAlchemy methods to add and save data.

In SQLAlchemy, use add() to add an object and commit() to save changes persistently.

❓ state_output

advanced

What is the output after restarting FastAPI app with saved data?

Given a FastAPI app that saves user data to a database, what will be the output of fetching users after restarting the app?

FastAPI

from fastapi import FastAPI
from sqlalchemy.orm import Session
from models import User

app = FastAPI()

@app.get('/users/')
async def read_users(db: Session):
    return db.query(User).all()

A [{'id': 1, 'name': 'Alice'}, {'id': 2, 'name': 'Bob'}]

B []

C None

D Error: database connection lost

💡 Hint

Think about whether data saved before restart is still there.

Since the data is saved persistently in the database, it remains available after app restart.

🔧 Debug

expert

Why does this FastAPI app lose data after restart?

Review this FastAPI code snippet. Why does the data disappear after restarting the app?

FastAPI

from fastapi import FastAPI

app = FastAPI()

items = []

@app.post('/items/')
async def add_item(name: str):
    items.append(name)
    return {'items': items}

A Because data is stored only in a list in memory, not in a database

B Because the list is cleared automatically on each request

C Because FastAPI deletes variables after each function call

D Because the app uses an incorrect HTTP method

💡 Hint

Think about where the data is saved and what happens when the app restarts.

Data stored in a Python list exists only while the app runs. Restarting clears memory, so data is lost.

Practice

1. Why do databases persist data in applications like FastAPI?

easy

A. To keep data safe even if the app stops or restarts

B. To make the app run faster

C. To delete old data automatically

D. To prevent users from accessing the app

Solution

1. Step 1: Understand what persistence means

   Persistence means data stays saved even after the program stops running.

2. Step 2: Connect persistence to databases in FastAPI

   Databases store data on disk, so FastAPI can retrieve it later, even after restarts.

3. Final Answer:

   To keep data safe even if the app stops or restarts -> Option A

4. Quick Check:

   Persistence means data stays saved [OK]

Hint: Persistence means data stays saved after app stops [OK]

Common Mistakes:

• Thinking databases speed up the app only
• Confusing persistence with data deletion
• Believing databases block user access

2. Which of the following is the correct way to save data to a database in FastAPI?

easy

A. Use a database session to add and commit the data

B. Print the data to the console

C. Store data in a local variable only

D. Use a global variable to hold data

Solution

1. Step 1: Identify how FastAPI interacts with databases

   FastAPI uses database sessions to add and commit data to save it permanently.

2. Step 2: Compare options for saving data

   Printing or using variables does not save data persistently; only committing via session does.

3. Final Answer:

   Use a database session to add and commit the data -> Option A

4. Quick Check:

   Commit data with session to save [OK]

Hint: Commit data with session to save persistently [OK]

Common Mistakes:

• Thinking printing saves data
• Using variables instead of database commit
• Skipping the commit step

3. Given this FastAPI code snippet, what will happen when the app restarts?

from fastapi import FastAPI
from sqlalchemy.orm import Session

app = FastAPI()

@app.post('/items/')
def create_item(session: Session, item: Item):
    session.add(item)
    session.commit()
    return item

medium

A. The items will be saved only in memory

B. The saved items will be lost after restart

C. The app will crash on restart

D. The saved items will still be available after restart

Solution

1. Step 1: Understand what session.commit() does

   Calling commit() saves data permanently to the database storage.

2. Step 2: Consider app restart effect on database data

   Since data is saved in the database, it remains after the app restarts.

3. Final Answer:

   The saved items will still be available after restart -> Option D

4. Quick Check:

   Committed data persists after restart [OK]

Hint: Committed data stays after app restarts [OK]

Common Mistakes:

• Confusing commit with temporary memory storage
• Assuming app restart clears database
• Thinking session.add alone saves data

4. What is wrong with this FastAPI code that tries to save data?

from fastapi import FastAPI

app = FastAPI()

@app.post('/users/')
def create_user(user: dict):
    user['id'] = 1
    return user

medium

A. It uses the wrong HTTP method

B. It does not save data to a database, so data is lost on restart

C. It has a syntax error in the function

D. It commits data twice

Solution

1. Step 1: Check if data is saved to a database

   The code only modifies and returns a dictionary; it does not save to any database.

2. Step 2: Understand consequence of no database saving

   Without saving to a database, data is lost when the app stops or restarts.

3. Final Answer:

   It does not save data to a database, so data is lost on restart -> Option B

4. Quick Check:

   No database save means no persistence [OK]

Hint: Data must be saved to database for persistence [OK]

Common Mistakes:

• Thinking returning dict saves data
• Confusing HTTP method with persistence
• Assuming syntax error when none exists

5. You want to ensure user data is saved permanently in FastAPI. Which approach correctly combines FastAPI and database persistence?

hard

A. Store user data in a global list variable inside the app

B. Save user data only in request body without database interaction

C. Use FastAPI with SQLAlchemy session to add and commit user data to a database

D. Print user data to console and rely on logs for storage

Solution

1. Step 1: Identify how to save data permanently

   Permanent saving requires writing data to a database, not just memory or logs.

2. Step 2: Match FastAPI with database usage

   FastAPI works well with SQLAlchemy sessions to add and commit data to databases.

3. Step 3: Eliminate incorrect options

   Global variables and printing do not persist data after app stops; request body alone is temporary.

4. Final Answer:

   Use FastAPI with SQLAlchemy session to add and commit user data to a database -> Option C

5. Quick Check:

   Database commit ensures permanent data [OK]

Hint: Use database session commit for permanent save [OK]

Common Mistakes:

• Using global variables for persistence
• Relying on request data without saving
• Thinking console logs save data