Question
📝 **Question:** When is fastapi.BackgroundTasks the WRONG choice?
📋 Pick the right answer.
💡 **Hint:** Re-read the theory above if unsure.
A BackgroundTasks should be replaced with a real queue only when the task takes longer than 30 seconds, because anything shorter typically completes before the worker is reaped during a normal redeploy cycle even with rolling restarts B Any work whose loss would harm the user — emails, charges, webhook deliveries, notifications C Once you have more than one background task per request, you must move to Celery because BackgroundTasks only supports a single task per response and silently drops any subsequent calls within the same response cycle every time D When the work is async, use Celery; when it's sync, BackgroundTasks is fine — the deciding factor is whether the function needs an event loop, not whether the work itself is durable or has user-facing side effects to manage carefully