Network_Appliance
NS0-157 · Question #152
NS0-157 Question #152: Real Exam Question with Answer & Explanation
The correct answer is B: data LIF of protocol CIFS. This question tests which ONTAP LIF types support cross-node failover and migration, distinguishing NAS protocol LIFs from SAN and infrastructure LIFs.
Network Configuration and Data Access
Question
Which two LIFs are able to failover or migrate to other nodes in the cluster? (Choose two.)
Options
- Acluster LIF
- Bdata LIF of protocol CIFS
- Cdata LIF of protocol FCoE
- Ddata LIF of protocol iSCSI
- Edata LIF of protocol NFS
- Fintercluster LIF
- Gnode management LIF
Explanation
This question tests which ONTAP LIF types support cross-node failover and migration, distinguishing NAS protocol LIFs from SAN and infrastructure LIFs.
Common mistakes.
- A. Cluster LIFs are dedicated to intra-cluster heartbeat and data replication traffic on the private cluster network and are never migrated or failed over - they must remain on their assigned cluster ports.
- C. FCoE data LIFs are bound to specific Converged Network Adapter (CNA) ports and are part of the FC fabric zoning, making cross-node migration impossible - FCoE relies on host-side multipathing for redundancy.
- D. iSCSI data LIFs do not support cross-node migration because iSCSI sessions are stateful and tied to a specific target IP; redundancy for iSCSI is achieved through host-side MPIO across multiple LIFs, not LIF migration.
- F. Intercluster LIFs are dedicated to SnapMirror replication and cluster peering traffic between separate clusters and do not support intra-cluster failover or migration to other nodes.
- G. Node management LIFs are scoped to their specific node for out-of-band administrative access and can only fail over between ports on the same node - they cannot migrate to a different node in the cluster.
Concept tested. ONTAP LIF cross-node failover and migration by protocol type
Reference. https://docs.netapp.com/us-en/ontap/networking/lif_roles95.html
Topics
#LIF migration#LIF failover#FCoE#iSCSI
Community Discussion
No community discussion yet for this question.