AWS API Gateway limits the number of requests a client can make. What is the default behavior when the limit is exceeded?
Think about how APIs usually inform clients about rate limits.
AWS API Gateway returns a 429 error to inform clients they have exceeded the allowed request rate, so clients can retry later.
You have microservices running on your own servers and need a gateway that supports plugins and custom logic. Which gateway fits best?
Consider which gateway is open-source and supports plugins.
Kong Gateway is open-source, supports plugins, and can run on-premises, making it ideal for customizable microservices environments.
Choose the correct Nginx config to forward incoming requests to a backend service running on localhost port 8080.
server {
listen 80;
location / {
# Your config here
}
}Look for the directive that forwards requests to another server.
The proxy_pass directive forwards requests to the backend. Using http://localhost:8080/ is correct for a local backend on port 8080.
To protect your APIs from unauthorized access, which Kong feature can you enable quickly without coding?
Think about standard authorization protocols supported by API gateways.
Kong Gateway offers an OAuth 2.0 plugin that can be enabled to secure APIs with token-based authorization without custom code.
You want low latency and high availability for your microservices across multiple AWS regions. How should you deploy AWS API Gateway?
Consider AWS services that help route users to the nearest region.
Deploying API Gateway in each region combined with Route 53 latency-based routing ensures users connect to the closest API Gateway, reducing latency and improving availability.