You are deploying two virtual servers, one heavily used database server and the other lightly used printer server. Which virtual CPU configuration would you recommend?

You are deploying two virtual servers, one heavily used database server and the other lightly used printer server. Which virtual CPU configuration would you recommend?

• A. One virtual CPU for the database server and two virtual CPUs for the print server
• B. Two virtual CPUs for the database server and two virtual CPUs for the print server
• C. Two virtual CPUs for the database server and one virtual CPU for the print server
• D. Three virtual CPUs for the print server and two virtual CPUs for the database server

Answer: (C)

Matching CPU resources to workload is the key. A heavily used database benefits from multiple CPUs to run parallel queries, handle many connections, and reduce wait times. Providing two vCPUs gives the database the needed parallelism and capacity. The printer service is lightly used and typically not CPU-bound, so one vCPU is usually enough to handle its tasks without wasting host resources. Allocating more CPUs to the printer would waste cycles and could complicate scheduling for the overall system. So, two virtual CPUs for the database and one for the printer best balances performance for the heavy workload with efficient resource use for the light workload. If demand grows, you can scale the database up further as needed.

Matching CPU resources to workload is the key. A heavily used database benefits from multiple CPUs to run parallel queries, handle many connections, and reduce wait times. Providing two vCPUs gives the database the needed parallelism and capacity. The printer service is lightly used and typically not CPU-bound, so one vCPU is usually enough to handle its tasks without wasting host resources. Allocating more CPUs to the printer would waste cycles and could complicate scheduling for the overall system. So, two virtual CPUs for the database and one for the printer best balances performance for the heavy workload with efficient resource use for the light workload. If demand grows, you can scale the database up further as needed.