DRAG DROP
You are evaluating the planned deployment of the additional Exchange Server 2013 servers.
You need to meet the technical requirement for installing all of the anti-spam agents and for enabling antimalware filtering.
What should you do? (To answer, drag the appropriate servers to the correct locations. Each server may be used once, more than once, or not at all.
You may need to drag the split bar between panes or scroll to view content.)
Select and Place:
Explanation/Reference:
Explanation:
Anti-Spam Agents
http://technet.microsoft.com/en-us/library/bb201691(v=exchg.150).aspx
In Microsoft Exchange Server 2013, the following anti-spam agents are available in the Transport service on Mailbox servers, but they are not installed by default:
Content Filter agent
Sender ID agent
Sender Filter agent
Recipient Filter agent
Protocol Analysis agent for sender reputation
However, you can install these anti-spam agents on a Mailbox server using a script in the Exchange Management Shell. Typically, you would install the anti-spam agents on a Mailbox server only when your organization accepts all incoming mail without any prior anti-spam filtering.
What happens if you install the available anti-spam agents in the Transport service on a Mailbox server, but you also have other Exchange anti-spam agents operating on the messages before they reach the Mailbox server?
For example, what if you have a Microsoft Exchange 2007 or Exchange 2010 Edge Transport server in the perimeter network that delivers incoming mail directly to the Transport service on the Mailbox server?
The anti-spam agents on the Mailbox server recognize the anti-spam X-header values that are added to messages by other Exchange anti-spam agents, and messages that contain these X-headers pass through without being scanned again. However, recipient look-ups performed by the Recipient Filter agent will occur again on the Mailbox server.
Anti-malware filtering
By default, malware filtering is enabled in Microsoft Exchange Server 2013. The default anti-malware policy controls your company-wide malware filtering settings.
As an administrator, you can view and edit, but not delete, the default anti-malware policy so that it is tailored to best meet the needs of your organization.
For greater granularity, you can also create custom malware filter policies and apply them to specified users, groups, or domains in your organization. Custom policies always take precedence over the default policy, but you can change the priority (that is, the running order) of your custom policies.
Client Access Servers
The Client Access Server role is simplified to be a stateless server that accepts and authenticates client connections and acts as a proxy between the clients and the Mailbox server, ensuring that clients can locate the Mailbox server with the required data.
No data or session state is stored on the Client Access server, and clients can connect to any Client Access server and even switch Client Access servers during a session (previously, clients using some protocols had to stay connected to the same server for an entire session), thereby reducing load-balancing complexity. Client Access servers can be located in different sites from Mailbox servers, which provides flexibility for deployments.
STEPS
SERVERS ON WHICH TO INSTALL ALL OF THE ANTI-SPAM AGENTS
(NOT INSTALLED BY DEFAULT)
1. ANY OF EX1-EX4
2, EXCLUDE EX5
3,
STEPS
SERVERS ON WHICH TO ENABLE ANTIMALWARE FILTERING
1. ANY OF EX1-EX4
2. EXCLUDE EX5
3.
http://zahirshahblog.com/2013/02/05/deploying-and-configuring-exchange-server-2013-step-by-step-part-1-installing-a-fresh-exchange-server-2013-messaging-organization-in-a-green-field-environment/
Malware protection settings, Exchange 2013 includes a brand-new enhanced feature for malware protection, by default this feature is enabled on Exchange Mailbox Servers, but if you want you can also disable it.
Anti-Spam Protection: Exchange 2013 Help
