A manufacturing company uses Azure SQL Database Hyperscale tier for its IoT telemetry data. The database is in West Europe and must be readable in East US for reporting with a maximum lag of 10 seconds. You configure a failover group with East US as the secondary region. After setup, reporting queries in East US show data that is 5 minutes old. What is the most likely cause?
Setting the secondary type to 'Readable' ensures the secondary is maintained with lower replication lag.
Why this answer
Option B is correct because by default, failover groups use asynchronous replication with a secondary type 'Geo' which may have higher lag. To achieve low lag, you must enable 'Configure secondary type' to 'Readable' (or 'Named' secondary in some configurations) which ensures near-synchronous replication, though still asynchronous. Option A is incorrect because the secondary is readable by default.
Option C is not a standard setting. Option D is unrelated.