You are the Exchange administrator for your company. The Exchange organization contains two Exchange routing groups. Each routing group contains four Exchange Server 2003 computers.
One Exchange server in each routing group hosts a routing group connector. The company’s Service Level Agreement (SLA) states that internal email service should not be disrupted by the failure of a single Exchange server.
You need to ensure that email messages are delivered between the two routing groups even if one of the Exchange servers fails. You want to achieve this goal by using the minimum amount of administrative effort.
What should you do?
A.
In each routing group, configure an additional SMTP virtual server on one Exchange server that is not used by the routing group connector.
B.
In each routing group, create an SMTP connector that forwards all mail for the SMTP address space of "*" to the bridgehead server in the other routing group.
C.
On the properties of each routing group connector, add an SMTP virtual server from another Exchange server.
D.
On an Exchange server that does not host the routing group connector, create an additional routing group connector and use the same local and remote SMTP virtual servers that are used by the existing routing group connector.
Explanation:
A Routing Group is a collection of "well-connected" Exchange Server computers. Messages sent between any two servers within a
Routing Group are routed directly from source to target. Full mesh, 24×7 connectivity is assumed. Any messages sent from a server
in one Routing Group to a server in an other Routing Group must be routed to a bridgehead in the source Routing Group and over to
a bridgehead in the destination Routing Group.
Incorrect answers:
A. Create additional SMTP virtual Server – Does not give any redundancy, as no connection is established if the link fails. In
addition, another virtual SMTP server would not use the default connections, and hence not do anything other than simple sit
there.
B. Create a SMTP link in each group that forwards all SMTP traffic to the other bridgehead server
� This would work, but is more administration, and if the bridgehead server goes down, this link would collapse as well.
C. On the properties of each routing group connector, add an SMTP virtual server from another server – This utilizes the same link
for connectivity, and hence has the same problem: If the link goes down, then there is no backup. Therefore, there is no
redundancy as required by the question.