A. Data SVM
Primary use case: Hosts intercluster LIFs for SnapMirror, SnapVault, and MetroCluster replication traffic.
Data SVMs are designed for NAS/SAN data services but also handle intercluster communication.
D. System SVM
Primary use case: Manages cluster peering, SnapMirror relationships, and other cluster-level communications.
The System SVM is created automatically and is essential for intercluster operations.
Why Not the Others?
B. Node SVM – Does not exist as an SVM type in ONTAP.
C. Admin SVM – Handles cluster management but does not host intercluster LIFs (only System and Data SVMs do).
Key Takeaway:
For replication, disaster recovery, or MetroCluster, ensure intercluster LIFs are properly configured on either:
A Data SVM (for storage-related replication).
Here's how each option relates:
A. Data: ✅ Yes, data SVMs can host intercluster LIFs if the intercluster communication is for SVM-level SnapMirror (SVM peering).
B. Node: ❌ No, "node" is not an SVM type.
C. Admin: ❌ No, "admin" is not an SVM type.
D. System: ✅ Yes, the system (cluster) SVM, also known as the cluster SVM (typically named Cluster), can host intercluster LIFs used for cluster-level SnapMirror.
Admin SVM:
The admin SVM is responsible for cluster management and includes cluster management LIFs and intercluster LIFs.
System SVM:
System SVMs are automatically created for cluster-level communications within an IPspace and also contain service policies that can be used for LIFs, including management and intercluster LIFs.
Intercluster LIFs:
These LIFs are used for communication between different clusters.
C & D :
C) Admin SVM : is the default SVM for the cluster where we can create InterCluster LIFs
D) System SVM : is a default SVM for a new created IPSPACE where we can create intercluster LIFs
When you create a custom IPspace, the system creates a system storage virtual machine (SVM) to serve as a container for the system objects in that IPspace. You can use the new SVM as the container for any intercluster LIFs in the new IPspace. The new SVM has the same name as the custom IPspace.
A, D , A can share with data lif ,D can host for cluster replication
Functionality: Manages cluster-wide settings and provides a single point for cluster administration.
Intercluster Communication: Does not typically host intercluster LIFs, as it is focused on administration rather than data services.
It is Admin and System. Why? Admin allows for intercluster lifs. And if you create a new ipspace with broadcastdomain, it will automatically create a system svm and you can create an intercluster lif.
a) Create intercluster LIFs on the system SVM (Configure intercluster LIFs on shared data ports); d) Data SVMs are commonly used for hosting intercluster LIFs. These LIFs allow communication between clusters for various purposes, such as replication and data mobility. The IP addresses assigned to intercluster LIFs can reside in the same subnet as data LIFs or in a different subnet.
This section is not available anymore. Please use the main Exam Page.NS0-163 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
wm_iv
Highly Voted 1 year, 1 month agoAnish
Most Recent 1 week agoAnish
1 week agoWissemBanks
1 month, 3 weeks agoBlacQ
2 months, 2 weeks ago060f43a
7 months, 1 week agohariramharry
8 months agolicwid
8 months, 1 week agoMr_Anderson
8 months, 3 weeks agogreg4711
9 months agoMagneto
9 months, 1 week agoDREEUW
10 months, 3 weeks agoChainedJedi
1 year, 2 months agoc69f2a8
1 year, 2 months agokombayn
1 year, 2 months agoEiri_F
1 year, 2 months agoviking007
1 year, 5 months agoKhemal
1 year, 5 months ago