HOTSPOT
You have an Exchange Server 2013 organization that contains three servers. The servers are configured as
shown in the following table.
All inbound email messages from the Internet are routed through EX01.
You plan to remove EX01 from the organization.
You need to ensure that all of the functionalities of EX01 are transferred to EX02 and EX03. The solution must
minimize administrative effort.
Which functionality should you transfer to each server? (To answer, select the appropriate server for each
functionality in the answer area.)
Hot Area:
Answer: 
Explanation:
http://technet.microsoft.com/en-us/library/bb125184(v=exchg.141).aspx
In the console tree, navigate to Organization Configuration > Mailbox.
In the result pane, click the Offline Address Book tab, and then select the OAB for which you want to move the
generation to a new server.
In the action pane, click Move.
On the Move Offline Address Book page, click Browse to open the Select Mailbox Server dialog box. Select the
server to which you want to move the OAB generation process, and then click OK.
Click Move to move the OAB generation process to the new server.
View the status of the move operation. The wizard will move the generation of your OAB to the new server and
copy the existing files for the OAB to the new server. Click Back to make configuration changes.
On the Completion page, review the following, and then click Finish to close the wizard:
A status of Completed indicates that the wizard completed the task successfully.
A status of Failed indicates that the task wasn’t completed. If the task fails, review the summary for an
explanation, and then click Back to make any configuration changes.
Click Finish to close the wizard.
http://technet.microsoft.com/en-us/library/aa998825(v=exchg.150).aspx
A distribution group expansion server This is the routing destination when a distribution group has a designated
expansion server that’s responsible for expanding the membership list of the group. A distribution group
expansion server is always a Hub Transport server or an Exchange 2013 Mailbox server.
http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx
FrontEnd Transport service – This service runs on all Client Access servers and acts as a stateless proxy for all
inbound and outbound external SMTP traffic for the Exchange 2013 organization. The Front End Transport
service doesn’t inspect message content, only communicates with the Transport service on a Mailbox server,
and doesn’t queue any messages locally.