You need to recommend a solution to meet the recovery requirements for the manufacturing database. Your solution must minimize costs. What should you recommend?

Database snapshots provide a fast and efficient way to revert a database to a previous point in time, which is crucial for recovery. They are cost-effective because they consume minimal storage, using a copy-on-write mechanism that only stores pages changed after the snapshot was created, and offer rapid recovery without requiring a full restore operation.

Transaction log backups are part of a traditional backup and restore strategy and, while enabling point-in-time recovery, require a full or differential backup and a restoration process, which is generally more resource-intensive and potentially slower than reverting a snapshot for quick recovery.

Differential backups improve recovery time by only backing up changes since the last full backup, but they still require a full backup and a restoration process, making them less immediate and potentially more costly in operational effort than the instant revert capability of a snapshot.

SQL Server Failover Clustering is a high-availability solution designed to minimize downtime in case of server hardware or OS failures, not a primary or cost-effective solution for recovering from data corruption or accidental changes within the database itself, and it incurs significant licensing and infrastructure costs.

Peer-to-peer replication is a complex and costly high-availability and data distribution solution that maintains multiple writable copies of data, which is not primarily designed for cost-effective point-in-time recovery from data errors and can even propagate corruption if not carefully managed.