In financial data architectures, time series data require storage designed to handle what?

• A. High-frequency trading risk optimization models.
• B. Data management and storage designed to accommodate time series data and data structured financial markets data (e.g. time periodicities of 5 trading days, followed by 2 weekend non-trading days, etc.).
• C. Manual recordkeeping for trade blotters.
• D. Regulatory compliance checklists.

Answer: (B)

Time series data in finance are sequences of observations indexed by time, so the storage layer must treat time as the primary access path. This requires efficient appends and fast range queries over time, along with calendar-aware handling of trading days, weekends, and holidays. Financial markets produce data that are structured by time and instrument, often needing consistent alignment across different time granularities (for example, daily OHLCV data across multiple assets, or multi-day windows with specific trading calendars). Designing storage to accommodate these patterns—time-based partitioning, time zones, gaps, and effective compression—enables scalable analytics and accurate aggregations. That’s why the best choice emphasizes data management and storage built to handle time series data and data structured financial markets data. The other options describe modeling, manual recordkeeping, or compliance tasks, which don’t address how time-based financial data should be stored.