Which practice is recommended to manage database growth in a large NPM deployment?

Which practice is recommended to manage database growth in a large NPM deployment?

• A. Archive old data
• B. Split the environment across multiple servers and optimized storage
• C. Enable data retention rollups
• D. Maintain indexes

Answer: (A)

Managing database growth in a large NPM deployment hinges on applying a data lifecycle policy that keeps the active database lean while preserving historical data elsewhere. Archiving old data directly reduces the volume of current data in the live database, which speeds up queries, shortens backup and maintenance windows, and helps the system stay responsive as the environment scales. The archived data can still be accessed for long-term reporting or audits without burdening the live store with decades of granular metrics. Other approaches can help in specific ways, but they don’t address the growth of the live data as effectively. Splitting the environment across multiple servers and storage can help with scalability, but it involves more complex infrastructure and doesn’t remove old data from the primary database. Enabling data retention rollups reduces detail by summarizing older data, which helps size and performance but sacrifices granularity. Maintaining indexes improves query performance but doesn’t reduce the amount of data stored.

Managing database growth in a large NPM deployment hinges on applying a data lifecycle policy that keeps the active database lean while preserving historical data elsewhere. Archiving old data directly reduces the volume of current data in the live database, which speeds up queries, shortens backup and maintenance windows, and helps the system stay responsive as the environment scales. The archived data can still be accessed for long-term reporting or audits without burdening the live store with decades of granular metrics.

Other approaches can help in specific ways, but they don’t address the growth of the live data as effectively. Splitting the environment across multiple servers and storage can help with scalability, but it involves more complex infrastructure and doesn’t remove old data from the primary database. Enabling data retention rollups reduces detail by summarizing older data, which helps size and performance but sacrifices granularity. Maintaining indexes improves query performance but doesn’t reduce the amount of data stored.