An elder-hedge backend lives on a private VNet and the gateway must sit with it in more than one region. Which APIM choice meets that requirement?
Select an answer to reveal the explanation.
Short Explanation
Private VNet plus multi-region gateway? That is Premium (or Premium v2)—Consumption will not inject into the elder-hedge network the way you need.
Full Explanation
When an elder-hedge backend lives on a private VNet and the gateway must sit with it across more than one region, choose Premium-class API Management (including Premium v2 where VNet injection is the documented path). Those tiers support the network injection and multi-region gateway footprint required for private backends with regional presence, which is exactly the networking shape this municipal scenario describes.
Consumption uses a serverless public gateway model without that private multi-region VNet injection shape, so it fails the stated network requirement even though it can be attractive for bursty public APIs. Developer tier is nonproduction regardless of any attached network diagram or aspirational architecture sketch. Front Door alone is a global entry and CDN-style service; it does not replace APIM’s API products, policies, subscriptions, and developer portal for managing the city’s API program in front of a private origin.
Exam caveat: map networking requirements (VNet integration, multi-region gateway) to Premium-class tiers early—trying to bolt private multi-region behavior onto Consumption or Developer is a common AZ-204 trap when distractors advertise “cheaper” tiers.
Operational check: deploy Premium (or Premium v2) with VNet integration in each required region, confirm the gateway can reach the private elder-hedge backend on private addresses, verify health across regions, and ensure callers use the APIM gateway hostname rather than any public origin URL.