A Chief Security Officer is looking for a solution that can reduce the occurrence of customers receiving errors from back-end infrastructure when systems go offline unexpectedly. The security architect would like the solution to help maintain session persistence. Which of the following would BEST meet the requirements?
A load balancer distributes incoming network traffic across multiple servers or back-end infrastructure components to ensure efficient utilization of resources and enhance the availability and reliability of services. In case one of the back-end servers goes offline unexpectedly, the load balancer can route traffic to other healthy servers, reducing the impact on customers and minimizing errors. Load balancers can also support session persistence, where the load balancer ensures that a specific client's requests are always directed to the same back-end server for the duration of the session. This is essential for maintaining a consistent user experience and avoiding issues that could arise if a user's session is suddenly interrupted due to server changes.
A load balancer can monitor the backend servers and direct traffic to working servers when other servers go offline. It can also maintain session persistence, where a reverse proxy does not care about session persistence.
If you put load balancing wouldn't the answer be NIC teaming since it includes load balancing?
yes, Network Interface Card (NIC) teaming is a common technique of grouping physical network adapters to improve performance and redundancy. The major benefits of NIC teaming are load balancing (redistributing traffic over networks) and failover (ensuring network continuity in the event of system hardware failure) without the need for multiple physical connections. Anyone can answer this please?
The answer should be B. The key here is "session persistence". Load balancing would direct to the server, but if NIC was down, the session would end. By doing NIC teaming, if a NIC go down, there is a redundancy to keep the session persistence.
the question did not mention NIC being down, it says system being down which means the server itself. If the server itself goes offline, what will the 2 NICS do?
Load balancer and Reverse Proxy will both do the job for requirement 1, but load balancer will also provide session persistency
I don't see how a Reverse Proxy will achieve redundancy.
A load balancer distributes incoming network traffic across multiple servers or back-end infrastructure components to ensure efficient utilization of resources and enhance the availability and reliability of services. In case one of the back-end servers goes offline unexpectedly, the load balancer can route traffic to other healthy servers, reducing the impact on customers and minimizing errors. Load balancers can also support session persistence, where the load balancer ensures that a specific client's requests are always directed to the same back-end server for the duration of the session. This is essential for maintaining a consistent user experience and avoiding issues that could arise if a user's session is suddenly interrupted due to server changes.
The answer is definitively load balancer. Session persistence is one of the benefits of a load balancer. Check out this page: https://www.nginx.com/resources/glossary/reverse-proxy-vs-load-balancer/#:~:text=A%20reverse%20proxy%20accepts%20a,server%20to%20the%20appropriate%20client.
Reverse proxies are placed between servers and clients, and they are used to help with load balancing and caching of content. Load balancers are used to distribute traffic to multiple systems, provide redundancy, and allow for ease of upgrades and patching. This is directly from CompTIA sec+ study guide book. caching of content = session persistence, hence the answer, A best of luck
I've used reverse proxies for years. Never saw one do load balancing or caching. Must be something new.
Oops. yes they do caching (mine does it, but it doesn't have automatic load-balancing, you have to change the forwarders manually - it's 10 years old, so, there's that)
Ah, but you won't get session persistence with reverse proxies! content caching is not the same thing as session handling. content caching is for all visitors
load balancer is a device or software that distributes network traffic across multiple servers to ensure efficient utilization of resources and improve reliability and availability. It can help reduce errors from back-end infrastructure by evenly distributing traffic and preventing overload on individual servers. This helps to avoid situations where systems go offline unexpectedly.
The problem with Load Balancers' Session Persistence is that it keeps your session persistent on one server - if that server goes down during your persistent session, data will be loss when switching the session to another PC. I found this about Reverse Proxies: Because reverse proxy server are the gateway between users and your application’s origin server, they’re able to determine where to route individual HTTP sessions. For applications using multiple backend servers, this means the reverse proxy can efficiently distribute the load, thereby improving overall user experience and helping ensure high availability. In the event that a server goes down, reverse proxies act as a failover solution, rerouting traffic to ensure continued site availability. I think its Reverse Proxy. Nic teaming helps have good performance to a server, but if it goes offline it doesnt matter how many NICS - e.g. an unexpected shutdown or crash
*data will be lost when switching to another SERVER (end of paragraph 1)
Session Persistence (sometimes called sticky sessions) involves directing a user's requests to one application or backend web server for the duration of a “session.” The session is the time it takes a user to complete a transaction or task that might include multiple requests. Why use reverse proxy instead of load balancer? A load balancer's main role is to distribute user requests across multiple servers. A reverse proxy can be used to facilitate requests between users and a single server
since reverse proxies don't do session persistence, why would you not pick a load balancer?
Answer is A. Session Persistence (sometimes called sticky sessions) involves directing a user's requests to one application or backend web server for the duration of a “session.” The session is the time it takes a user to complete a transaction or task that might include multiple requests. Why use reverse proxy instead of load balancer? A load balancer's main role is to distribute user requests across multiple servers. A reverse proxy can be used to facilitate requests between users and a single server
Reverse proxies are more focused on caching and security, while load balancers are aimed at evenly distributing traffic and ensuring high availability.
A reverse proxy has nothing to do with back-end infrastructure and wouldn't help when systems go offline unexpectedly. A load balancer would to this perfectly.
Load balancer employs "sticky session" which is persistence.
A load balancer spreads incoming traffic across multiple backend servers. this will satisfy the issue of when the systems go offline as the load balancer can redirect traffic to other available servers, reducing customers receiving errors. Load balancers can also be configured to ensure that request from the same client are consistently routed the same backend server this helps maintain session persistence. Nic teaming combines multiple network interfaces for redundancy and increased bandwidth but doesn't handle incoming traffic or session management. Answer. C Load balancer.
NIC only provides the network redundancy, If the system goes offline, NIC won't be help.
C. Load balancer Some load balancers use source address affinity to direct the requests. Source affinity sends requests to the same server based on the requestor’s IP address and provides the user with session persistence.
https://www.upguard.com/blog/reverse-proxy-vs-load-balancer Load balancers ensure a specific user’s (i.e. from a particular IP address) requests are always sent to the same server during a session.
Answer is A, load balancer. Load balancer can handle session persistence! Info about a users session is stored at the browser level for example, changing server in the middle of communication would cause issues along with latency. Load balancers handle session persistence as needed. Its a key feature of a load balancer, not a reverse proxy.