A corporate environment will include Exchange Server 2010. You need to recommend a solution that
meets the following client access requirements:
• Automatic failover of specific client access protocols
• Distribution of client access traffic across multiple Client Access servers
• Secure Sockets Layer (SSL) session ID for client–to–Client Access server affinity
What should you recommend?
A.
Deploy a Client Access server array.
B.
Deploy Microsoft Forefront Unified Access Gateway (UAG) as a reverse proxy.
C.
Deploy a hardware load balancer for the Client Access servers.
D.
Deploy Microsoft Forefront Threat Management Gateway (TMG) as a reverse proxy.
Explanation:
Hardware Load Balancing
If you have more than eight Client Access servers in a single Active Directory site, your organization
will need a more robust load balancing solution. Although software load balancing solutions
available, a hardware load balancing solution provides the most capacity solutions, see Microsoft
Unified Communications Hardware Load Balancer Deployment. For more information about
Exchange 2010 server solution, see Microsoft Unified Hardware Load Balancing Hardware Load
Balancer Deployment. Hardware load balancers support very high traffic throughput and can be
configured to load balance in many ways. Most hardware load balancer vendors have
documentation about how their product works with Exchange 2010. The simplest way to configure
hardware load balancers is to create a fallback list of the be applied by the load balancer. For
example, the load balancer will try cookie-based affinity first, then SSL session ID, and then source IP
affinity.