A SQL Server Always On Availability Group has two replicas in the primary datacenter and one replica in a secondary region. The business requires automatic failover with zero data loss within the primary datacenter and accepts potential data loss and manual intervention for the regional DR. How should you configure the replicas?

This configuration meets the business requirements precisely. Synchronous commit with automatic failover between the two primary-datacenter replicas ensures zero data loss and automatic failover within the primary site. This is because synchronous commit guarantees that transactions are committed on both replicas before the primary acknowledges completion, preventing data loss during failover. Asynchronous commit for the DR replica allows for better performance by not waiting for the remote commit, which is acceptable given the tolerance for potential data loss and manual intervention for regional disaster recovery. Incorrect options: Setting all three replicas to synchronous commit with automatic failover would significantly impact performance due to the latency of committing across regions and is not required given the business's acceptance of data loss for DR. Setting the primary to asynchronous commit would introduce potential data loss even for local failovers, which contradicts the requirement for zero data loss within the primary datacenter. Using synchronous commit for the DR replica and asynchronous for the local secondary, while disabling automatic failover, would not meet the zero data loss and automatic failover requirements within the primary datacenter.