Hyperflex External SAN Connectivity for Microsoft Clustering
A network engineer is designing a Cisco Hyperflex infrastructure. The infrastructure will be connected to an external SAN fiber channel array and must support Microsoft clustering. Which storage connectivity method must be used to meet these requirements?
Community Votes
75% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests the specific integration mechanism between HCI and legacy shared storage, where the common trap is confusing general network protocols like FCoE with the virtualization-level mapping technique.
This page clarifies that Raw Device Mapping (RDM) is the required storage connectivity method for Cisco HyperFlex when integrating with an external Fibre Channel SAN to support Microsoft clustering workloads.
Many learners select Fibre Channel over Ethernet (FCoE) because it connects Ethernet networks to FC arrays, but FCoE is a transport protocol, not the VM-level connectivity method required for clustering in this context.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Raw Device Mapping (RDM) is the correct answer because it allows a virtual machine to access a block device on the storage array directly. In the context of Cisco HyperFlex integrated with an external SAN, RDM is used to map the external LUNs to the VMs so they can participate in a Microsoft Failover Cluster. This ensures the cluster nodes see the storage as local, which is a strict requirement for Windows Server clustering.Why the Other Options Are Wrong
Fibre Channel over Ethernet (FCoE) is a protocol that encapsulates FC frames within Ethernet, but it does not inherently provide the virtualization abstraction layer needed for the VMs to share the storage in a clustered configuration without additional software-defined storage components. Internet Small Computer Systems Interface (iSCSI) uses TCP/IP and is generally not the primary choice for high-performance FC SAN integration in this specific HCI scenario. Server Message Block (SMB) is a file-sharing protocol, whereas clustering typically requires block-level access for the database or system files.Community Comment Notes
Community consensus strongly supports C, citing Cisco Press documentation on HyperFlex integration. One commenter noted that RDM is the appropriate option for Microsoft external storage specifically. Another user initially suggested FCoE but acknowledged the official guide points to RDM for these specific use cases like booting VMs from legacy SAN.Exam Strategy
When dealing with HCI and external storage integration questions, distinguish between the transport protocol (like FCoE) and the virtualization mapping method (like RDM). For Microsoft clustering scenarios involving external shared storage, RDM is often the key term linking the VM to the SAN.
Frequently Asked Questions
Why not use FCoE for Hyperflex external storage?
FCoE is a transport protocol. While it enables connectivity, RDM is the specific virtualization technology used to map the external LUNs to the VMs for clustering awareness.
Can iSCSI be used for Microsoft clustering in Hyperflex?
While technically possible in some setups, the question specifies an external SAN fiber channel array, making RDM via the FC path the intended architectural solution.