Which statement best describes how to verify replication health during maintenance?

Which statement best describes how to verify replication health during maintenance?

• A. DNS resolution
• B. NTP offset
• C. SVM creation
• D. Replication health metrics

Answer: (D)

The ability to verify replication health during maintenance rests on examining replication health metrics. These metrics directly reflect how well the replication relationship is performing, showing whether the secondary copy is keeping up with the primary, and whether any errors or inconsistencies have occurred during or after maintenance activities. You’ll typically look at indicators like the replication status (healthy, suspended, or degraded), lag time or recovery point objective (RPO), the last successful transfer time, transfer rate, and any error counts or verification results. If these metrics indicate healthy, up-to-date replication with no errors, you can be confident the maintenance didn’t disrupt data protection. If there’s increased lag, failed transfers, or errors, you’d investigate and possibly resynchronize before relying on replication for recovery. While DNS resolution and NTP offset matter for overall system operation and timekeeping, they don’t measure the actual health of the replication stream. Creating a new SVM is a setup action and doesn’t reflect ongoing replication health.

The ability to verify replication health during maintenance rests on examining replication health metrics. These metrics directly reflect how well the replication relationship is performing, showing whether the secondary copy is keeping up with the primary, and whether any errors or inconsistencies have occurred during or after maintenance activities. You’ll typically look at indicators like the replication status (healthy, suspended, or degraded), lag time or recovery point objective (RPO), the last successful transfer time, transfer rate, and any error counts or verification results. If these metrics indicate healthy, up-to-date replication with no errors, you can be confident the maintenance didn’t disrupt data protection. If there’s increased lag, failed transfers, or errors, you’d investigate and possibly resynchronize before relying on replication for recovery. While DNS resolution and NTP offset matter for overall system operation and timekeeping, they don’t measure the actual health of the replication stream. Creating a new SVM is a setup action and doesn’t reflect ongoing replication health.