###BeginCaseStudy###
Topic 3, Contoso Ltd,
Overview General Overview Contoso. Ltd. is an international company that has 3,000 employees.
The company has sales, marketing, research, and human resource departments.
Physical Locations
Contoso has two main offices. The offices are located in New York and Chicago. Each moffice has a data center.
The New York office uses a network subnet of 10.1.0.0/16. The Chicago office uses a mnetwork subnet of
10.128.0.0/16.
The offices connect to each other by using a WAN link. Each office connects directly to the Internet.
Existing Environment
Active Directory The network contains an Active Directory forest named contoso.com. The forest mcontains a
single domain. All domain controllers run Windows Server 2012 R2. The forest mfunctional level is Windows
Server 2012 R2.
The forest contains six domain controllers configured as shown in the following table.
The forest is configured as a single Active Directory site.
Active Directory administrators manage the Active Directory schema. Exchange Server madministrators do not
have access to modify the schema.
Contoso has deployed Active Directory Rights Management Services (AD RMS).
Current Business Model
Contoso partners with a company names Fabrikam. Inc. on manufacturing initiatives. The partnership between
Contoso and Fabrikam requires that both companies share confidentialm information frequently.
Requirements
Business Goals
Contoso plans to install Exchange Server 2016 to provide messaging services for its users.
It must be as easy as possible for the users at Contoso to share free/busy information with mthe users at
Fabrikam.
As much as possible Contoso plans to minimize the costs associated with purchasing hardware and software.
Planned Changes
Contoso plans to implement the following changes before installing Exchange Server 2016:
Install hardware Network Load Balancing (NLB) in the New York and Chicago offices.
Implement Microsoft Office Online Servers in the New York and Chicago offices.
Provide Contoso users with company-approved tablets.
Planned Messaging Infrastructure
You plan to create an Exchange Server 2016 organization named Contoso. You plan to deploy seven servers
that will have Exchange Server 2016 installed. The servers will be configured as mshown in the following table.
All of the servers will be members of a database availability group (DAG) named DAG01.
Client Access Requirements
Contoso identifies the following client access requirements for the planned deployment:
Users must be able to configure their tablet to synchronize email by using Autodiscover.
Users must be able to access the Exchange Server organization by using the following names:
Mail.contoso.com
Autodiscover.contoso.com
Users must be able to access Outlook on the web internally and externally from their tablet.
Users must be able to access Office Online Server by using the URL of office-online.contoso.com.
Security Requirements
Contoso identifies the following security requirements for the planned deployment:
Exchange Server mailbox databases must be encrypted while at rest.
Users must be prevented from using Outlook on the web while they are offline.
Contoso users must be able to share Calendar details with approved external domains only.
Email messages sent to the users in the fabrikam.com SMTP domain must be encrypted automatically.
Whenever possible, client computers must be directed to the same Exchange server for log collection.
Users must be able to access their mailbox by using Exchange ActiveSync on the company approved tablets
only.
Email messages sent from the users in the human resources department of Contoso must be protected by
using AD RMS. regardless of the mail client.
Availability Requirements
Contoso identifies the following high-availability requirements for the planned deployment:
Servers must be able to complete a restart without administrative intervention.
The network load balancer must be able to probe the health of each workload.
If a data center fails, the databases in the other data center must be activated automatically.
Redundant copies of all email messages must exist in the transport pipeline before and after mdelivery.
Email messages must be made highly available by the Exchange Server organization before and after delivery.
If you manually mount the databases following the data center failure, the databases in the failed site must be
prevented from mounting automatically.
###EndCaseStudy###
You run the Get-SendConnector cmdlet and you receive the following output.
You need to recommend which actions are required to secure email connectivity between the contoso.com
SMTP domain and the fabrikam.com SMTP domain.
Which two actions should you recommend? Each correct answer presents part of the solution.
A.
Import a server certificate that has a subject name of ex01.contoso.com and a subject alternate name
of ex02.contoso.com.
B.
Create an Outlook protection rule.
C.
Import a server certificate that has a subject name of smtp.contoso.com.
D.
Configure theTLSSendDomainSecureListparameter for the organization.
E.
Modify the Connector Type parameter for the Send connector.
c,d
https://technet.microsoft.com/en-gb/library/bb123543(v=exchg.141).aspx#Step1
I believe D and E? The send connector type must be Partner, I remember seeing this in one of Paul Cunningham’s courses at Pluralsight.
https://technet.microsoft.com/en-us/library/jj657514(v=exchg.150).aspx
Unless this would apply only to TLS emails I believe D/E are correct.
To start with, I believe we should n’t touch the default send connector for this.
TLSSendDomainSecureList and TLSReceiveDomainSecureList parameters to be configured on Set-TransportConfig and there are no details on the the screenshots, whether done or not. So I’d ignore this.
I’ll choose C and E.
As per the screenshot, I see smtp.contoso.com is configured as FQDN, so we must need an SSL cert.
For me only other option making sense on the Send Connector configuration is Connector Type (partner) and scoped to respective target SMTP space.
The answer are correct.Read the article below:
https://social.technet.microsoft.com/wiki/contents/articles/17842.configuring-domain-security-on-exchange-server-2013.aspx
From the link that you provided it seems right. From the provided options the only matching (but NOT enough) are those two so you’ll still need to change Domain Secure Enabled to true and the receive secure list.