SK0-004 · Question #802
A technician is moving a legacy application that was originally purchased from a company that is no longer in business. The application initially ran on a server that had one single-core processor…
The correct answer is A. Virtualize the hardware and assign CPU cores to match the license. A legacy application licensed for a single-core processor will report a CPU license violation when running on modern multi-core hardware. Virtualization solves this by allowing the administrator to present only the licensed CPU count to the application.
Question
A technician is moving a legacy application that was originally purchased from a company that is no longer in business. The application initially ran on a server that had one single-core processor installed. When moving to a new dual 8-core processor server, the technician receives a message that the application is now out of CPU license. Which of the following should the technician do to get the license functional on the new hardware?
Options
- AVirtualize the hardware and assign CPU cores to match the license
- BRemove one of the processors to match the license
- CTurn off one of the processor cache levels to comply with the license
- DDisable CPU stepping to comply with the license
How the community answered
(19 responses)- A84% (16)
- B11% (2)
- D5% (1)
Why each option
A legacy application licensed for a single-core processor will report a CPU license violation when running on modern multi-core hardware. Virtualization solves this by allowing the administrator to present only the licensed CPU count to the application.
Virtualization platforms such as VMware vSphere or Microsoft Hyper-V allow administrators to configure the exact number of virtual CPUs (vCPUs) assigned to a VM, effectively replicating the single-core environment the legacy license was tied to. This makes the application see only one core regardless of the underlying physical hardware, bringing it back into license compliance without acquiring a new license. Because the original vendor is out of business and no new license can be obtained, virtualization is the only practical path to compliance.
Physically removing a processor wastes expensive hardware resources, requires downtime, and does not address per-core licensing since the remaining processor may still expose more cores than the license allows.
Disabling CPU cache levels affects processor performance but does not change the number of logical processors or cores reported to the operating system, so it has no effect on CPU licensing.
CPU stepping refers to the silicon revision version of a physical processor and is not a configurable setting - it cannot be disabled and has no bearing on core count or license compliance.
Concept tested: Virtualization to resolve legacy CPU licensing constraints
Source: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-technology-overview
Topics
Community Discussion
No community discussion yet for this question.