H13-629_V3.0 · Question #91
In the SmartVirtualization feature, eDevlun and external lun correspond to each other, and eDevlun is the external lun
The correct answer is B. False. B is correct because the statement contains a critical error in its second clause: while eDevLUN and the external LUN do correspond to each other, eDevLUN is not the external LUN - it is the internal virtual LUN created on the virtualizing storage system that maps to and…
Question
In the SmartVirtualization feature, eDevlun and external lun correspond to each other, and eDevlun is the external lun
Options
- ATrue
- BFalse
How the community answered
(27 responses)- A15% (4)
- B85% (23)
Explanation
B is correct because the statement contains a critical error in its second clause: while eDevLUN and the external LUN do correspond to each other, eDevLUN is not the external LUN - it is the internal virtual LUN created on the virtualizing storage system that maps to and represents the external LUN. They are related but distinct objects.
Option A (True) is wrong because it conflates two separate logical entities. The external LUN resides on the external (third-party) storage array, whereas eDevLUN is the local device-side representation within the SmartVirtualization framework - treating them as the same thing misrepresents the architecture.
Memory tip: Think of eDevLUN as a "shadow" or "proxy" - it mirrors the external LUN internally, but a shadow is not the object casting it. The "e" in eDevLUN stands for the external association, not that it is the external LUN.
Topics
Community Discussion
No community discussion yet for this question.