Select the following statements that are true about unplanned storage failover (SFO). (Choose all that apply)

The failed node is genuinely offline and is not virtually hosted by the HA partner - only its aggregates and volumes are taken over, and the node itself remains unavailable until it is repaired and rejoins the cluster.

Data LIF migration during unplanned failover depends on the LIF failover policy and port configuration; LIFs with a 'disabled' failover policy or lacking suitable home-node ports will not migrate, so migration is not guaranteed to always occur.

During unplanned SFO, the surviving HA partner automatically assumes disk and aggregate ownership from the failed node through the takeover process, allowing it to continue serving data from those aggregates without interruption.

After takeover, the Volume Location Database (VLDB) is updated to record that the failed node's aggregates are now hosted by the surviving partner node, ensuring clients and other cluster components can locate the data correctly.