What is a best practice regarding backups in an NPM deployment?

What is a best practice regarding backups in an NPM deployment?

• A. Test backups before putting them into production
• B. Backups are optional
• C. Only back up configuration, not database
• D. Backups should be performed once a year

Answer: (D)

The main idea is that backups must be usable when you need them, which means you should verify them by testing restores before relying on them in production. In an NPM deployment, this means performing restore drills to confirm that a backup can actually be used to recover the system, that the backup captures everything you rely on (both configuration and database data), and that the restore process meets your recovery objectives. Backups should be automated and performed regularly enough to minimize data loss, with restoration tests run periodically in a safe environment to confirm the data integrity and the time required to recover. Also, store backups securely offsite, encrypt them as needed, and enforce retention policies so you can recover from different types of incidents.

The main idea is that backups must be usable when you need them, which means you should verify them by testing restores before relying on them in production. In an NPM deployment, this means performing restore drills to confirm that a backup can actually be used to recover the system, that the backup captures everything you rely on (both configuration and database data), and that the restore process meets your recovery objectives. Backups should be automated and performed regularly enough to minimize data loss, with restoration tests run periodically in a safe environment to confirm the data integrity and the time required to recover. Also, store backups securely offsite, encrypt them as needed, and enforce retention policies so you can recover from different types of incidents.