What is important to remember about VMs when deploying Direct Attached Storage (DAS) only systems?

Question

Options

• AFailure of a physical server brings down only specific VMs allocated to that specific storage and
• BFailure of a physical server doesn't bring down all the VMs that are installed on that VMware
• CFailure of a VM brings down all the components that are installed on the VM.
• DFailure of a VM doesn't bring down all the components that are installed on the VM.

• A
  92% (34)
• C
  3% (1)
• D
  5% (2)

Explanation

In a DAS-only environment, storage is physically bound to a single server - there is no shared network storage pool - so when a physical server fails, only the VMs running on that server (and using its directly attached storage) go down; VMs on other physical servers with their own DAS remain unaffected. This is the critical exam point: the blast radius of a hardware failure is limited to that server's VMs, not the entire virtual infrastructure.

Why the distractors are wrong:

• B is misleadingly worded - while it is technically true that "not all" VMs in the environment fail, it understates the real impact (all VMs on that server do fail) and omits the key storage-locality concept that A captures precisely.
• C is false - VM failures are isolated by design; a single VM crashing does not cascade to other VMs or all components on the host.
• D is also false - if a VM itself fails, the applications and services running inside that VM absolutely go down with it.

Memory tip: Think of DAS as a "single point of failure per server." The rule is server dies → its VMs die, others survive. Contrast this with SAN/NAS, where storage is shared and a single storage failure can affect VMs across many servers - that contrast is often tested alongside this concept.

No community discussion yet for this question.