You need to recommend a disaster recovery strategy for the Inventory database. What should you include in the recommendation?

Log shipping is a straightforward disaster recovery solution that automatically backs up transaction logs from a primary database and restores them to one or more secondary databases on separate servers. It provides geographic redundancy with configurable latency and is ideal when a simple, low-cost DR strategy is needed without the complexity of clustering or availability groups. It also supports a warm standby that can be brought online if the primary fails.

SQL Server Failover Clustering is a high-availability solution that protects against server-level failures within a single datacenter using shared storage, but it does not provide geographic disaster recovery since all nodes share the same storage and are typically co-located.

AlwaysOn Availability Groups provide high availability and disaster recovery but require SQL Server Enterprise Edition and Windows Server Failover Clustering infrastructure, making them more complex and costly than log shipping for a straightforward DR recommendation.

Peer-to-peer replication is designed for scale-out read workloads and multi-master scenarios to distribute data across multiple nodes, not for disaster recovery, as it does not provide a clean failover mechanism or maintain a recoverable standby copy.