###BeginCaseStudy###
Testlet 1
Topic 1, Fabrikam, Inc
Overview
Fabrikam, Inc., is a pharmaceutical company located in Europe. The company has 5,000 users.
The company is finalizing plans to deploy an Exchange Server 2013 organization.
The company has offices in Paris and Amsterdam.
Existing Environment
Active Directory Environment
The network contains an Active Directory domain named fabrikam.com. An Active Directory
site exists for each office.
Network Infrastructure
The roles and location of each server are configured as shown in the following table.
Client computers run either Windows 7 or Windows 8 and have Microsoft Office 2010 installed.
The Paris office uses the 192.168.1.0/24 IP range. The Amsterdam office uses the 192.168.2.0/24 IP range.
The offices connect to each other by using a high-speed, low-latency WAN link. Each office has a 10-Mbps
connection to the Internet.
Planned Exchange Infrastructure
The company plans to deploy five servers that run Exchange Server. The servers will be configured as shown
in the following table.
The company plans to have mailbox databases replicated in database availability groups (DAGs). The mailbox
databases and DAGs will be configured as shown in the following table.
DAG1 will use FS1 as a file share witness. DAG2 will use FS3 as a file share witness.
You plan to create the following networks on each DAG:
A dedicated replication network named DAGNET1
A MAPI network named DAGNET2
All replication traffic will run on DAGNET1. All client connections will run on DAGNET2. Client connections must
never occur on DAGNET1. Replication traffic must only occur on DAGNET2 if DAGNET1 is unavailable.
Each Exchange Server 2013 Mailbox server will be configured to have two network adapters.
The following two mailbox databases will not be replicated as part of the DAGs:
A mailbox database named AccountingDB that is hosted on EX1
A mailbox database named TempStaffDB that is hosted on EX4EDGE1 will have an Edge Subscription configured, with both EX1 and EX2 as targets.
Requirements
Planned Changes
An external consultant reviews the Exchange Server 2013 deployment plan and identifies the following areas of
concern:
The DAGs will not be monitored.
Multiple Edge Transport servers are required to prevent the potential for a single point of failure.
Technical Requirements
Fabrikam must meet the following technical requirements:
Email must be evaluated for SPAM before the email enters the internal network.
Production system patching must minimize downtime to achieve the highest possible service to users.
Users must be able to use the Exchange Control Panel to autonomously join and disjoin their department’s
distribution lists.
Users must be able to access all Internet-facing Exchange Server services by using the names of
mail.fabrikam.com and autodiscover.fabrikam.com.
The company establishes a partnership with another company named A. Datum Corporation. A Datum uses the SMTP suffix adatum.com for all email addresses. Fabrikam plans to exchange sensitive information with A.
Datum and requires that the email messages sent between the two companies be encrypted. The solution must
use Domain Security.
Users in the research and development (R&D) department must be able to view only the mailboxes of the users
in their department from Microsoft Outlook. The users in all of the other departments must be prevented from
viewing the mailboxes of the R&D users from Outlook.
Administrators plan to produce HTML reports that contain information about recent status changes to the
mailbox databases.
Fabrikam is evaluating whether to abort its plan to implement an Exchange Server 2010 Edge Transport server
and to implement a Client Access server in the Paris office instead. The Client Access server will have antispam agents installed.
###EndCaseStudy###
An administrator recommends removing EDGE1 from the implementation plan and adding a new Client Access
server named CAS-8 instead.
You need to identify which anti-spam feature will NOT be available on CAS-8.
Which anti-spam feature should you identify?
A.
Connection Filtering
B.
Sender Filtering
C.
Content Filtering
D.
Recipient Filtering
Explanation:
EDGE1 is an exchange server 2010
CAS-8 would be an exchange server 2013
Typically, you would enable the anti-spam agents on a mailbox server if your organization doesn’t have an Edge
Transport server, or doesn’t do any prior anti-spam filtering before accepting incoming messages.
Connection Filtering agent is only available on the Edge Transport server role. Exchange 2013 does not have
an Edge Transport server role yet.
The Connection Filter agent and the Attachment Filter agent are only available on an Edge Transport server.
Connection Filtering on Edge Transport Servers: Exchange 2013 Help
Anti-spam agents on Legacy Edge Transport servers
If your organization has an Exchange 2007 or Exchange 2010 Edge Transport server installed in the perimeter
network, all of the anti-spam agents that are available on a Mailbox server are installed and enabled by default
on the Edge Transport server. However, the following anti-spam agents are only available on an Edge
Transport server:
Connection Filtering agent Connection filtering inspects the IP address of the remote server that’s trying to send
messages to determine what action, if any, to take on an inbound message. The remote IP address is available
to the Connection Filtering agent as a byproduct of the underlying TCP/IP connection that’s required for the
SMTP session. Connection filtering uses a variety of IP Block lists, IP Allow lists, as well as IP Block List
provider services or IP Allow List provider services to determine whether the connection from the specific IP
should be blocked or allowed in the organization. For more information about connection filtering in Exchange
2010, see <fwlink to http://technet.microsoft.com/library/bb124320(v=exchg.141).aspx>.
Attachment Filter agent Attachment filtering filters messages based on attachment file name, file name
extension, or file MIME content type. You can configure attachment filtering to block a message and its
attachment, to strip the attachment and allow the message to pass through, or to silently delete the message
and its attachment. For more information about attachment filtering in Exchange 2010, see <fwlink to http://
technet.microsoft.com/library/bb124399(v=exchg.141).aspx>
What’s Discontinued in Exchange 2013
http://technet.microsoft.com/en-us/library/jj619283(v=exchg.150).aspx
Feature
Anti-spam agent management in the EMC
In Exchange 2010, when you enabled the anti-spam agents on the Hub Transport server, you could manage
the anti-spam agents in the Exchange Management Console (EMC). In Exchange 2013, when you enable the
anti-spam agents in the Transport service on a Mailbox server, you can’t manage the agents in the Exchange
admin center (EAC). You can only use the Exchange Management Shell. For information about how to enablethe anti-spam agents on a Mailbox server, see Enable Anti-Spam Functionality on a Mailbox Server.
Connection Filtering agent on Hub Transport servers
In Exchange 2010, when you enabled the anti-spam agents on a Hub Transport server, the Attachment Filter
agent was the only anti-spam agent that wasn’t available. In Exchange 2013, when you enable the antispam
agents in the Transport service on a Mailbox server, the Attachment Filter agent and the Connection Filtering
agent aren’t available. The Connection Filtering agent provides IP Allow List and IP Block List capabilities. For
information about how to enable the anti-spam agents on a Mailbox server, see Enable Anti-Spam Functionality
on a Mailbox Server.
Note:
You can’t enable the anti-spam agents on an Exchange 2013 Client Access server. Therefore, the only way to
get the Connection Filtering agent is to install an Exchange 2010 or Exchange 2007 Edge Transport server in
the perimeter network. For more information, see Use an Edge Transport Server in Exchange 2013.
Sender Filter agent
Sender filtering compares the sender on the MAIL FROM: SMTP command to an administrator-defined list of
senders or sender domains who are prohibited from sending messages to the organization to determine what
action, if any, to take on an inbound message.
Content Filter agent
Content filtering assesses the contents of a message.
Spam quarantine is a feature of the Content Filter agent that reduces the risk of losing legitimate messages that
are incorrectly classified as spam. Spam quarantine provides a temporary storage location for messages that
are identified as spam and that shouldn’t be delivered to a user mailbox inside the organization. For more
information, Recipient Filter agent
Recipient filtering compares the message recipients on the RCPT TO: SMTP command to an administrator
defined Recipient Block list. If a match is found, the message isn’t permitted to enter the organization.
You can’t enable the anti-spam agents on an Exchange 2013 Client Access server.
Therefore, the only way to get the Connection Filtering agent is to install an Exchange 2010 or Exchange 2007
Edge Transport server in the perimeter network
Connection Filtering agent is only available on the Edge Transport server role. Exchange 2013 does not have
an Edge Transport server role yet.
NOT B C D
Only need to identify 1 and this is connection filtering.