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

 To find the highest latency seen on restore, you need to look at the output of the table that shows the latency measurements for different operations and sizes. The highest latency is 10021 ms, which is the maximum latency for the GET operation with 8KB size. This means that when the users recover files with the Windows Previous Versions tab, they are reading data from the cloud tier that has been tiered using the snapshot-only policy, which causes high latency and slow restores.

• The other latencies are not correct, as they are lower than 10021 ms. The maximum latency for the PUT operation with 4MB size is 10500 ms, but this is not related to the restore operation, as it is writing data to the cloud tier. The maximum latency for the GET operation with 4KB size is 9591 ms, which is slightly lower than 10021 ms. The maximum latency for the GET operation with 32KB size is 7889 ms, which is much lower than 10021 ms. The maximum latency for the GET operation with 256KB size is 7838 ms, which is also much lower than 10021 ms. References :- FabricPool overview, FabricPool requirements, FabricPool best practices, High READ Latency from the fabric pool aggregate.

 The correct way to warm the cache before clients access the cache volume for the first time is to prepopulate the cache volume with data from the origin volume using the flexcache prepopulate start command. This command copies the data blocks from the origin volume to the cache volume in the background, without affecting the client access to the origin volume. The other options are not valid for this scenario because:

• Enabling block-level invalidation using the volume flexcache origin config modify command does not warm the cache, but rather allows the origin volume to invalidate the cached data blocks when they are modified or deleted.
• Copying the data from the origin volume to the cache volume with the NetApp XCP Migration Tool is not recommended, as it can cause data inconsistency and performance degradation. XCP is a data migration tool that can copy data between different types of volumes, such as FlexVol and FlexGroup, but not between FlexCache and origin volumes.
• Synchronizing the origin and cache first with the volume flexcache sync-properties command does not warm the cache, but rather ensures that the cache volume inherits the properties of the origin volume, such as size, security style, and export policy. References :- Prepopulate a FlexCache volume, FlexCache volume concepts, FlexCache volume best practices

 The number of ISCSI LIFs that will be created from the SVM setup wizard, as shown in the exhibit, is 16. This is because the LIFs per node field is set to 2, and there are 4 nodes in the cluster. Therefore, the total number of LIFs is 2 x 4 8 for each SVM, and since there are two SVMs, the total number of LIFs is 8 x 2 16. The other options are incorrect because they do not match the calculation based on the exhibit. References :- Configure an SVM for iSCSI, Configure iSCSI on an existing SVM