NS0-162 Exam Dumps : NetApp Certified Data Administrator (ONTAP)

The performance capacity report shows the current and optimal performance metrics for the CPU resource on each node of the cluster. The current metrics reflect the actual workload on the resource, while the optimal metrics reflect the workload that would result in the best performance. The performance capacity, or headroom, is the difference between the current and optimal metrics. A low or negative headroom indicates that the resource is over utilized and may experience performance degradation. The exhibit shows that both nodes have negative headroom for the CPU resource, which means that the CPU has been over utilized. A storage failover event will cause performance issues, as the surviving node will have to handle the workload of both nodes, which will further reduce the headroom and increase the latency. References :- Identify remaining performance capacity, What is Performance Capacity in ONTAP 9 and Unified Manager?

The igroup is a logical grouping of initiators that can access a set of LUNs. The igroup must contain the IQNs (iSCSI Qualified Names) or WWPNs (World Wide Port Names) of the initiators that need to access the LUNs. In this scenario, the igroup named “ESX” has the iSCSI protocol and the VMware OS type, but it does not have any initiators listed. This means that the VMware hosts cannot authenticate and connect to the LUNs in the SVM. To resolve this issue, the igroup must be populated with the correct initiators that match the VMware hosts. This can be done by using the igroup add command or the System Manager GUI12. References :- Create an igroup, Add initiators to an igroup

 To make the destination NAS volume writable, you need to break the SnapMirror relationship using the snapmirror break command from the destination cluster, and then use the volume mount command to mount the NAS volume in the NFS namespace. Breaking the SnapMirror relationship will make the destination volume read/write and allow clients to access the latest Snapshot copy. Mounting the volume in the NFS namespace will make the volume visible to the clients and enable them to access the data. The other options are not correct because:

• Deleting the SnapMirror relationship from the destination cluster will not make the destination volume writable, but rather remove the relationship configuration and history. This will prevent future resynchronization or updates of the relationship.
• Breaking the SnapMirror relationship using the snapmirror break command from the source cluster will not work, because the source cluster is unavailable due to networking issues. The command must be run from the destination cluster. References :- Break the SnapMirror relationship, Mount a volume in the namespace