Your company has an enterprise application running on Compute Engine that requires high availability and high performance. The application has been deployed on two instances in two zones in the same region in active-passive mode. The application writes data to a persistent disk. In the case of a single zone outage, that data should be immediately made available to the other instance in the other zone. You want to maximize performance while minimizing downtime and data loss. What should you do?

The correct option leverages a regional SSD persistent disk, which provides synchronous replication of data across two zones within a region. This ensures that in the event of a single zone outage, the data is immediately available to the instance in the other zone with minimal downtime and data loss, and high performance due to SSD. Force-attaching the disk allows the standby instance to quickly take over. The other options are less suitable. Hourly snapshots introduce potential data loss of up to an hour. Cloud Storage with gcs-fuse has higher latency than a regional persistent disk, impacting performance. Local SSDs are ephemeral and require manual replication (like rsync), which adds complexity, latency, and potential data loss.