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

To cache on-premises ONTAP volumes into the cloud with Cloud Volumes ONTAP, you need to use the FlexCache feature, which creates a writable, persistent cache of a data volume that is consistent and coherent with its original data set and stored in a remote location. FlexCache supports both SMB and NFS protocols, which are the traditional file access protocols for Windows and UNIX/Linux systems respectively. You can control file access using UNIX-style permissions, NTFS-style permissions, or a mix of both. Clients can access the same files using both SMB and NFS protocols123.

• NVMe and iSCSI are not supported by FlexCache, as they are block protocols that run on standard Ethernet networks. FlexCache is a file-based solution that works with file protocols only12. References :- Client protocols | NetApp Documentation, Client protocols - NetApp, Cloud Volumes ONTAP for AWS: Storage for the Cloud Era.

 FabricPool is a feature of ONTAP that allows you to tier cold data from a local tier (aggregate) to a capacity tier (object storage) in the cloud or on-premises. ONTAP 9.8 supports four types of capacity tiers: AWS S3, Azure Blob, Google Cloud Storage, and ONTAP S3. StorageGRID is a NetApp product that provides on-premises S3 object storage. Therefore, both StorageGRID and ONTAP S3 are supported as capacity tiers for FabricPool aggregates in ONTAP 9.8. SWIFT Object Store and NFS Export are not supported as capacity tiers for FabricPool aggregates. References :- Considerations and requirements for using FabricPool, Storage Efficiencies, FabricPool with StorageGRID Recommendation Guide

 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.