You need to set up Microsoft SQL Server on GCP. Management requires that there's no downtime in case of a data center outage in any of the zones within a GCP region. What should you do?

The correct solution is to set up SQL Server Always On Availability Groups (AGs) using Windows Failover Clustering and place nodes in different zones. This configuration provides high availability and disaster recovery for SQL Server by replicating databases across multiple instances in different failure domains (zones). In case of a zone outage, the AG automatically fails over to a healthy replica in another zone, ensuring no downtime. Configuring a Cloud SQL instance with high availability enabled is incorrect because Cloud SQL for SQL Server does not support Always On Availability Groups directly for this level of multi-zone resilience. Cloud Spanner is a globally distributed database, but the requirement is specifically for Microsoft SQL Server, making it an unsuitable choice. Setting up SQL Server on Compute Engine with Always On Availability Groups and placing nodes in different subnets is a partial solution; the critical part for zone-level resilience is placing nodes in different zones, not just different subnets within the same zone.