Load Balancing

Correct Answer: Global Server Load Balancing

The most effective method for distributing traffic based on the user's geographical location is Global Server Load Balancing. This method allows for directing users to the server that is geographically closest to them, resulting in decreased latency and enhanced user experience. The other options - Least Connection, Round Robin, and Weighted Round Robin - do not take geographical location into consideration. Least Connection directs traffic to the server with fewest connections, irrespective of the user's location. Round Robin and Weighted Round Robin distribute traffic evenly or based on weights assigned to each server respectively, again regardless of the user's geographical location.

Correct Answer: Persistence (stickiness)

The best choice for this situation is 'Persistence (stickiness)'. This configuration enables the load balancer to direct a user's requests to the same server for the duration of a session. It ensures the flow and consistency of transaction processing, which is very important in financial transactions. 'Round Robin' equally distributes requests to all servers, but cannot guarantee a user's requests to the same server. 'Weighted Round Robin' is similar to 'Round Robin', but provides more requests to servers with higher capacity - again, it cannot ensure constant redirection to the same server. 'Least Connection' directs more traffic to the server with the fewest active connections, and while it attempts to balance the load, it cannot make sure transactions are processed on the same server they are initiated on.

Correct Answer: Least Connection

The 'Least Connection' load balancing algorithm would be the best choice in this scenario. This algorithm works by assigning new requests to the server with the fewest current connections. It is especially useful when there are a large number of persistent connections in the traffic that are unevenly distributed between the servers. It ensures that no single server is overwhelmed with traffic, which leads to better performance during peak hours. On the other hand, 'Round Robin' and 'Weighted Round Robin' distribute requests evenly or based on weights assigned to each server. These methods do not consider the current load on each server, which could lead to some servers getting overwhelmed during heavy traffic. 'IP Hash' creates a unique hash key for each IP address and uses it to distribute requests, which is not necessarily the most efficient method in a high traffic scenario.