AZ-104 Question #132: Real Exam Question with Answer & Explanation

Question

Hotspot Question You have an Azure Migrate project that has the following assessment properties: Target location: East US Storage redundancy: Locally redundant. Comfort factor: 2.0 Performance history: 1 month Percentile utilization: 95th Pricing tier: Standard Offer: Pay as you go You discover the following two virtual machines: A virtual machine named VM1 that runs Windows Server 2016 and has 10 CPU cores at 20 percent utilization A virtual machine named VM2 that runs Windows Server 2012 and has four CPU cores at 50 percent utilization How many CPU cores will Azure Migrate recommend for each virtual machine? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Answer:

Options

• __typehotspot
• variantdropdown

Explanation

Azure Migrate calculates the recommended CPU cores by determining the effectively utilized cores and multiplying them by the configured comfort factor.

Approach. Azure Migrate uses performance-based sizing. The formula is: Recommended Cores = (Total Cores * Utilization Percentage) * Comfort Factor.

For VM1: It has 10 cores at 20% utilization. The effectively utilized cores are 10 * 0.20 = 2 cores. Applying the comfort factor of 2.0, the recommendation is 2 * 2.0 = 4 cores.

For VM2: It has 4 cores at 50% utilization. The effectively utilized cores are 4 * 0.50 = 2 cores. Applying the comfort factor of 2.0, the recommendation is 2 * 2.0 = 4 cores.

Common mistakes.

• common_mistake. A common mistake is selecting '2', which represents the effectively utilized cores but fails to apply the required comfort factor of 2.0. Another mistake is assuming Azure Migrate will just recommend the original core count without factoring in actual performance utilization.

Concept tested. Azure Migrate Assessment Sizing Logic (Performance-based sizing and Comfort Factor calculation)

Reference. https://learn.microsoft.com/en-us/azure/migrate/concepts-assessment-calculation#calculate-sizing-performance-based

No community discussion yet for this question.