Bird
0
0

Why might polling as a fallback be less efficient than WebSockets in Flask applications?

hard📝 Conceptual Q10 of 15
Flask - WebSocket and Real-Time
Why might polling as a fallback be less efficient than WebSockets in Flask applications?
APolling repeatedly sends requests even when no new data is available
BPolling requires a persistent connection open at all times
CPolling automatically compresses data, reducing bandwidth
DPolling uses server push to send data instantly
Step-by-Step Solution
Solution:

  1. Step 1: Understand polling behavior

    Polling sends requests at intervals regardless of data changes, causing unnecessary traffic.

  2. Step 2: Compare with WebSocket efficiency

    WebSockets keep a connection open and send data only when available, saving resources.

  3. Final Answer:

    Polling repeatedly sends requests even when no new data is available -> Option A

  4. Quick Check:

    Polling inefficiency = repeated requests without new data [OK]
Quick Trick: Polling wastes resources by requesting unchanged data [OK]
Common Mistakes:
MISTAKES
  • Thinking polling uses persistent connections
  • Assuming polling compresses data automatically
  • Confusing polling with server push

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Flask Quizzes
Background Tasks - Defining Celery tasks - Quiz 13medium Deployment - Logging in production - Quiz 12easy Flask Ecosystem and Patterns - Migrating to async Flask - Quiz 4medium Flask Ecosystem and Patterns - Application factory pattern deep dive - Quiz 9hard Middleware and Extensions - Before_request as middleware alternative - Quiz 15hard Middleware and Extensions - Extension initialization pattern - Quiz 1easy Testing Flask Applications - Test fixtures with pytest - Quiz 15hard WebSocket and Real-Time - Room-based messaging - Quiz 5medium WebSocket and Real-Time - Namespace concept - Quiz 13medium WebSocket and Real-Time - Broadcasting to clients - Quiz 15hard