Network Appliance NS0-520 Practice Test - Questions Answers, Page 21

FLI does not support iSCSI connections directly. In order for iSCSI LUNs to be migrated using FLI, the LUN type must be changed to FC. After the migration is complete, the LUN type is changed back to iSCSI.

You can find more information on this link:

https://docs.netapp.com/us-en/ontap-fli/sanmigration/concept_lun_requirements_and_limitations.html

Because NVMe/FC simply swaps command sets from SCSI to NVMe, it is an easy transition to make.

NVMe/FC uses the same FC transport and therefore the same hardware from the host, through the switch and all the way to the NVMe/FC target port on the storage array. Thus, NVMe/FC implementations can use existing FC infrastructure, including HBAs, switches, zones, targets, and cabling.

You can find more information on this link:

https://www.netapp.com/de/media/10681-tr4684.pdf

For clustered Data ONTAP, support for SCSI UNMAP begins in the 8.2 release family. For a LUN to advertise support for and accept SCSI UNMAP commands, enable the space-allocation option on LUNs which you expect to use this feature with.

You can find more information on this link:

https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/ONTAP_and_Windows_SCSI_unmap_and_space_reclamation

Depending on what is selected in the "Trigger" option, Snapshot Autodelete will automatically delete a snapshot when, either the volume space utilized, or the snapshot reserve reaches a threshold capacity specified below.

Automatic deletion of Snapshot copies from flexible volumes Data ONTAP can automatically delete one or more Snapshot copies on the volume, provided the Data ONTAP Snapshot copy autodeletion policy is enabled and set to trigger when the overwrite reserve is nearly full on the volume.

You can find more information on this link:

https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/How_to_use_Snapshot_Autodelete

https://library.netapp.com/ecmdocs/ECMP1217281/html/GUID-98FB8EC4-F3AE-4D25-AF44-E3200AFEB1AB.html

It is recommended that all SVMs in ISCSI configurations have a minimum of two LIF's per node in separate Ethernet networks for redundancy and MPIO across multiple paths.

You can find more information on this link:

https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-sanconf%2FGUID-650DC466-CA3F-4032-8005-078FCEEB52E7.html

The NPV core switch is defined as an upstream switch on which NPIV is enabled. The NPV core switch receives traffic that is passed to it from a downstream switch that has NPV enabled on it. A switch that is in NPV mode does not switch traffic; instead, it passes traffic to the upstream NPV core switch on which NPIV is enabled.

After NPIV is enabled on the core NPV switch, the port should automatically come up (unless there are other issues).

You can find more information on this link:

https://www.cisco.com/c/en/us/td/docs/storage/san_switches/mds9000/sw/rel_3_x/troubleshooting/guide/trblgd/ts_npv.html#wp131957

Broadcast Domains are used to segment and create failover groups automatically... Broadcast Domain do not guarantee redundancy on ISCSI because failover groups are not used on ISCSI.

Both LUN created are inheriting the space reserved parameter from its volume parent, so both LUNs are thick provisioned using 20 GB each one of them and the snapshots have not increased because there has not been any changes since their creation 100GB - 20 GB - 20GB

Create the LUN that you want to use as a boot device, and map it to the igroup as LUN ID 0 You can find more information on this link:

https://library.netapp.com/ecmdocs/ECMP1656701/html/GUID-76BFD6AC-BC2A-419A-9DD3-D98423B2B67F.html