Machine count drives cost under volume-based licensing for a cloud migration

CV0-003 By islever Editorial Last updated

Explain the factors that contribute to capacity planning.

Short answer

C Volume-based licensing meters the number of machines running the software, so the machine count is what drives licensing cost.

Question

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?
  1. The number of cores
  2. The number of threads
  3. The number of machines Correct Answer
  4. The number of sockets

Key Takeaways

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.

Common mistake: 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.

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.

Community Votes

D
57%
C
43%

57% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. Therealjosh 👍 4 Answered 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.
  2. 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.
  3. braveheart22 👍 2 Answered 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.
  4. BigM 👍 1 Answered 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.

Reader comments & corrections

No reader corrections 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.

Budget-threshold notifications are the fastest low-effort way to monitor cloud spend

S-grade

SSH key import is the next check when a remote KVM connection fails after the daemon is verified

S-grade

IaaS web, PaaS database, and SaaS email match a team strong on web servers but short on DBAs

S-grade

Unchanged default passwords are the likely cause when a NATed storage appliance shows foreign files and traffic

S-grade

← Back to CV0-003 Study Guide