In SVM DR failover testing, which prerequisite ensures the destination cluster can take over without IP conflicts?

In SVM DR failover testing, which prerequisite ensures the destination cluster can take over without IP conflicts?

• A. Mediator must be installed
• B. Source SVM must be stopped
• C. Data LIFs must be manually recreated
• D. SVM must remain online

Answer: (B)

The key idea is preventing IP address conflicts when the destination cluster takes over the SVM. To do that, you need to ensure there are no active IPs owned by the source SVM at the moment of failover. Stopping the source SVM releases its IP addresses (the data LIFs) so the destination cluster can claim them without two clusters trying to use the same addresses. If the source SVM were left online, those IPs would still be in use, leading to conflicts and network instability when the destination takes over. The other options don’t address this conflict directly: the mediator is about quorum in certain configurations, data LIFs don’t require manual recreation for this prerequisite, and requiring the SVM to stay online would cause the opposite problem by keeping IPs active on both sides.

The key idea is preventing IP address conflicts when the destination cluster takes over the SVM. To do that, you need to ensure there are no active IPs owned by the source SVM at the moment of failover. Stopping the source SVM releases its IP addresses (the data LIFs) so the destination cluster can claim them without two clusters trying to use the same addresses. If the source SVM were left online, those IPs would still be in use, leading to conflicts and network instability when the destination takes over. The other options don’t address this conflict directly: the mediator is about quorum in certain configurations, data LIFs don’t require manual recreation for this prerequisite, and requiring the SVM to stay online would cause the opposite problem by keeping IPs active on both sides.