What is the basic concept of Network Load Balancing (NLB) and when would you use it?

What is the basic concept of Network Load Balancing (NLB) and when would you use it?

• A. NLB distributes inbound network traffic across multiple servers to improve scalability and availability for services like web servers.
• B. NLB encrypts traffic end-to-end with SSL.
• C. NLB backs up data to tape.
• D. NLB manages Active Directory replication.

Answer: (D)

Network Load Balancing distributes inbound requests across multiple servers so the load is shared and no single machine becomes a bottleneck. This approach boosts scalability—more users or higher traffic can be handled—and improves availability because if one server fails, others continue handling requests. You’d use it when you’re running the same service on several servers and want to handle more traffic or provide fault tolerance, such as a website, web application, or API front end. It works best with stateless services or with session management that can move users between servers without loss, though some configurations support sticky sessions if needed. It’s not about encryption, data backups, or directory replication, which are managed by other technologies.

Network Load Balancing distributes inbound requests across multiple servers so the load is shared and no single machine becomes a bottleneck. This approach boosts scalability—more users or higher traffic can be handled—and improves availability because if one server fails, others continue handling requests.

You’d use it when you’re running the same service on several servers and want to handle more traffic or provide fault tolerance, such as a website, web application, or API front end. It works best with stateless services or with session management that can move users between servers without loss, though some configurations support sticky sessions if needed.

It’s not about encryption, data backups, or directory replication, which are managed by other technologies.