What are the trade-offs involved in setting longer data retention for performance data?

• A. Longer retention improves historical analysis but increases storage requirements and could impact performance; use archiving or data rollups
• B. Shorter retention reduces storage needs but limits historical analysis
• C. Retention has no impact on performance
• D. Archiving is unrelated to retention

Answer: (A)

Longer data retention keeps more detail over time, which is valuable for historical analysis, trend spotting, and forensic debugging because you can examine longer periods and compare different time frames. But it also means your database grows larger, which drives up storage costs and increases the work required for backups, indexing, and queries. That extra data can slow performance, especially for queries that scan wide time ranges or require aggregations over many points. A common, practical approach is to keep recent data in full detail and move older data to cheaper storage or summarize it with rollups, so you can still analyze long-term trends without the full raw data burden. The other options miss key trade-offs: shorter retention cuts storage needs but sacrifices historical insight, and retention clearly does impact performance; archiving is tied to retention rather than unrelated.