[Solved] Why might you choose a class-based dependency over a function-based one in FastAPI? - Ans: To maintain internal state or reuse setup logic across calls | FastAPI

FastAPI - Dependency Injection

Why might you choose a class-based dependency over a function-based one in FastAPI?

ABecause classes automatically cache results

BTo maintain internal state or reuse setup logic across calls

CTo avoid using async code

DBecause functions cannot accept parameters

Step-by-Step Solution

Solution:

Step 1: Understand benefits of class-based dependencies
Classes can hold internal state and reuse setup logic, unlike stateless functions.
Step 2: Evaluate incorrect options
Functions can accept parameters, async is optional, classes don't auto-cache results.
Final Answer:
To maintain internal state or reuse setup logic across calls -> Option B
Quick Check:
Stateful logic favors classes = D [OK]

Quick Trick: Use classes to keep state or reuse logic [OK]

Common Mistakes:

MISTAKES

Master "Dependency Injection" in FastAPI

9 interactive learning modes - each teaches the same concept differently

More FastAPI Quizzes

Why might you choose a class-based dependency over a function-based one in FastAPI?