A disaster causes a FlexGroup volume to be unrecoverable, but it was protected by a SnapMirror relationship. You solve the issue, and the source is operational.
Now, you want to return to serving the data from the original source.
In this scenario, what do you do next?
When you want to return to serving data from the original source after a disaster, you need to remove the existing SnapMirror relationship to ensure that the source is no longer dependent on the backup destination. Therefore, the correct step would be to delete the SnapMirror relationship.
https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.pow-fg-mgmt%2FGUID-576192B0-18B8-40D3-AA3E-FC34415DC4F7.html Reverse a SnapMirror relationship between FlexGroup volumes during disaster recovery Steps On the original destination FlexGroup volume, remove the data protection mirror relationship between the source FlexGroup volume and the destination FlexGroup volume: snapmirror delete -destination-path svm_name:volume_name cluster2::> snapmirror delete -destination-path vsd:dst On the original source FlexGroup volume, remove the relationship information from the source FlexGroup volume: snapmirror release -destination-path svm_name:volume_name -relationship-info-only After deleting a SnapMirror relationship, you must remove the relationship information from the source FlexGroup volume before attempting a resynchronization operation. cluster1::> snapmirror release -destination-path vsd:dst -relationship-info-only true
This is down to wording , trys to trip you up with whether its an "Initialization" or a "Deletion" of the SnapMirror relationship, AS above comment, you are deleting the SnapMirror relationship betweeen src & dst , then resynching .Not Inializng,
Correct Answer D ; delete initial relationship