CV0-003 · Question #153
A hypervisor that prevents vendor lock-in is:
The correct answer is C. an open source hypervisor. Open source hypervisors prevent vendor lock-in because they are not controlled by a single commercial vendor, allowing workload portability across hardware and providers.
Question
A hypervisor that prevents vendor lock-in is:
Options
- Aa proprietary hypervisor.
- Ban integrated hypervisor.
- Can open source hypervisor.
- Da framework hypervisor.
How the community answered
(38 responses)- B5% (2)
- C92% (35)
- D3% (1)
Why each option
Open source hypervisors prevent vendor lock-in because they are not controlled by a single commercial vendor, allowing workload portability across hardware and providers.
A proprietary hypervisor is controlled exclusively by one vendor, which is the definition of vendor lock-in - customers become dependent on that vendor's roadmap, pricing, and compatibility decisions.
An integrated hypervisor is typically embedded within a vendor's hardware or platform stack, deepening dependency on that specific vendor's ecosystem rather than reducing it.
Open source hypervisors such as KVM and Xen are freely available and community-developed, meaning organizations are not tied to a specific vendor's licensing, pricing, or support lifecycle. This portability allows workloads to move across different hardware platforms and cloud providers without proprietary dependencies.
A 'framework hypervisor' is not a recognized standard industry classification and does not describe any known hypervisor category associated with portability or open standards.
Concept tested: Open source hypervisors as a vendor lock-in mitigation strategy
Source: https://www.kernel.org/doc/html/latest/virt/kvm/index.html
Topics
Community Discussion
No community discussion yet for this question.