Which three attributes would you specify when creating a LUN? (Choose three)
A.
The host operating system of the system attached to LUN.
B.
The version of Data ONTAP
C.
The size of the LUN.
D.
The path to the LUN.
Explanation:
https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_lun.1.htmlThe usage for lun create is shown below. Options not in brackets are mandatory.
lun create -s size -t ostype [ -o noreserve ] [ -e space_alloc ] lun_path
This usage of the lun create command should be employed to create a new LUN of given size,
with initiallyzero contents. The LUN is created at the lun_path given. No file should already exist at
the given lun_path. Thedirectory specified in the lun_path must be a qtree root directory.
The size is specified in bytes. Optionally, a number followed by a one-character multiplier suffix
can be used: c(1), w (2), b (512), k (1024), m (k*k), g (k*m), t (m*m).
The size of the created LUN could be larger than the size specified, in order to get an integral
number ofcylinders while reporting the geometry using SAN protocols.
The size of the LUN actually created is reported if it is different from that specified in the
command.
The mandatory ostype argument is one of: solaris (the LUN will be used to store a Solaris raw disk
in a singleslicepartition), windows (the LUN will be used to store a raw disk device in a singlepartition Windows diskusing the MBR (Master Boot Record) partitioning style), hpux (the LUN will
be used to store HP-UX data), aix(the LUN will be used to store AIX data), vld (the LUN contains a
SnapManager VLD), linux (the LUN will beused to store a Linux raw disk without any partition
table), netware (the LUN will be used to store NetWaredata), vmware (the LUN will be used to
store VMware data), windows_gpt (the LUN will be used to storeWindows data using the GPT
(GUID Partition Type) partitioning style), windows_2008 (the LUN will be used tostore Windows
data for Windows 2008 systems), openvms (the LUN will be used to store Open-VMS data),xen
(the LUN will be used to store Xen data), hyper_v (the LUN will be used to store Hyper-V data),
solaris_efi(the LUN will be used to store Solaris_EFI data).
By default, the LUN is space-reserved. To manage space usage manually, -o noreserve can be
specified.
Using this option will create a LUN without any space being reserved. Provisioning threshold
events can beenabled by specifying -e space_alloc option. This option has to be used in
conjunction with -o noreserve.