Machine count drives cost under volume-based licensing for a cloud migration
Explain the factors that contribute to capacity planning.
AnswerCorrect answer: C — Volume-based licensing meters the number of machines running the software, so the machine count is what drives licensing cost.
A systems administrator is planning to migrate to a cloud solution with volume-based licensing. Which of the following is most important when considering licensing costs?
57% of anonymous learners picked answer D.
Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
CompTIA's capacity planning templates separate per-user, socket-based, core-based, and volume-based licensing, so volume must mean quantity of instances, not processor sockets or cores.
A migration is planned to a cloud solution licensed by volume. Volume-based licensing charges by the quantity of licensed instances deployed, so the number of machines running the software is what determines the bill, unlike socket-based or core-based templates that meter processors.
Choosing sockets (D) imports the definition of socket-based licensing, which is a distinct template on the same objective list and therefore cannot also describe volume-based licensing.
Community Discussion (4 comments)
BigM👍 1Selected: C
Explanation: In a volume-based licensing model, costs are typically determined by the number of instances (machines) running the software. ✔ Many cloud providers charge based on per-instance or per-VM usage. ✔ If licensing is volume-based, the total cost scales with the number of deployed machines. ✔ Tracking active machine instances is crucial for cost optimization.
braveheart22👍 2Selected: C
The volume-based licensing model typically charges based on the number of instances rather than CPU sockets. Many software vendors base their licensing on the total number of instances (or virtual machines) where the software will be installed or used. However, some specific software products, particularly those related to server or enterprise applications, may charge based on CPU sockets or cores. It’s important to check the specific licensing terms of the software in question, as different vendors may have different criteria for their volume-based licensing.
54a6b25👍 3
C. The number of machines Explanation: Volume-based licensing: This type of licensing model typically charges based on the number of instances (machines) being used. The cost is determined by the total count of virtual machines (VMs) or servers that are running.
Therealjosh👍 4Selected: D
D. The number of sockets In volume-based licensing for cloud solutions, licensing costs are typically based on the number of CPU sockets allocated to virtual machines. Sockets refer to physical or virtual CPU sockets assigned to a virtual machine instance. The more sockets you use, the higher the licensing costs are likely to be. Therefore, the number of sockets is the most important factor to consider when estimating and managing licensing costs in a cloud environment with volume-based licensing.
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Log in to comment, report an error, or add a note about this question.
Expert Analysis
Why the Answer Is Correct
Volume-based licensing, in the sense used by CompTIA's standard licensing templates, prices the software by the volume of licenses consumed, which for server software in the cloud means each instance or machine running it. Double the VMs and the license count doubles, regardless of how big each machine is. When planning the migration budget, tracking how many machines will run the licensed software is therefore the cost driver.
Why the Other Options Are Wrong
A, the number of cores, and D, the number of sockets, each describe different licensing templates, core-based and socket-based respectively, which the same objective lists as separate models from volume-based. B, the number of threads, is not a licensing unit in any standard template and is a property of the CPU architecture rather than of the license count.
Community Comment Notes
54a6b25 argues that volume-based licensing charges per instance, with cost determined by the count of VMs or servers running the software. BigM concurs, noting cloud providers bill per instance and that tracking active machine instances is the cost lever. Therealjosh favors sockets, but that reading collapses volume-based into socket-based licensing, which the objective list defines as a distinct template; braveheart22 sides with C on the same reasoning.