A hazel-copse teammate provisions Application Gateway because the team needs an API gateway with keys, products, policies, and a developer portal. Which service should they use instead?
Select an answer to reveal the explanation.
Short Explanation
Application Gateway is L7 load balancing—not APIM. Keys, products, policies, and the developer portal live in Azure API Management.
Full Explanation
Azure API Management is the service that provides API subscription keys, products, policy enforcement, and a developer portal. The hazel-copse teammate provisioned Application Gateway thinking it was an API program gateway; Application Gateway is Layer-7 load balancing and WAF-capable routing for web traffic, not an API product catalog with developer self-service subscriptions.
Front Door with WAF strengthens global entry and web application firewall posture but does not issue APIM-style subscription keys or host the APIM developer portal experience partners expect. Application Gateway alone likewise lacks that built-in developer portal and product/subscription model. Traffic Manager is DNS-based traffic routing across endpoints and does not document OpenAPI operations or manage API products and policies.
Exam caveat: distractors often name other Azure networking services—match the feature list (keys, products, policies, portal) to APIM specifically rather than to any service that happens to sit at the edge.
Operational check: create an APIM instance, define a product with a subscription key requirement, attach a sample policy such as rate-limit or set-header, and open the developer portal to confirm hazel-copse partners can discover and subscribe—capabilities Application Gateway will not expose.