What is a typical benefit of using data rollups in NPM?

What is a typical benefit of using data rollups in NPM?

• A. They increase data detail for the entire history.
• B. They compress data to store longer histories, improving storage and query performance.
• C. They delete data after 90 days.
• D. They replicate data to remote sites.

Answer: (B)

Data rollups summarize fine-grained time series data into coarser intervals, turning many individual measurements into fewer, higher-level points. This approach dramatically reduces storage needs while keeping the ability to analyze long-term trends, which is the typical benefit. By compressing older data, storage requirements shrink and queries over long periods become faster because there’s less data to process. Older data becomes less detailed, but the overarching patterns and trends remain visible, which is exactly what you want for extended history. The other options don’t fit: increasing detail across the entire history would require more storage, deleting data after a fixed period isn’t what rollups do, and replicating data to remote sites is about data distribution, not rollups.

Data rollups summarize fine-grained time series data into coarser intervals, turning many individual measurements into fewer, higher-level points. This approach dramatically reduces storage needs while keeping the ability to analyze long-term trends, which is the typical benefit. By compressing older data, storage requirements shrink and queries over long periods become faster because there’s less data to process. Older data becomes less detailed, but the overarching patterns and trends remain visible, which is exactly what you want for extended history. The other options don’t fit: increasing detail across the entire history would require more storage, deleting data after a fixed period isn’t what rollups do, and replicating data to remote sites is about data distribution, not rollups.