H13-511_V5.5 · Question #92
Which of the following descriptions about the storage architecture of FusionCompute is correct?
The correct answer is B. After the storage resource is encapsulated into data storage and associated with the host, it is. Option B correctly describes the provisioning workflow in FusionCompute: once a storage resource (such as a LUN or NFS share) is encapsulated into a datastore and that datastore is associated with a compute host, virtual machines on that host can then allocate and use virtual…
Question
Which of the following descriptions about the storage architecture of FusionCompute is correct?
Options
- AThe LUNs partitioned on the FusionStorage Block can be encapsulated as data storage
- BAfter the storage resource is encapsulated into data storage and associated with the host, it is
- CStorage resources are FusionCompute's unified encapsulation of storage units in storage
- DThe physical storage medium that provides storage space for virtualization is called a storage
How the community answered
(63 responses)- A13% (8)
- B78% (49)
- C3% (2)
- D6% (4)
Explanation
Option B correctly describes the provisioning workflow in FusionCompute: once a storage resource (such as a LUN or NFS share) is encapsulated into a datastore and that datastore is associated with a compute host, virtual machines on that host can then allocate and use virtual disks from it - this is the required sequence before VM storage becomes accessible.
Option A is incorrect because FusionStorage Block LUNs cannot be directly encapsulated as datastores in the same way; FusionStorage is integrated through its own storage resource type, and the statement oversimplifies the association model.
Option C confuses the two layers: storage resources are the raw units (LUNs, NFS shares) presented to FusionCompute, while data storage (datastores) is FusionCompute's unified encapsulation of those resources - C has the definition backwards.
Option D misidentifies terminology: physical storage media (disk arrays, SAN devices) are called storage devices or storage pools, not "storage resources" in FusionCompute's architecture.
Memory tip: Think of it as a 3-step pipeline - Resource → Datastore → Host association - you must complete all three steps before a VM can write a single byte. Option B is the only choice that correctly reflects this dependency chain.
Topics
Community Discussion
No community discussion yet for this question.