###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###
Your company has an Exchange Server 2016 organization named contoso.com. You need to
recommend a solution that meets following requirements:
A user named Userl must be able to send email messages by using an alias of [email protected] the From
field.
Recipients of the messages must be prevented from the identifying the actual sender of the message.
Userl and a user named User2 must each receive a copy of replies to [email protected]
What should you recommend?
A.
Create a distribution group named Sales that has an alias of Sales. Add User1 and User2 to the group.
Assign the Send As permissions to User1.
B.
Create a shared mailbox named Sales that has an Alias of Sales. Assign the Receive As permission
User1 and User2. Assign the Send As permission to User 1
C.
Create a shared mailbox named Sales that has an Alias of Sales. Assign the Receive As permission
User1 and User2. Assign the Send on permission to User 1
D.
Create a distribution group named Sales that has an alias of Sales. Add User1 and User2 to the group.
Assign the send on Behalf permission to User1.
B
https://technet.microsoft.com/en-us/library/mt577278(v=exchg.160).aspx
I think right answer is A because when you create shared mailbox you also need create transport rule to send copy of message to User1 and User2. With distribution group no extra action is needed.
Option A is close and correct.
Send As permission on the DL, so that User1 can send an email as [email protected].
User1 and 2 being members of the group receives the message. Question didn’t say User1 can’t receive the message.
Since User2 do not have send as permission, he cant send emails claiming, [email protected].
Shared mailbox way will work, this involves applying a forward or transport rule. ReceiveAs permission mentioned is not meant to receive email, So I consider it as wrong 🙂