Answer: Last Sync Time

## Explanation When monitoring for replication delays that could impact the Recovery Point Objective (RPO) in a geo-zone-redundant storage (GZRS) configuration for Azure Data Lake Storage, the **Last Sync Time** metric is the most appropriate choice for the following reasons: ### Why Last Sync Time (Option D) is Correct: - **Direct RPO Measurement**: The Last Sync Time metric provides the exact timestamp of the last successful synchronization between the primary and secondary regions. This directly indicates how current the data is in the secondary region. - **RPO Impact Assessment**: By comparing the Last Sync Time with the current time, you can calculate the potential data loss window. If the Last Sync Time is significantly behind, it indicates replication delays that directly impact RPO. - **Azure Documentation Support**: Microsoft's official documentation specifically recommends monitoring Last Sync Time for geo-redundant storage configurations to track replication health and RPO compliance. - **Real-time Visibility**: This metric gives immediate insight into the replication lag, allowing proactive identification of issues before they escalate. ### Why Other Options Are Less Suitable: **Option A (5xx: Server Error errors)**: - While important for overall system health monitoring, server errors don't directly measure replication delays or RPO impact. They indicate service availability issues but not the synchronization status between regions. **Option B (Average Success E2E Latency)**: - This metric measures the end-to-end latency of storage operations but doesn't specifically track inter-region replication delays. It's more relevant for performance monitoring rather than RPO compliance. **Option C (Availability)**: - Availability metrics track whether the storage service is accessible, but they don't provide information about data synchronization status between regions or replication delays affecting RPO. ### Best Practice Recommendation: For comprehensive monitoring of GZRS replication health, it's recommended to monitor Last Sync Time alongside other metrics like replication status and error rates. However, for specifically identifying replication delays that impact RPO, Last Sync Time remains the definitive metric according to Azure best practices and documentation.

Author: LeetQuiz Editorial Team