Exam 3V0-21.21 All QuestionsBrowse all questions from this exam
Go to Exam
Question 20

An architect is designing a VMware solution for a customer based on the following information:

✑ The solution must use investments in existing storage array that supports both block and file storage.

✑ The solution must support the ability to migrate workloads between hosts within a cluster.

✑ The solution must support resource management priorities.

✑ The solution must support the ability to connect virtual machines directly to LUNs.

✑ The solution should use existing IPv4 based network infrastructure.

✑ There is no budget for additional physical hardware.

Which two design decisions could the architect make to meet these requirements? (Choose two.)

    Correct Answer: C, D

    The architect is tasked with using an existing storage array that supports block and file storage while maintaining the ability to connect virtual machines directly to LUNs and utilizing the existing IPv4 network infrastructure. Fibre Channel (FC) is not suitable as it does not use IP-based infrastructure, and NFS does not support Raw Device Mapping (RDM) - a feature required for direct access to LUNs. Fibre Channel over Ethernet (FCoE) and iSCSI, however, are both IPv4-based block storage solutions that satisfy all these requirements, including RDM support, resource management priorities, and usage of the existing network infrastructure without requiring additional physical hardware.

Discussion
estornudoOptions: BD

I'd say B and D: NFS 3 and iSCSI FC is not IP NFS4.1 does not support I/O control https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-8A929FE4-1207-4CC5-A086-7016D73C328F.html Starting from vSphere 7.0, VMware no longer supports software FCoE in production environments. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-6B49866F-7005-4099-84AC-4FB2A1A91F64.html

TachinskyOptions: CD

Must be C and D. FC is not IP NFS does not support RDMs (direct access to LUNs) Only Software FCoE is not support anymore. Not FCoE in general

Tachinsky

I need to correct my given answer: Following the requirement: the solution must support block and file storage The answer must be B NFS 3 for file and D iSCSI for Block.

Geoquake

"existing storage array that supports both block and file storage" It's the existing array who supports block and file. There is no prerequisite concerning the solution on that point.

c11Options: CD

C,D for sure FC is not over IP NFS doesn't support RDM FCoE is FC over Ethernet (IP network) iSCSI is over IP network.

diegof1Options: BD

A. FC does not use IP C. Starting from vSphere 7.0, VMware no longer supports software FCoE in production environments. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-6B49866F-7005-4099-84AC-4FB2A1A91F64.html E. NFS 4.1 does not support Storage IO Control https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-8A929FE4-1207-4CC5-A086-7016D73C328F.html

VCIX_ChrisOptions: CD

C and D obviously. "The solution must support the ability to connect virtual machines directly to LUNs." - this rules out non-block storage. "The solution should use existing IPv4 based network infrastructure." - this rules out FC. Left are iSCSI and FCOE, both is IPv4-based block storage.

JailBreak

Sorry but "End of Availability and End of Support for Fibre Channel over Ethernet (FCoE) on Intel Network Controllers from vSphere 6.5 and later" And where is the File Level solution?

MegalodonOptions: BD

A: FC is not IP C: Since vSphere 7 no support for FCoE in production E: NFS 4.1 does not support SIOC

safodzOptions: BD

FCoE not supported

HIC3540Options: CD

RDM is not supported by NFS, and that knocks both versions out. FC violates Req 5. That leaves us with 2 answers verified here: KB / Table 2. https://kb.vmware.com/s/article/79616

Coop99

I agree C & D are the correct answers

MohamedZohairOptions: BD

The answer is BD

FR_WolfmanOptions: CD

Answers are C & D, which are the only possible solutions for using RDM on an IPv4 network A >> FC does not use the IPv4 network infrastructure, it needs a SAN B >> No RDM on NFS 3 C >> FCoE almost the same things as FC, but through IPv4 network (and the proper hardware of course) D >> Of course, you can use RDM on iSCSI (Demo here : https://www.starwindsoftware.com/blog/vmware/rdm-disks-vmware-vsphere-vms-create/) E >> No RDM on NFS 4.1.

hamadakotaOptions: BD

The answer is BD NFS 3 and iSCSI

AlchotOptions: CD

The storage supports file and block but does not say file storage type must be used. ISCSI and FCOE meets all FR

diegof1Options: BD

A. FC does not use IP C. Starting from vSphere 7.0, VMware no longer supports software FCoE in production environments. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-6B49866F-7005-4099-84AC-4FB2A1A91F64.html E. NFS 4.1 does not support Storage IO Control https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-8A929FE4-1207-4CC5-A086-7016D73C328F.html

JailBreakOptions: BD

The answer is always NFS and iSCSI. There are many Storage systems that support both, so only one system will be needed here. The question is NFS v3 or NFS v4.1, I will vote E for v4.1

purulenceOptions: CD

I`m convinced with the explanations regarding RDM is not supported by NFS. ISCSI, FCOE

MasterHowOptions: CD

C & D, no other support RDM and use existing IPv4

Bobob55Options: BD

Block and file so nfs and iscsi