Exam 70-341 topic 1 question 72 discussion

Actual exam question from Microsoft's 70-341

Question #: 72
Topic #: 1

You need to install and configure anti-spam and antimalware filtering. Which servers should you install the anti-spam agents and enable the anti-spam and antimalware filtering? (Choose two)

A. You should install the anti-spam agents on the Client Access Servers only.
B. You should install the anti-spam agents on the Mailbox servers only.
C. You should install the anti-spam agents on the Client Access Servers and the Mailbox Servers.
D. You should enable antimalware filtering on the Client Access Servers only.
E. You should enable antimalware filtering on the Mailbox servers only.
F. You enable antimalware filtering on the Client Access Servers and the Mailbox Servers.

Show Suggested Answer

Suggested Answer: BE 🗳️
In Exchange 2013, the anti-spam agents can only be installed on the Mailbox role. But, the connection filtering which is very useful in fighting spam emails is not available in 2013.
Same goes for the attachment filter. Even though CAS proxies emails back and forth (if setup correctly), it is a stateless proxy and cant have any anti-spam agents on it.
In Exchange 2013 the anti-spam functionality (through protocol agents) is running on the Mailbox Server and not on the Client Access Server so all mail, including all spam will hit the Mailbox Server when installed in a configuration as outlined in these blog post series.
The anti-spam functionality is enabled using a PowerShell script (.\EnableAntiSpamAgents.ps1) and offers Sender and Recipient filtering, content filtering,
Sender Reputation and Sender ID filtering. To activate the ant-spam agents on the Mailbox Server open the Exchange Management Shell and enter the following commands:
CD $Exscripts.\Install-AntiSpamAgents.ps1
You can't enable the anti-spam agents on an Exchange 2013 Client Access Server
The Malware Filter runs on every 2013 Mailbox server to protect against malware and viruses.
References:

by [deleted] at April 4, 2025, 5:37 a.m.

Comments

Submit Cancel

Currently there are no comments in this discussion, be the first to comment!