Which of the following best describes the primary role of a reverse proxy in a web system?
Think about what a reverse proxy does between clients and servers.
A reverse proxy sits in front of backend servers, forwarding client requests to them. It can also balance load, cache responses, and improve security.
Where is a reverse proxy typically placed in a web application architecture?
Consider the flow of requests from users to servers.
A reverse proxy is placed between clients and backend servers to intercept and manage incoming requests.
How does a reverse proxy help scale backend servers in a high-traffic web application?
Think about how load balancing works in web systems.
A reverse proxy can distribute client requests across multiple backend servers, balancing load and improving scalability.
Which is a common tradeoff when introducing a reverse proxy into a system?
Consider both benefits and costs of adding components in a network path.
While a reverse proxy adds an extra step in request handling, it improves security, caching, and load balancing, which outweighs the slight latency increase.
A reverse proxy handles 10,000 requests per second. Each request averages 500KB response size. What is the approximate outgoing bandwidth needed for the reverse proxy?
Calculate bandwidth = requests per second × response size in bits.
10,000 requests/s × 500KB = 5,000,000 KB/s = 5 GB/s. Convert to bits: 5 GB/s × 8 = 40 Gbps. But 500KB is 0.5MB, so 10,000 × 0.5MB = 5,000 MB/s = 5 GB/s. Actually, 5 GB/s × 8 = 40 Gbps. The correct option closest is 5 Gbps, so re-check units: 500KB = 500 × 1024 bytes = 512,000 bytes = 4,096,000 bits. 10,000 × 4,096,000 bits = 40,960,000,000 bits/s = 40.96 Gbps. So correct is about 40 Gbps, closest option is 50 Gbps (D). So correct answer is D.