###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 have an Exchange Server 2016 organization.
You need to ensure that users in each department download an Offline Address Book (OAB) that only contains
the users in their department. The solution must ensure that all of the users can continue to see all the other
users in the organization.
Which three actions should you perform? Each correct answer presents part of the solution.
A.
Create an OAB for each department
B.
Modify the properties for each user mailbox.
C.
Create an address book policy (ABP) for each department.
D.
Create an address list for each department.
E.
Modify the properties of the default OAB.
F.
Create an email address policy for each department.
https://technet.microsoft.com/en-us/library/jj657455(v=exchg.150).aspx
I think you need to also create an address list for each department, because you cannot create an OAB without address list. New-OfflineAddressBook cmdlet has Addresslists as required parameter. Of course we can assume that address lists for departments are already there.
Exact procedure would be
1) Create an address list for each department
2) Create an OAB for each department
3) Create an address book policy for each department
4) Modify the properties for each user mailbox (=> Set-Mailbox –AddressBookPolicy )
Pluralsight courses from James Cunningham also follow this process. Mahoney is correct.
One possibility is to set OAB direct to mailbox without Address Book Policy (Set-Mailbox -OfflineAddressBook). In that case I would choose A,B and D.
Agree
A B D
Does not make sense to put it on a usermailbox why not just make policy to achieve this if it can be easy
https://technet.microsoft.com/en-us/library/hh529931(v=exchg.150).aspx
We have to choose three answer:
1. Create address list
2. Create oab with this address list
3. Assign OAB to mailbox
So answer is A & B & D.
With address book policy this task can be completed in four steps.
So that makes ACD
Why do you need a Address Book policy if we can define just the OAB on mailboxes.
My options are – D, A and B.
Create New Address lists based on the departments
Create new Offline Address Book, with the department specific Address list
Set each mailbox with -OfflineAddressBook switch with the OAB created above.
Even if you create a AddressBook policy, you still need to define per mailbox (Set-Mailbox is still mandatory). Since the same can be achieved without a AddressBookPolicy, I feel “C” is optional.
Moreover, To define in Addresslist policy, we still need department specific OAB created for the restricted view. We shouldn’t use default OAB.
….
Address book policies are meant to restrict the Address list views for different set of users, which is not the ask here. Catch is – “all of the users can continue to see all the other users in the organization”