HAT-420 · Question #105
A customer would like to add the File Module option to their Hitachi Unified Storage (HUS) system to provide files services. Which three types of connectivity are required from the File Module?…
Correct Answer: A, B, D The Hitachi HUS File Module requires FC to HUS (A) because the File Module accesses block storage from the HUS array over Fibre Channel - it sits in front of the HUS and virtualizes block storage into file services. IP to SMU (B) is required because the…
Question
A customer would like to add the File Module option to their Hitachi Unified Storage (HUS) system to provide files services. Which three types of connectivity are required from the File Module? (Choose three.)
Options
- AFC to HUS
- BIP to SMU
- CFC to Servers
- DIP to Servers
- EFC to SMU
Explanation
Correct Answer: A, B, D
The Hitachi HUS File Module requires FC to HUS (A) because the File Module accesses block storage from the HUS array over Fibre Channel - it sits in front of the HUS and virtualizes block storage into file services. IP to SMU (B) is required because the Storage Management Unit communicates with and manages the File Module over an IP network connection. IP to Servers (D) is required because NAS file services (NFS/CIFS/SMB) are delivered to client servers over an IP/Ethernet network - that's the fundamental nature of file-based storage access.
Why the distractors are wrong:
- C (FC to Servers) is wrong because file services use IP protocols, not Fibre Channel - FC to servers is a SAN/block storage pattern, not a NAS/file pattern.
- E (FC to SMU) is wrong because the SMU is a management appliance that communicates over IP, not FC.
Memory tip: Think of the File Module as a "translator" sitting in the middle - it speaks FC inward (to the HUS block storage), IP outward (to servers for file access), and IP upward (to the SMU for management). The rule of thumb is: management = IP, file clients = IP, back-end storage = FC.
Topics
Community Discussion
No community discussion yet for this question.