You are configuring FC ports on front-end SAN switches for a 4-node MetroCluster configuration across two data centers. You need to ensure that each data center serves FC LUNs when a FC port goes offline in one data center.
In this scenario, which front-end switch setting must be modified to avoid overlap when a new port comes online?
To ensure each data center serves FC LUNs effectively and avoids any overlap when a new port comes online, the setting related to rejecting duplicate World Wide Port Names (WWPNs) must be modified. Enabling WWPN reject will prevent conflicts by ensuring that any duplicate WWPN attempts are rejected, allowing for smooth operation of the MetroCluster configuration.
It should be C https://docs.netapp.com/us-en/ontap/san-admin/prevent_port_overlap_between_switchover.html
C seems correct thansk FURKA for the link provided
If the FC port on the disaster is not yet removed, the fabric login attempt of the FC port at the surviving site might be rejected due to a duplicate WWPN. This behavior of the FC switches can be changed to honor the login of the previous device and not the existing one. On Cisco you do switch(config)# no fcns reject-duplicate-pwwn vsan 1
A is the right answer
https://docs.netapp.com/us-en/ontap/san-admin/prevent_port_overlap_between_switchover.html