Choose the best description of the main function of an API Gateway.
Think about how clients interact with many services through one interface.
An API Gateway provides a unified entry point for clients, routing requests to appropriate backend services. It does not store data or replace load balancers but complements them.
Select the API Gateway pattern designed to combine responses from several services into a single client response.
Think about a pattern that collects and merges data from different sources.
The Aggregator Pattern collects data from multiple backend services and combines it into one response for the client, simplifying client interactions.
Identify the way an API Gateway contributes to system scalability.
Consider how reducing backend load can help scale the system.
API Gateways can cache frequent responses, which reduces the number of calls to backend services, thus improving scalability and performance.
Choose the main disadvantage or risk introduced by adding an API Gateway.
Think about what happens if the gateway stops working.
An API Gateway centralizes traffic, so if it fails and lacks redundancy, it can bring down access to all services, making it a critical point to protect.
Calculate the approximate concurrent connections the API Gateway should support during peak load.
Calculate total requests during peak, then estimate how many happen simultaneously assuming average request duration.
10,000 users × 50 requests/hour = 500,000 requests/hour. Peak is 2 hours, so 500,000 requests spread over 2 hours = 250,000 requests/hour during peak. That is about 69 requests per second (250,000 / 3600). Assuming each request lasts 100ms (0.1s), concurrent connections = 69 × 0.1 = ~7. So 700 is a safe estimate considering bursts and overhead.