###BeginCaseStudy###
Testlet 1
Topic 2, Contoso Ltd
Overview
General Overview
Contoso, Ltd., is a scientific research and supply company that has offices along the east coast of
North America. The company recently completed an upgrade to Exchange Server 2013.
Physical Locations
The company has three sales offices and a research office. The sales offices are located in
Atlanta, New York, and Montreal. The research office is located in Miami.
Existing Environment
Existing Environment
Active Directory Environment
The network contains one Active Directory forest named contoso.com. The Miami office has its own domain
named research.contoso.com.
Each office is configured as an Active Directory site. Each site contains two domain controllers that run
Windows Server 2008 R2 x64. All of the FSMO roles for contoso.com are owned by a domain controller in the
New York site. All of the FSMO roles for the research.contoso.com domain are owned by a domain controller in
the Miami site.
One domain controller in each site is configured as a global catalog server. All of the domain controllers are
configured as DNS servers.
The functional level of the forest and domains is Windows Server 2008 R2.
Network Infrastructure
All client computers are configured to connect to the DNS servers in their respective office only.
Contoso.com has a standalone certification authority (CA) on a server that runs Windows Server 2008 R2.
All offices connect to the New York office by using a high-speed WAN link.
Email Infrastructure
The Exchange Server 2013 organization contains four servers in the New York office. The servers are
configured as shown in the following table.
All external access for the contoso.com organization is provided through an Internet link at the New York office.
Load balancing is provided by using DNS round robin. All inbound and outbound email for the domain is routed
through a mail appliance in the New York office.The Exchange Server 2013 organization contains four servers in the Atlanta office. The servers are configured
as shown in the following table.
The file share witness for NY-DAG is on a file server in the Atlanta office.
The Exchange Server 2013 organization contains two servers in the Montreal office and two servers in the
Miami office. The servers are configured as shown the following table.
All external access to the organization of the research.contoso.com domain is provided through the Internet link
at the Miami office. Load balancing is provided by using DNS round robin. All inbound and outbound email for
the domain goes through an email appliance in the Miami office.
All Exchange Server 2013 servers run Windows Server 2012 Standard.
All users have Windows Phone devices that connect to the Exchange organization by using Exchange
ActiveSync.
User Issues
You discover the following user issues:
Some users report that, intermittently, they fail to connect to their email from their Windows Phone device.
Some users from the New York office report that some searches from Outlook Web App return incomplete
results.
Some of the users in each office report that they fail to access their mailbox during the maintenance period
of the Active Directory domain controllers.
You verify that all of the remote users can connect to the network successfully by using a VPN connection, and
can then launch Outlook successfully.
Partnerships
Contoso recently entered into a partnership with a company named A. Datum Corporation. A Datum has a main office and four branch offices. The main office is located in Toronto.
A Datum has a messaging infrastructure configured as shown in the following table.
Requirements
Planned Changes
Contoso plans to deploy a hardware load balancer in the New York office. The load balancer must bridge all
SSL connections to the Exchange servers.
You plan to deploy two new Exchange Server 2013 servers in a virtual server environment in the Miami office.
The servers will host a few mailboxes as part of an evaluation of resource utilization for virtualized Exchange
servers.
You also plan to deploy a high availability solution for Mailbox servers in the
You plan to replace the email appliance in New York because of recent power outages.
Business Requirements
Contoso identifies the following business requirements:
Minimize the hardware costs required for a load balancing solution.
Minimize the software costs required for a load balancing solution.
Minimize user interruptions if a service fails on a Mailbox server.
Minimize user interruptions if a service fails on a Client Access server.
###EndCaseStudy###
You need to ensure that all of the email messages sent from the Internet to adatum.com are routed through the contoso.com organization.
What should you create in contoso.com? (Each corrects answer presents part of the solution. Choose all that apply.)
A.
A contact object for each adatum.com recipient
B.
An internal relay accepted domain for adatum.com
C.
A Send connector that is configured to point to the contoso.com transport servers
D.
A Send connector that is configured to point to the adatum.com transport servers
E.
An authoritative accepted domain for adatum.com
Explanation:
Internal Relay Domain
You can configure a relay domain as an internal relay domain or as an external relay domain. These two relay
domain types are described in the following sections.
When you configure an internal relay domain, some or all of the recipients in this domain don’t have mailboxes
in this Exchange organization. Mail from the Internet is relayed for this domain through Transport servers in this
Exchange organization. This configuration is used in the scenarios that are described in this section.
An organization may have to share the same SMTP address space between two or more different messaging
systems. For example, you may have to share the SMTP address space between Exchange and a third-party
messaging system, or between Exchange environments that are configured in different Active Directory forests.
In these scenarios, users in each email system have the same domain suffix as part of their email addresses.
To support these scenarios, you need to create an accepted domain that’s configured as an internal relay
domain. You also need to add a Send connector that’s sourced on a Mailbox server and configured to send
email to the shared address space. If an accepted domain is configured as authoritative and a recipient isn’t
found in Active Directory, a non-delivery report (NDR) is returned to the sender. The accepted domain that’s
configured as an internal relay domain first tries to deliver to a recipient in the Exchange organization. If the
recipient isn’t found, the message is routed to the Send connector that has the closest address space match.
If an organization contains more than one forest and has configured global address list (GAL) synchronization,
the SMTP domain for one forest may be configured as an internal relay domain in a second forest. Messages
from the Internet that are addressed to recipients in internal relay domains are relayed to the Mailbox servers in
the same organization. The receiving Mailbox servers then route the messages to the Mailbox servers in the
recipient forest. You configure the SMTP domain as an internal relay domain to make sure that email that’s
addressed to that domain is accepted by the Exchange organization. The connector configuration of your
organization determines how messages are routed.
B
An accepted domain is any SMTP namespace for which a Microsoft Exchange Server 2013 organization sends
or receives email.
Accepted domains include those domains for which the Exchange organization is authoritative. An Exchange
organization is authoritative when it handles mail delivery for recipients in the accepted domain.
Accepted domains also include domains for which the Exchange organization receives mail and then relays it to
an email server that’s outside the organization for delivery to the recipient.
D
2nd part of establishing an internal relay domain is to establish a Send Connector that is configured to point to
the other organization’s mail servers (a datum)
NOT A
Better to establish an internal relay domain.
A mail-enabled Active Directory contact that contains information about people or organizations that exist
outside the Exchange organization. Each mail contact has an external email address. All messages sent to the
mail contact are routed to this external email address.
NOT C
Need to establish a Send connector to adatum.com not contoso.com
NOT E
Need to establish an internal relay domain not an authorative accepted domain for adatum.com
Accepted Domains: Exchange 2013 Help
Send Connectors: Exchange 2013 Help