CAS-003 · Question #862
A company's human resources department recently had its own shadow IT department spin up multiple VM guests on one host, each hosting a mixture of differently labeled data types (confidential and…
The correct answer is A. Vulnerabilities associated with a single platform hosting multiple data types on VMs should have. The core problem is that the shadow IT department co-located data of different classification levels (confidential and restricted) on the same VM guest. This creates risk because a compromise, misconfiguration, or insider threat affecting one data type could expose the other…
Question
A company’s human resources department recently had its own shadow IT department spin up multiple VM guests on one host, each hosting a mixture of differently labeled data types (confidential and restricted) on the same guest. Which of the following cloud and virtualization considerations would BEST address the issue presented in this scenario?
Options
- AVulnerabilities associated with a single platform hosting multiple data types on VMs should have
- BVulnerabilities associated with maintaining and patching multiple hypervisors.
- CType 1 vs. Type 2 hypervisor approaches should have been considered.
- DVulnerabilities associated with shared hosting services provided by the IT department should
How the community answered
(29 responses)- A72% (21)
- B14% (4)
- C3% (1)
- D10% (3)
Explanation
The core problem is that the shadow IT department co-located data of different classification levels (confidential and restricted) on the same VM guest. This creates risk because a compromise, misconfiguration, or insider threat affecting one data type could expose the other. The key consideration that should have been addressed is that hosting mixed-sensitivity data on shared VMs on a single host violates data segregation principles. Each data classification should reside on isolated VMs or separate hosts to enforce access controls and limit blast radius. The other choices address hypervisor patching (B) and hypervisor type selection (C), which are valid considerations but do not directly address the specific mixing of classified data types raised in this scenario.
Topics
Community Discussion
No community discussion yet for this question.