A software company wants to ensure that their application remains available in outages in one...

Synchronous remote replication maintains an exact, continuously up-to-date copy of production data at a second data center, since every write is committed to both locations before being acknowledged, which means that if the primary data center suffers an outage, the secondary site already holds a fully current copy of the data and applications can fail over to it with essentially no data loss and minimal disruption, directly supporting the goal of continuous availability across a data center outage. This proactive, real-time replication architecture is the correct technical mechanism for the stated requirement, since it ensures data readiness at the alternate site before an outage ever occurs, rather than reacting to one afterward. Reviewing storage capacity (B) is a routine operational and planning activity that ensures sufficient space exists, but it does nothing to establish an available, current copy of data at an alternate location during an outage. Documenting outage recovery plans (C) is an important governance and preparedness activity, ensuring the organization knows what steps to take during an outage, but a written plan alone does not create the technical capability for continuous data availability; it complements, but does not substitute for, the underlying replication infrastructure. Periodic backups (D) capture point-in-time copies at intervals, introducing potential data loss and recovery delay, which does not meet the bar of continuous availability the way real-time synchronous replication does. Synchronous replication is correct.

Reference topic: Replication and Data Archiving - Synchronous Replication for Continuous Data Center Availability.