What is a potential impact of extending data retention in NPM?

What is a potential impact of extending data retention in NPM?

• A. Increases database size and may impact performance
• B. Always improves performance
• C. Does not affect storage
• D. Deletes old data automatically

Answer: (A)

Extending data retention means the system keeps more historical data in the database for a longer time. That increases the database size and the amount of data queries, backups, and reports must process, which can lead to slower performance if resources or indexing aren’t scaled or tuned accordingly. It does not automatically improve performance, and it does affect storage because more data requires more disk space. It also doesn’t delete old data automatically—retention means preserving it unless you set up archiving or purging later. To balance needs, you can archive older records, summarize data, or use partitioning and regular maintenance to keep performance acceptable while maintaining historical history.

Extending data retention means the system keeps more historical data in the database for a longer time. That increases the database size and the amount of data queries, backups, and reports must process, which can lead to slower performance if resources or indexing aren’t scaled or tuned accordingly. It does not automatically improve performance, and it does affect storage because more data requires more disk space. It also doesn’t delete old data automatically—retention means preserving it unless you set up archiving or purging later. To balance needs, you can archive older records, summarize data, or use partitioning and regular maintenance to keep performance acceptable while maintaining historical history.