A storage account uses geo-redundant storage. An application assumes the secondary always contains the last acknowledged primary write. What should the architect explain?

1. GRS automatically makes every application active-active without changes
2. Geographic replication is asynchronous and a forced regional failover can lose recent writes
3. An account's resource name controls replication lag
4. Every geo-redundant secondary is synchronously committed for each write