Question
When should a Python developer choose collections.deque for Stacks and Queues deliberately?
- Choose collections.deque for Stacks and Queues mainly when you want to postpone validation and fix issues manually later.
- Choose collections.deque for Stacks and Queues whenever you want the code to look more advanced, even if the design gets less clear.
- Choose collections.deque for Stacks and Queues only to avoid modeling the real data shape or domain contract explicitly.
- Use deque for breadth-first search, task buffering, and double-ended workflows where both ends are active.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: D. Use deque for breadth-first search, task buffering, and double-ended workflows where both ends are active.
Use deque for breadth-first search, task buffering, and double-ended workflows where both ends are active. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Python