Your company has a main office and three branch offices.
You have an Exchange Server 2013 organization. The main office contains five Exchange servers. Each
branch office contains two Exchange servers. All of the servers have all of the Exchange server roles installed.
Each branch office contains one database availability group (DAG).
You need to recommend a load balancing solution for the branch offices. The solution must ensure that both
servers in each office are the targets of all client connections.
What are two possible recommendations? Each correct answer presents a complete solution.
A.
DNS round robin
B.
Layer 4 hardware load balancers
C.
CAS arrays
D.
Network Load Balancing (NLB) clusters
Explanation:
B: The use of hardware load balancers is still supported for Exchange 2013.
C: In Exchange 2010, Microsoft introduced the concept of a Client Access array. After a Client Access array
was configured for an Active Directory site, all Client Access servers in the site automatically became membersof the array. In current builds of Exchange 2013, no configuration of a Client Access array is required, because
the deployment of a load balanced and highly available service is much simpler.
Incorrect answers:
Not A: A: a DNS round robin could in theory be used entirely in place of a hardware load balancer – in fact it’s
almost as effective as using Windows Network Load balancing. However, DNS Round robin is in fact no load balancer.
Not D: Windows Network Load Balancing (WNLB) can’t be used on Exchange servers where mailbox DAGs
are also being used because WNLB is incompatible with Windows failover clustering. If you’re using an
Exchange 2013 DAG and you want to use WNLB, you need to have the Client Access server role and the
Mailbox server role running on separate servers.
https://technet.microsoft.com/en-us/library/jj898588%28v=exchg.150%29.aspx