AZ-305 Practice Question 60: API Gateway on Premises Traffic
Microsoft Azure Solutions Architect Expert (AZ-305) · Test 6 · question 10 of 10
An insurer exposes APIs from backends in Azure and from a datacenter. A regulation requires that calls to the datacenter APIs are processed inside the datacenter and never travel through Azure gateways. The API team wants one management plane for definitions, policies, products and the developer portal, and does not want to operate separate API management platforms.
What should you include in the design?
Show answer and explanation
Answer:
The self-hosted gateway is a containerized version of the API Management gateway that you run in your own environment, including on-premises. It is configured from the same cloud-based management plane, so definitions, policies, products and the developer portal stay in one Azure API Management instance, while API traffic to the backends is processed locally in the datacenter and does not pass through an Azure gateway.
Option A adds a managed gateway in Azure. It is a multi-region deployment for latency and availability, but the traffic is still handled by gateways in Azure, which the regulation forbids.
Option B keeps traffic local but creates several platforms with duplicated definitions to keep in sync, which is the operational burden the team wants to avoid.
Option D is a regional layer 7 load balancer and firewall for web applications hosted in Azure. It does not provide API management features such as products, policies or a developer portal.
Reference: Self-hosted gateway overview