Which cmdlets should you run?
###BeginCaseStudy###
Case Study: 1
Contoso Ltd (A)
Overview
Contoso, Ltd., is a healthcare company in Europe that has 2,000 users. The company is
migrating to Windows Server 2012.
The company has two main offices and two branch offices. The main offices are located in
Paris and Amsterdam. One of the branch offices is a sales office located in Berlin. The other
branch office is a research office located in Brussels.
The offices connect to each other by using a WAN link.
Current Environment
Active Directory
The network contains an Active Directory forest named contoso.com. An Active Directory
site exists for each office.
The forest contains a child domain named research.contoso.com.
The functional level of both the domains is Windows Server 2008.
In each site, there are two domain controllers for the contoso.com domain and two domain
controllers for the research.contoso.com domain. The domain controllers run Windows
Server 2008 R2.
All of the domain controllers are global catalog servers.
The FSMO roles were not moved since the domains were deployed.
Network Infrastructure
All servers run Windows Server 2008 R2.
Each user has a laptop computer that runs Windows 7.
The company has 10 print servers. Each print server contains several shared printers.
The company has 10 file servers that have the following disk configurations:
• A simple volume named C that is the System and Boot volume and is
formatted NTFS
• A mounted virtual hard disk (VHD) named DATA that is formatted
NTFS
• A simple volume named D that is formatted FAT32
• A simple volume named E that is formatted NTFS
• A Clustered Shared Volume (CSV)
The Paris office contains a server named PA1. The Amsterdam office contains a server
named AM1. Both servers have the following server roles installed:
• DNS Server
• DHCP Server
• Remote Access
The DNS servers are configured to use the DNS servers of the company’s Internet Service
Provider (ISP) as forwarders.
Users often work remotely. The users access the internal network by using an SSTP-based
VPN connection.
Requirements
Planned Changes
The company plans to implement the following changes:
• Create a child domain named sales.contoso.com. Only the domain controllers in
sales.contoso.com will host a zone for the sales.contoso.com domain. The domain
controllers in sales.contoso.com will run Windows Server 2012. The client computers
in sales.contoso.com will use the sales.contoso.com domain controllers as their DNS
servers.
• Implement two servers in the Amsterdam office and two servers in the Paris office to
replace PA1 and AMI. These new servers will run Windows Server 2012 and will not
have shared storage.
• Decommission the research.contoso.com domain. All of the users and the Group
Policy objects (GPOs) in research.contoso.com will be migrated to contoso.com.
• Migrate the existing print queues to virtualized instances of Windows Server 2012.
• Migrate the file servers to new servers that run Windows Server 2012.
• Implement RADIUS authentication for VPN connections.
• Deploy Windows Server 2012 to all new servers.
Technical Requirements
The company identifies following technical requirements:
• All changes to Group Policies must be logged.
• Network Access Protection (NAP) policies must be managed centrally.
• Core networking services in each office must be redundant if a server
fails.
• The possibility of IP address conflicts during the DHCP migration must
be minimized.
• A central log of the IP address leases and the users associated to
those leases must be created.
• All of the client computers must be able to resolve internal names and
internet names.
• Administrators in the Paris office need to deploy a series of desktop
restrictions to the entire company by using Group Policy.
• The new sales.contoso.com domain will contain a web application that
will access data from a Microsoft SQL Server located in the contoso.com
domain. The web application must use integrated Windows authentication.
Users’ credentials must be passed from the web applications to the SQL
Server.
###EndCaseStudy###
After the planned upgrade to Windows Server 2012, you restore a user account from the
Active Directory Recycle Bin.
You need to replicate the restored user account as quickly as possible.
Which cmdlets should you run?
Which tool should you use?
###BeginCaseStudy###
Case Study: 1
Contoso Ltd (A)
Overview
Contoso, Ltd., is a healthcare company in Europe that has 2,000 users. The company is
migrating to Windows Server 2012.
The company has two main offices and two branch offices. The main offices are located in
Paris and Amsterdam. One of the branch offices is a sales office located in Berlin. The other
branch office is a research office located in Brussels.
The offices connect to each other by using a WAN link.
Current Environment
Active Directory
The network contains an Active Directory forest named contoso.com. An Active Directory
site exists for each office.
The forest contains a child domain named research.contoso.com.
The functional level of both the domains is Windows Server 2008.
In each site, there are two domain controllers for the contoso.com domain and two domain
controllers for the research.contoso.com domain. The domain controllers run Windows
Server 2008 R2.
All of the domain controllers are global catalog servers.
The FSMO roles were not moved since the domains were deployed.
Network Infrastructure
All servers run Windows Server 2008 R2.
Each user has a laptop computer that runs Windows 7.
The company has 10 print servers. Each print server contains several shared printers.
The company has 10 file servers that have the following disk configurations:
• A simple volume named C that is the System and Boot volume and is
formatted NTFS
• A mounted virtual hard disk (VHD) named DATA that is formatted
NTFS
• A simple volume named D that is formatted FAT32
• A simple volume named E that is formatted NTFS
• A Clustered Shared Volume (CSV)
The Paris office contains a server named PA1. The Amsterdam office contains a server
named AM1. Both servers have the following server roles installed:
• DNS Server
• DHCP Server
• Remote Access
The DNS servers are configured to use the DNS servers of the company’s Internet Service
Provider (ISP) as forwarders.
Users often work remotely. The users access the internal network by using an SSTP-based
VPN connection.
Requirements
Planned Changes
The company plans to implement the following changes:
• Create a child domain named sales.contoso.com. Only the domain controllers in
sales.contoso.com will host a zone for the sales.contoso.com domain. The domain
controllers in sales.contoso.com will run Windows Server 2012. The client computers
in sales.contoso.com will use the sales.contoso.com domain controllers as their DNS
servers.
• Implement two servers in the Amsterdam office and two servers in the Paris office to
replace PA1 and AMI. These new servers will run Windows Server 2012 and will not
have shared storage.
• Decommission the research.contoso.com domain. All of the users and the Group
Policy objects (GPOs) in research.contoso.com will be migrated to contoso.com.
• Migrate the existing print queues to virtualized instances of Windows Server 2012.
• Migrate the file servers to new servers that run Windows Server 2012.
• Implement RADIUS authentication for VPN connections.
• Deploy Windows Server 2012 to all new servers.
Technical Requirements
The company identifies following technical requirements:
• All changes to Group Policies must be logged.
• Network Access Protection (NAP) policies must be managed centrally.
• Core networking services in each office must be redundant if a server
fails.
• The possibility of IP address conflicts during the DHCP migration must
be minimized.
• A central log of the IP address leases and the users associated to
those leases must be created.
• All of the client computers must be able to resolve internal names and
internet names.
• Administrators in the Paris office need to deploy a series of desktop
restrictions to the entire company by using Group Policy.
• The new sales.contoso.com domain will contain a web application that
will access data from a Microsoft SQL Server located in the contoso.com
domain. The web application must use integrated Windows authentication.
Users’ credentials must be passed from the web applications to the SQL
Server.
###EndCaseStudy###
You implement a new virtualized print server that runs Windows Server 2012.
You need to migrate the print queues.
Which tool should you use?
What method should you use to deploy servers?
###BeginCaseStudy###
Case Study: 1
Contoso Ltd (A)
Overview
Contoso, Ltd., is a healthcare company in Europe that has 2,000 users. The company is
migrating to Windows Server 2012.
The company has two main offices and two branch offices. The main offices are located in
Paris and Amsterdam. One of the branch offices is a sales office located in Berlin. The other
branch office is a research office located in Brussels.
The offices connect to each other by using a WAN link.
Current Environment
Active Directory
The network contains an Active Directory forest named contoso.com. An Active Directory
site exists for each office.
The forest contains a child domain named research.contoso.com.
The functional level of both the domains is Windows Server 2008.
In each site, there are two domain controllers for the contoso.com domain and two domain
controllers for the research.contoso.com domain. The domain controllers run Windows
Server 2008 R2.
All of the domain controllers are global catalog servers.
The FSMO roles were not moved since the domains were deployed.
Network Infrastructure
All servers run Windows Server 2008 R2.
Each user has a laptop computer that runs Windows 7.
The company has 10 print servers. Each print server contains several shared printers.
The company has 10 file servers that have the following disk configurations:
• A simple volume named C that is the System and Boot volume and is
formatted NTFS
• A mounted virtual hard disk (VHD) named DATA that is formatted
NTFS
• A simple volume named D that is formatted FAT32
• A simple volume named E that is formatted NTFS
• A Clustered Shared Volume (CSV)
The Paris office contains a server named PA1. The Amsterdam office contains a server
named AM1. Both servers have the following server roles installed:
• DNS Server
• DHCP Server
• Remote Access
The DNS servers are configured to use the DNS servers of the company’s Internet Service
Provider (ISP) as forwarders.
Users often work remotely. The users access the internal network by using an SSTP-based
VPN connection.
Requirements
Planned Changes
The company plans to implement the following changes:
• Create a child domain named sales.contoso.com. Only the domain controllers in
sales.contoso.com will host a zone for the sales.contoso.com domain. The domain
controllers in sales.contoso.com will run Windows Server 2012. The client computers
in sales.contoso.com will use the sales.contoso.com domain controllers as their DNS
servers.
• Implement two servers in the Amsterdam office and two servers in the Paris office to
replace PA1 and AMI. These new servers will run Windows Server 2012 and will not
have shared storage.
• Decommission the research.contoso.com domain. All of the users and the Group
Policy objects (GPOs) in research.contoso.com will be migrated to contoso.com.
• Migrate the existing print queues to virtualized instances of Windows Server 2012.
• Migrate the file servers to new servers that run Windows Server 2012.
• Implement RADIUS authentication for VPN connections.
• Deploy Windows Server 2012 to all new servers.
Technical Requirements
The company identifies following technical requirements:
• All changes to Group Policies must be logged.
• Network Access Protection (NAP) policies must be managed centrally.
• Core networking services in each office must be redundant if a server
fails.
• The possibility of IP address conflicts during the DHCP migration must
be minimized.
• A central log of the IP address leases and the users associated to
those leases must be created.
• All of the client computers must be able to resolve internal names and
internet names.
• Administrators in the Paris office need to deploy a series of desktop
restrictions to the entire company by using Group Policy.
• The new sales.contoso.com domain will contain a web application that
will access data from a Microsoft SQL Server located in the contoso.com
domain. The web application must use integrated Windows authentication.
Users’ credentials must be passed from the web applications to the SQL
Server.
###EndCaseStudy###
What method should you use to deploy servers?
What should you recommend?
###BeginCaseStudy###
Case Study: 2
Proseware, Inc (A)
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
auto-enrollment.
• 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###
HOTSPOT
You need to recommend a configuration for the DHCP infrastructure.
What should you recommend? To answer, select the appropriate options in the answer area.
What should you include in the recommendation?
###BeginCaseStudy###
Case Study: 2
Proseware, Inc (A)
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
auto-enrollment.
• 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 trust model.
What should you include in the recommendation?
What should you recommend?
###BeginCaseStudy###
Case Study: 2
Proseware, Inc (A)
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
auto-enrollment.
• 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 the VPN protocols for Proseware.
What should you recommend? To answer, drag the appropriate VPN protocols to the correct
offices. Each protocol 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
What should you recommend?
###BeginCaseStudy###
Case Study: 2
Proseware, Inc (A)
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
auto-enrollment.
• 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###
HOTSPOT
You need to recommend a storage configuration for the Hyper-V hosts.
What should you recommend? To answer, select the appropriate options in the answer area.
What is the best approach to achieve the goal?
###BeginCaseStudy###
Case Study: 2
Proseware, Inc (A)
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
auto-enrollment.
• 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 deployment method for Proseware.
What is the best approach to achieve the goal? More than one answer choice may achieve
the goal. Select the BEST answer.
What should you include in the recommendation?
###BeginCaseStudy###
Case Study: 2
Proseware, Inc (A)
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
auto-enrollment.
• 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?
What should you recommend?
###BeginCaseStudy###
Case Study: 2
Proseware, Inc (A)
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
auto-enrollment.
• 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.
