You use Azure Cache for Redis Enterprise as a session store for a multi-tenant web app. The business requires that, after a node restart or failover, recovered data must lose no more than one second of writes while minimizing write latency overhead. Which persistence configuration should you use?

The correct option is to enable Append Only File (AOF) persistence with fsync every second. This configuration ensures that data is written to the AOF file at most every second, meeting the requirement of losing no more than one second of writes. It also balances data durability with performance, as fsync always would introduce significant write latency, and fsync every second is less impactful. RDB snapshotting, even every 15 minutes, would allow for up to 15 minutes of data loss, failing to meet the one-second requirement. Disabling persistence entirely and relying only on zone redundancy would not guarantee data recovery within the specified one-second window after a full cache failure or restart.