You can avoid data corruption when issuing cf forcetakeover -d if the remote node is ________.

You can avoid data corruption when issuing cf forcetakeover -d if the remote node is ________.

• A. In a giveback mode
• B. Fenced off manually
• C. Powered on and accessible
• D. Powered off and inaccessible

Answer: (D)

The capability to use cf forcetakeover -d safely hinges on the remote node not being able to participate in I/O. When the remote node is powered off and inaccessible, it cannot write to disks or cache data that might conflict with the local node’s state. In that scenario, skipping the usual data-consistency checks with -d won’t risk data corruption because there’s no chance the partner will diverge or cause inconsistencies. If the remote node were still online or in a state where it could perform writes or cache data (giveback mode, fenced, or simply accessible), bypassing those checks could lead to data corruption due to potential conflicting writes or unsynced state. Therefore, the safest condition for using the option is when the remote node is powered off and inaccessible.

The capability to use cf forcetakeover -d safely hinges on the remote node not being able to participate in I/O. When the remote node is powered off and inaccessible, it cannot write to disks or cache data that might conflict with the local node’s state. In that scenario, skipping the usual data-consistency checks with -d won’t risk data corruption because there’s no chance the partner will diverge or cause inconsistencies. If the remote node were still online or in a state where it could perform writes or cache data (giveback mode, fenced, or simply accessible), bypassing those checks could lead to data corruption due to potential conflicting writes or unsynced state. Therefore, the safest condition for using the option is when the remote node is powered off and inaccessible.