###BeginCaseStudy###
Case Study: 2
Proseware, Inc
Overview
General Overview
Proseware, Inc. is a pharmaceutical services company that has a sales department, a
marketing department, an operations department, and a human resources department.

Physical Locations
Proseware has two main offices. One of the offices is located in New York. The other office
is located in Chicago. The New York office uses a 172.16.1.0/24 network ID. The Chicago
office uses a 192.168.1.0/24 network ID.
The offices connect to each other by using a high-bandwidth, low-latency WAN link. Each
office connects directly to the Internet.
Existing Environment
The network contains an Active Directory forest named proseware.com. The forest contains
two domains named proseware.com and chicago.proseware.com. All of the user accounts and
the computer accounts in the New York office reside in the proseware.com domain. All of the
user accounts and the computer accounts in the Chicago office reside in the
chicago.proseware.com domain. All DNS zones are Active-Directory-integrated.
Each office is configured as an Active Directory site. The network ID for each office is
associated to the appropriate site.
Each office contains two domain controllers. The domain controllers were recently upgraded
from Windows Server 2008 R2 to Windows Server 2012 R2. The functional level of the
domain and the forest is Windows Server 2003.
The company uses Active Directory user attributes to store the personal information of its
employees in custom attributes.
Existing Servers
The relevant servers are configured as shown in the following table.

All servers run Windows Server 2012 R2.

DC01 has an IPv4 scope. The starting IP address in the range is 172.16.1.100 and the ending
address is 172.16.1.199.
DC03 has an IP4v scope. The starting IP address in the range is 192.168.1.100 and the ending
IP address is 192.168.1.199. There are no exclusion ranges configured on DC01 or DC03.
Requirements
Planned Changes
Proseware plans to implement the following changes:
• Deploy a read-only domain controller (RODC) to the London office.
• Give users remote access to both offices by using a VPN connection from their laptop
or tablet.
• If DC01 fails, ensure that the computers in the New York office can receive IP
addresses within 30 minutes.
• In the New York site, deploy two 50-TB, Fibre Channel SAN disk arrays. Offloaded
Data Transfer (ODX) will be used on both storage arrays. The Hyper-V hosts will use the
new SANs for virtual machine storage.
• Open three additional offices in Montreal, Atlanta, and London. The offices will
connect to each other by using a high-bandwidth, low-latency WAN link. Each office will
connect directly to the Internet.
• For legal reasons, the Montreal site will have its own forest named
montreal.proseware.com.
• The Montreal and Atlanta offices will have local IT administrators to manage the
network infrastructure of their respective office. The London office will not have a local IT
staff. Each office will have approximately 50 client computers.
Technical Requirements
Proseware identifies the following technical requirements:
• Users in the Montreal office must only be allowed to access shares that are located on
File01 and File02. The Montreal users must be prevented from accessing any other servers in
the proseware.com forest regardless of the permissions on the resources,
• Users in the New York office must be able to reconnect to the remote access VPN
servers automatically. Users in the Chicago office must use SSL to connect to the remote
access VPN servers.
• Domain controllers that run Windows Server 2012 R2 and Windows Server 2008 R2
must be able to be deployed to the proseware.com domain.
• Administrators in the New York office must be able to restore objects from the Active
Directory Recycle Bin.
• The DNS servers must be prevented from overwriting the existing DNS entries that
have been stored in cache.
• Each DNS server must be managed by an administrator from the same office as the
DNS server.
• The required time to create new fixed virtual hard disks (VHDs) on the SANs must be
minimized.

• The remote access servers must be able to restrict outgoing traffic based on IP
addresses.
• All certificates must be deployed to all of the client computers by using autoenrollment.
• All of the DHCP Server server roles must be installed on a domain controller.
• Only one DHCP server in each site must lease IP addresses at any given time.
• DHCP traffic must not cross site boundaries.
• RODCs must not contain personal user information.
###EndCaseStudy###

You need to recommend a solution for the remote access servers. What should you include
in the recommendation?

###BeginCaseStudy###
Case Study: 2
Proseware, Inc
Overview
General Overview
Proseware, Inc. is a pharmaceutical services company that has a sales department, a
marketing department, an operations department, and a human resources department.

Physical Locations
Proseware has two main offices. One of the offices is located in New York. The other office
is located in Chicago. The New York office uses a 172.16.1.0/24 network ID. The Chicago
office uses a 192.168.1.0/24 network ID.
The offices connect to each other by using a high-bandwidth, low-latency WAN link. Each
office connects directly to the Internet.
Existing Environment
The network contains an Active Directory forest named proseware.com. The forest contains
two domains named proseware.com and chicago.proseware.com. All of the user accounts and
the computer accounts in the New York office reside in the proseware.com domain. All of the
user accounts and the computer accounts in the Chicago office reside in the
chicago.proseware.com domain. All DNS zones are Active-Directory-integrated.
Each office is configured as an Active Directory site. The network ID for each office is
associated to the appropriate site.
Each office contains two domain controllers. The domain controllers were recently upgraded
from Windows Server 2008 R2 to Windows Server 2012 R2. The functional level of the
domain and the forest is Windows Server 2003.
The company uses Active Directory user attributes to store the personal information of its
employees in custom attributes.
Existing Servers
The relevant servers are configured as shown in the following table.

All servers run Windows Server 2012 R2.

DC01 has an IPv4 scope. The starting IP address in the range is 172.16.1.100 and the ending
address is 172.16.1.199.
DC03 has an IP4v scope. The starting IP address in the range is 192.168.1.100 and the ending
IP address is 192.168.1.199. There are no exclusion ranges configured on DC01 or DC03.
Requirements
Planned Changes
Proseware plans to implement the following changes:
• Deploy a read-only domain controller (RODC) to the London office.
• Give users remote access to both offices by using a VPN connection from their laptop
or tablet.
• If DC01 fails, ensure that the computers in the New York office can receive IP
addresses within 30 minutes.
• In the New York site, deploy two 50-TB, Fibre Channel SAN disk arrays. Offloaded
Data Transfer (ODX) will be used on both storage arrays. The Hyper-V hosts will use the
new SANs for virtual machine storage.
• Open three additional offices in Montreal, Atlanta, and London. The offices will
connect to each other by using a high-bandwidth, low-latency WAN link. Each office will
connect directly to the Internet.
• For legal reasons, the Montreal site will have its own forest named
montreal.proseware.com.
• The Montreal and Atlanta offices will have local IT administrators to manage the
network infrastructure of their respective office. The London office will not have a local IT
staff. Each office will have approximately 50 client computers.
Technical Requirements
Proseware identifies the following technical requirements:
• Users in the Montreal office must only be allowed to access shares that are located on
File01 and File02. The Montreal users must be prevented from accessing any other servers in
the proseware.com forest regardless of the permissions on the resources,
• Users in the New York office must be able to reconnect to the remote access VPN
servers automatically. Users in the Chicago office must use SSL to connect to the remote
access VPN servers.
• Domain controllers that run Windows Server 2012 R2 and Windows Server 2008 R2
must be able to be deployed to the proseware.com domain.
• Administrators in the New York office must be able to restore objects from the Active
Directory Recycle Bin.
• The DNS servers must be prevented from overwriting the existing DNS entries that
have been stored in cache.
• Each DNS server must be managed by an administrator from the same office as the
DNS server.
• The required time to create new fixed virtual hard disks (VHDs) on the SANs must be
minimized.

• The remote access servers must be able to restrict outgoing traffic based on IP
addresses.
• All certificates must be deployed to all of the client computers by using autoenrollment.
• All of the DHCP Server server roles must be installed on a domain controller.
• Only one DHCP server in each site must lease IP addresses at any given time.
• DHCP traffic must not cross site boundaries.
• RODCs must not contain personal user information.
###EndCaseStudy###

You need to recommend a solution for the RODC
Which attribute should you include in the recommendation?

###BeginCaseStudy###
Case Study: 2
Proseware, Inc
Overview
General Overview
Proseware, Inc. is a pharmaceutical services company that has a sales department, a
marketing department, an operations department, and a human resources department.

Physical Locations
Proseware has two main offices. One of the offices is located in New York. The other office
is located in Chicago. The New York office uses a 172.16.1.0/24 network ID. The Chicago
office uses a 192.168.1.0/24 network ID.
The offices connect to each other by using a high-bandwidth, low-latency WAN link. Each
office connects directly to the Internet.
Existing Environment
The network contains an Active Directory forest named proseware.com. The forest contains
two domains named proseware.com and chicago.proseware.com. All of the user accounts and
the computer accounts in the New York office reside in the proseware.com domain. All of the
user accounts and the computer accounts in the Chicago office reside in the
chicago.proseware.com domain. All DNS zones are Active-Directory-integrated.
Each office is configured as an Active Directory site. The network ID for each office is
associated to the appropriate site.
Each office contains two domain controllers. The domain controllers were recently upgraded
from Windows Server 2008 R2 to Windows Server 2012 R2. The functional level of the
domain and the forest is Windows Server 2003.
The company uses Active Directory user attributes to store the personal information of its
employees in custom attributes.
Existing Servers
The relevant servers are configured as shown in the following table.

All servers run Windows Server 2012 R2.

DC01 has an IPv4 scope. The starting IP address in the range is 172.16.1.100 and the ending
address is 172.16.1.199.
DC03 has an IP4v scope. The starting IP address in the range is 192.168.1.100 and the ending
IP address is 192.168.1.199. There are no exclusion ranges configured on DC01 or DC03.
Requirements
Planned Changes
Proseware plans to implement the following changes:
• Deploy a read-only domain controller (RODC) to the London office.
• Give users remote access to both offices by using a VPN connection from their laptop
or tablet.
• If DC01 fails, ensure that the computers in the New York office can receive IP
addresses within 30 minutes.
• In the New York site, deploy two 50-TB, Fibre Channel SAN disk arrays. Offloaded
Data Transfer (ODX) will be used on both storage arrays. The Hyper-V hosts will use the
new SANs for virtual machine storage.
• Open three additional offices in Montreal, Atlanta, and London. The offices will
connect to each other by using a high-bandwidth, low-latency WAN link. Each office will
connect directly to the Internet.
• For legal reasons, the Montreal site will have its own forest named
montreal.proseware.com.
• The Montreal and Atlanta offices will have local IT administrators to manage the
network infrastructure of their respective office. The London office will not have a local IT
staff. Each office will have approximately 50 client computers.
Technical Requirements
Proseware identifies the following technical requirements:
• Users in the Montreal office must only be allowed to access shares that are located on
File01 and File02. The Montreal users must be prevented from accessing any other servers in
the proseware.com forest regardless of the permissions on the resources,
• Users in the New York office must be able to reconnect to the remote access VPN
servers automatically. Users in the Chicago office must use SSL to connect to the remote
access VPN servers.
• Domain controllers that run Windows Server 2012 R2 and Windows Server 2008 R2
must be able to be deployed to the proseware.com domain.
• Administrators in the New York office must be able to restore objects from the Active
Directory Recycle Bin.
• The DNS servers must be prevented from overwriting the existing DNS entries that
have been stored in cache.
• Each DNS server must be managed by an administrator from the same office as the
DNS server.
• The required time to create new fixed virtual hard disks (VHDs) on the SANs must be
minimized.

• The remote access servers must be able to restrict outgoing traffic based on IP
addresses.
• All certificates must be deployed to all of the client computers by using autoenrollment.
• All of the DHCP Server server roles must be installed on a domain controller.
• Only one DHCP server in each site must lease IP addresses at any given time.
• DHCP traffic must not cross site boundaries.
• RODCs must not contain personal user information.
###EndCaseStudy###

DRAG DROP
You need to recommend changes for the Active Directory infrastructure.
What should you recommend? To answer, drag the appropriate domain and forest functional
levels for proseware.com to the correct locations. Each functional level may be used once,
more than once, or not at all. You may need to drag the split bar between panes or scroll to
view content.

###BeginCaseStudy###
Case Study: 2
Proseware, Inc
Overview
General Overview
Proseware, Inc. is a pharmaceutical services company that has a sales department, a
marketing department, an operations department, and a human resources department.

Physical Locations
Proseware has two main offices. One of the offices is located in New York. The other office
is located in Chicago. The New York office uses a 172.16.1.0/24 network ID. The Chicago
office uses a 192.168.1.0/24 network ID.
The offices connect to each other by using a high-bandwidth, low-latency WAN link. Each
office connects directly to the Internet.
Existing Environment
The network contains an Active Directory forest named proseware.com. The forest contains
two domains named proseware.com and chicago.proseware.com. All of the user accounts and
the computer accounts in the New York office reside in the proseware.com domain. All of the
user accounts and the computer accounts in the Chicago office reside in the
chicago.proseware.com domain. All DNS zones are Active-Directory-integrated.
Each office is configured as an Active Directory site. The network ID for each office is
associated to the appropriate site.
Each office contains two domain controllers. The domain controllers were recently upgraded
from Windows Server 2008 R2 to Windows Server 2012 R2. The functional level of the
domain and the forest is Windows Server 2003.
The company uses Active Directory user attributes to store the personal information of its
employees in custom attributes.
Existing Servers
The relevant servers are configured as shown in the following table.

All servers run Windows Server 2012 R2.

DC01 has an IPv4 scope. The starting IP address in the range is 172.16.1.100 and the ending
address is 172.16.1.199.
DC03 has an IP4v scope. The starting IP address in the range is 192.168.1.100 and the ending
IP address is 192.168.1.199. There are no exclusion ranges configured on DC01 or DC03.
Requirements
Planned Changes
Proseware plans to implement the following changes:
• Deploy a read-only domain controller (RODC) to the London office.
• Give users remote access to both offices by using a VPN connection from their laptop
or tablet.
• If DC01 fails, ensure that the computers in the New York office can receive IP
addresses within 30 minutes.
• In the New York site, deploy two 50-TB, Fibre Channel SAN disk arrays. Offloaded
Data Transfer (ODX) will be used on both storage arrays. The Hyper-V hosts will use the
new SANs for virtual machine storage.
• Open three additional offices in Montreal, Atlanta, and London. The offices will
connect to each other by using a high-bandwidth, low-latency WAN link. Each office will
connect directly to the Internet.
• For legal reasons, the Montreal site will have its own forest named
montreal.proseware.com.
• The Montreal and Atlanta offices will have local IT administrators to manage the
network infrastructure of their respective office. The London office will not have a local IT
staff. Each office will have approximately 50 client computers.
Technical Requirements
Proseware identifies the following technical requirements:
• Users in the Montreal office must only be allowed to access shares that are located on
File01 and File02. The Montreal users must be prevented from accessing any other servers in
the proseware.com forest regardless of the permissions on the resources,
• Users in the New York office must be able to reconnect to the remote access VPN
servers automatically. Users in the Chicago office must use SSL to connect to the remote
access VPN servers.
• Domain controllers that run Windows Server 2012 R2 and Windows Server 2008 R2
must be able to be deployed to the proseware.com domain.
• Administrators in the New York office must be able to restore objects from the Active
Directory Recycle Bin.
• The DNS servers must be prevented from overwriting the existing DNS entries that
have been stored in cache.
• Each DNS server must be managed by an administrator from the same office as the
DNS server.
• The required time to create new fixed virtual hard disks (VHDs) on the SANs must be
minimized.

• The remote access servers must be able to restrict outgoing traffic based on IP
addresses.
• All certificates must be deployed to all of the client computers by using autoenrollment.
• All of the DHCP Server server roles must be installed on a domain controller.
• Only one DHCP server in each site must lease IP addresses at any given time.
• DHCP traffic must not cross site boundaries.
• RODCs must not contain personal user information.
###EndCaseStudy###

You run the Get-DNSServercmdlet on DC01 and receive the following output:

You need to recommend changes to DC01. Which attribute should you recommend
modifying?

###BeginCaseStudy###
Case Study: 3
Litware, Inc
Overview
Litware, Inc., is a manufacturing company. The company has a main office and two branch
offices. The main office is located in Seattle. The branch offices are located in Los Angeles
and Boston.
Existing Environment
Active Directory

The network contains an Active Directory forest named litwareinc.com. The forest contains a
child domain for each office. The child domains are named boston.litwareinc.com and
la.litwareinc.com. An Active Directory site exists for each office.
In each domain, all of the client computer accounts reside in an organizational unit (OU)
named AllComputers and all of the user accounts reside in an OU named AllUsers.
All domain controllers run Windows Server 2008 R2 and are configured as DNS servers.
The functional level of the domain and the forest is Windows Server 2008.
Network Infrastructure
The main office has the following servers:
• Five physical Hyper-V hosts that run Windows Server 2012
• Three virtual file servers that run Windows Server 2008 R2
• One physical DHCP server that runs Windows Server 2008 R2
• Ten physical application servers that run Windows Server 2012
• One virtual IP Address Management (IPAM) server that runs Windows Server 2012
• One virtual Windows Server Update Services (WSUS) server that runs Windows
Server 2008 R2
• One physical domain controller and two virtual domain controllers that run Windows
Server 2008 R2
Each branch office has following servers:
• One virtual file server that runs Windows Server 2008 R2
• Two physical Hyper-V hosts that run Windows Server 2012
• One physical DHCP server that runs Windows Server 2008 R2
• One physical domain controller and two virtual domain controllers that run Windows
Server 2008 R2
All of the offices have a high-speed connection to the Internet. The offices connect to each
other by using T1 leased lines.
The IPAM server in the main office gathers data from the DNS servers and the DHCP servers
in all of the offices.
Requirements
Planned Changes
The company plans to implement the following changes:
• Implement the Active Directory Recycle Bin.
• Implement Network Access Protection (NAP).
• Implement Folder Redirection in the Boston office only.
• Deploy an application named Appl to all of the users in the Boston office only.
• Migrate to IPv6 addressing on all of the servers in the Los Angeles office. Some
application servers in the Los Angeles office will have only IPv6 addresses.
Technical Requirements
The company identifies the following technical requirements:
• Minimize the amount of administrative effort whenever possible.
• Ensure that NAP with IPSec enforcement can be configured.

• Rename boston.litwareinc.com domain to bos.litwareinc.com.
• Migrate the DHCP servers from the physical servers to a virtual server that runs
Windows Server 2012.
• Ensure that the members of the Operators groups in all three domains can manage the
IPAM server from their client computer.
VPN Requirements
You plan to implement a third-party VPN server in each office. The VPN servers will be
configured as RADIUS clients. A server that runs Windows Server 2012 will perform
RADIUS authentication for all of the VPN connections.
Visualization Requirements
The company identifies the following visualization requirements:
• Virtualize the application servers.
• Ensure that the additional domain controllers for the branch offices can
be deployed by using domain controller cloning.
• Automatically distribute the new virtual machines to Hyper-V hosts
based on the current resource usage of the Hyper-V hosts.
Server Deployment Requirements
The company identifies the following requirements for the deployment of new servers on the
network:
• Deploy the new servers over the network.
• Ensure that all of the server deployments are done by using multicast.
Security Requirements
A new branch office will open in Chicago. The new branch office will have a single readonly domain controller (RODC). Confidential attributes must not be replicated to the Chicago
office.
###EndCaseStudy###

You need to recommend a server deployment strategy for the main office that meets the
server deployment requirements.
What should you recommend installing in the main office?