Question
When should a Python developer choose datetime and Time Zone Awareness deliberately?
- Choose timezone-aware datetimes for persisted timestamps, distributed systems, and API contracts that outlive one machine's local clock.
- Choose datetime and Time Zone Awareness mainly when you want to postpone validation and fix issues manually later.
- Choose datetime and Time Zone Awareness whenever you want the code to look more advanced, even if the design gets less clear.
- Choose datetime and Time Zone Awareness only to avoid modeling the real data shape or domain contract explicitly.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: A. Choose timezone-aware datetimes for persisted timestamps, distributed systems, and API contracts that outlive one machine's local clock.
Choose timezone-aware datetimes for persisted timestamps, distributed systems, and API contracts that outlive one machine's local clock. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Python