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
Not sure how this can be C if there are no CAS arrays in Exchange 2013. I also believe NLB is not supported? So I’d think it’s A and B
0
0
I Agree.
Answer should be A and B
0
0
A and B , no cas in 2013
0
0
I understand what everyone is saying about no CAS arrays but the question says “The solution must ensure that both servers in each office are the targets of all client connections.” That is not what DNS round robin does.
0
0
Understood RA but the question states that “The solution must ensure that both servers in each office are the targets of all client connections.” DNS round robin will do that. Agreed it’s not ideal but traffic will flow to both servers – it just has no way of knowing if the server is working or not (no health checks like you can setup on a HLB).
0
0
No CAS arrays in 2013
NLB cannot be installed on a server that is a member of a DAG
0
0
just beneath, are a lot of completely not connected web sites to ours, nonetheless, they’re certainly worth going over
0
0