A company wants to create an API to authorize users by using JSON Web Tokens (JWTs). The company needs to support dynamic access to multiple AWS services by using path-based routing. Which solution…

Deploying an Application Load Balancer (ALB) as the primary backend for API Gateway might introduce redundant Layer 7 routing if API Gateway is already handling path-based routing, and 'Configure IAM' is too vague for JWT authorization specifics.

An API Gateway HTTP API, while supporting JWTs, typically offers fewer advanced routing and integration features compared to a REST API for complex dynamic access to multiple services.

An Amazon API Gateway REST API supports JWT authorization via custom authorizers or Cognito and can implement path-based routing to direct requests to different backend integrations. For high-performance and stable private integration with backend resources within a VPC, a Network Load Balancer (NLB) can be used as a target for a VPC Link, providing a static IP endpoint for API Gateway to access multiple AWS services.

A Network Load Balancer (NLB) operates at Layer 4 and does not provide path-based routing functionality itself, making it unsuitable if the load balancer is expected to perform this routing.