AZ-120 · Question #291
You have an Azure subscription and an Enterprise Agreement (EA). You plan to deploy an SAP on Azure production landscape that will contain the following virtual machines: - One M-series virtual…
The correct answer is D. Request a quota increase for the Azure region. Requesting a quota increase (D) is the right move because Azure subscriptions have default regional core quotas, and the error message explicitly states the quota limit is exceeded - a targeted quota increase resolves this directly, at no cost, without changing any architecture…
Question
You have an Azure subscription and an Enterprise Agreement (EA). You plan to deploy an SAP on Azure production landscape that will contain the following virtual machines:
- One M-series virtual machine with 128 cores
- 15 E-series virtual machines with a total of 300 cores
- 10 D-series virtual machines with a total of 160 cores
During the deployment of the E-series virtual machines, you receive the following error message. Operation results in exceeding quota limits of Core. You need to ensure you can complete the E-series virtual machine deployment. The solution must meet the following requirements:
- Maintain the performance of the SAP landscape.
- Minimize administrative effort.
- Minimize costs.
What should you do?
Options
- AConvert the subscription to Pay-As-You-Go (PAYG).
- BCreate a second subscription and split the virtual machines evenly between both subscriptions.
- CResize the D-series and E-series virtual machines.
- DRequest a quota increase for the Azure region.
How the community answered
(53 responses)- A8% (4)
- B4% (2)
- C2% (1)
- D87% (46)
Explanation
Requesting a quota increase (D) is the right move because Azure subscriptions have default regional core quotas, and the error message explicitly states the quota limit is exceeded - a targeted quota increase resolves this directly, at no cost, without changing any architecture or resources. Converting to Pay-As-You-Go (A) doesn't increase quotas; EA subscriptions already support quota increases, so changing billing models adds cost and complexity with no benefit. Splitting VMs across two subscriptions (B) doubles administrative overhead, complicates SAP landscape networking and management, and still doesn't guarantee the second subscription has sufficient quota. Resizing D-series and E-series VMs (C) would degrade SAP workload performance and violates the sizing requirement, since SAP production systems are sized precisely for workload demands.
Memory tip: When you see "quota exceeded" in Azure, the answer is almost always "request a quota increase" - it's free, fast, and requires no architectural changes. Think of it as asking your landlord for more space rather than moving to a new building or downsizing your furniture.
Topics
Community Discussion
No community discussion yet for this question.