Exchange DAG Split-Brain Concern – Consistency Validation Query

We recently encountered a transient network partition within our Exchange Database Availability Group. We are now concerned about the possibility of database divergence resulting from a split-brain scenario.

Could you please advise on the recommended approach for validating database consistency across all DAG members prior to returning the environment to normal service? We would particularly appreciate guidance on any built-in health checks or validation cmdlets that should be run at this stage.