A load balancer primarily distributes incoming network traffic across multiple servers to ensure no single server becomes overwhelmed. Which of the following is a key differentiator when comparing a load balancer to an API gateway in a system design context?

Load balancers operate at a lower network layer (e.g., Layer 4) and are generally unaware of the application's protocol, while API gateways operate at a higher layer (e.g., Layer 7) and understand application-level protocols like HTTP.

API gateways are exclusively used for distributing traffic, whereas load balancers are used for security and authentication.

Load balancers are primarily designed for internal service-to-service communication, while API gateways are for external client access only.

API gateways typically manage caching and request transformation, which are not functions of load balancers.

Consider a scenario where you have multiple microservices, and clients need to interact with them through a single, unified entry point. Additionally, you need to handle cross-cutting concerns like authentication, rate limiting, and request routing based on the request path. Which component would be most suitable for this role?

A traditional Layer 4 load balancer.

A reverse proxy with basic forwarding rules.

A company is experiencing performance issues due to uneven distribution of user requests across its web servers. They want to ensure that traffic is spread evenly to maintain optimal performance and availability. Which component should they implement or enhance?

A load balancer to distribute traffic across servers.

An API gateway to handle request transformations.

A content delivery network (CDN) for caching static assets.

A message queue for asynchronous processing.

Which of the following is a typical responsibility of an API gateway that is generally NOT a core responsibility of a standard load balancer?

Implementing authentication and authorization for incoming requests.

Distributing incoming requests across multiple backend instances.

Performing health checks on backend servers.

Terminating SSL/TLS connections.

A system designer is choosing between a Layer 7 load balancer and an API gateway. The primary requirement is to route traffic based on the HTTP request method (GET, POST, PUT, DELETE) and the request path (e.g., /users, /products). Which component is better suited for this task, and why?

API gateway, because it inherently understands HTTP and can perform content-based routing.

Layer 7 load balancer, because it can inspect HTTP headers.

Both are equally capable, as both operate at the application layer.

Neither is suitable; a DNS-based load balancer should be used for path-based routing.

Which of the following is a potential downside of relying solely on a traditional load balancer for managing microservices communication?

It may not provide sufficient mechanisms for service discovery.

It cannot handle SSL/TLS termination effectively.

It lacks the ability to perform health checks on services.

It is not capable of caching responses.

A system requires strict enforcement of API usage policies, including limiting the number of requests a user can make within a specific time frame (rate limiting) and ensuring only authorized users can access certain endpoints. Which component is best equipped to enforce these policies centrally?

Individual microservices, each implementing their own rate limiting and authentication.

Which statement accurately describes a difference in functionality between a typical load balancer and an API gateway regarding request modification?

API gateways can transform request headers and bodies (e.g., add/remove fields, change formats), while load balancers typically do not.

Load balancers can modify request bodies, while API gateways cannot.

Neither component is designed to modify requests; modification should happen at the service level.

Both components are equally capable of arbitrary request modification.

A developer is building a new feature that involves aggregating data from three different microservices. They want to expose this aggregated data as a single API endpoint to the client. From the perspective of simplifying client interactions, which approach is most effective?

Use an API gateway to perform the aggregation (e.g., using a pattern like the Client Facade).

Modify each of the three microservices to include the aggregated data in their responses.

Implement the aggregation logic directly in the client application.

Introduce a new database to store the aggregated data.

When considering security in a microservices architecture, an API gateway can serve as a 'security blanket' for backend services. Which of the following security functions is MOST likely to be handled exclusively or primarily by the API gateway?

Authentication and authorization of incoming API requests.

Input validation of data within the request body.

Encryption of data within the database.

Securing individual service-to-service communication channels.

A team is migrating a monolithic application to microservices. They decide to place an API gateway in front of their new microservices. What is the MOST significant benefit this API gateway provides during the migration process?

It allows clients to interact with the new microservices using the same API structure as the monolith during the transition.

It automatically refactors the monolithic code into microservices.

It eliminates the need for load balancing.

It enhances the performance of the original monolithic application.

In a system design, what is a key characteristic that distinguishes an API gateway from a standard reverse proxy?

An API gateway provides richer features like request transformation, rate limiting, and analytics, which are often beyond the scope of a basic reverse proxy.

A reverse proxy exclusively handles HTTP/S traffic, while an API gateway can handle any network protocol.

A reverse proxy's primary role is load balancing, whereas an API gateway's is security.

API gateways are stateless, while reverse proxies are stateful.

A distributed system uses both a load balancer and an API gateway. The load balancer is configured to distribute incoming traffic across multiple instances of the API gateway. What is the primary reason for this configuration?

To prevent the API gateway from becoming a single point of failure and to improve its availability and scalability.

To enable the API gateway to perform more advanced load balancing functions.

To reduce the latency of requests processed by the API gateway.

To allow the API gateway to perform SSL termination for the load balancer.

Load balancer vs API gateway in system design — Free MCQ Practice Test

Load balancer vs API gateway in system design — Free MCQ Practice Test | testpaper.space