Giving the legacy Consumption plan an unbounded timeout
The wrong answers attach an unbounded execution timeout to the legacy Consumption plan, or give that plan an Always On setting. On Consumption the documented maximum is 10 minutes, with a 5-minute default, and Always On is not exposed. Unbounded execution is documented for Flex Consumption, Premium, Dedicated and Container Apps. On the Dedicated plan it applies only once Always On is enabled on the plan that hosts the function app.
See it in a sample questionExpecting Container Apps to expose the Kubernetes API
The wrong answers pick Container Apps, Container Instances or Functions on Container Apps when application teams need direct Kubernetes API and control-plane access. Container Apps is built on Kubernetes but hides the API, and Container Instances runs single container groups with no orchestrator. Azure Kubernetes Service is where the decision tree routes teams that need that access, Helm charts, or a cluster of up to 5,000 nodes on the Standard or Premium tier.
See it in a sample questionTreating Traffic Manager as a proxy
The wrong answers expect Traffic Manager to rewrite headers, route by URL path or fail over in-flight requests. Traffic Manager works only at the DNS level: once it returns a DNS response the client connects directly to the endpoint, and DNS TTL caching slows failover. Header transformation, TLS termination at the edge and re-routing on origin failure belong to Front Door, a global Layer 7 proxy, while path-based routing inside one region belongs to Application Gateway.
See it in a sample questionConfusing Service Endpoints with Private Endpoints
The wrong answers credit a Service Endpoint with what only a Private Endpoint does. A Service Endpoint works from inside the VNet and keeps the service's public IP and FQDN, so on-premises clients cannot use it. A Private Endpoint maps one resource instance to a private IP from the VNet, protects against data exfiltration, and is reachable over ExpressRoute or VPN. Clients resolve that private IP only when the Azure Private DNS zone for the service, such as the one for blob.core.windows.net, is linked to their VNet.
See it in a sample questionMisplacing features between Classic Premium and Premium v2
The wrong answers misplace features between the two Premium tiers of API Management. An upgrade to Premium v2 is assumed to bring multi-region deployment, yet multi-region deployment under a single instance is supported only on Classic Premium, and so is the self-hosted gateway. In the other direction, availability zones, workspaces and the 5 GB built-in cache are treated as Classic Premium exclusives, when Premium v2 has them too. Standard v2 and Consumption have no multi-region deployment either.
See it in a sample question