###BeginCaseStudy###
Title: Case Study
The following testlet will present a Case Study followed by [count] multiple choice question(s), [count] create a tree question(s), [count] build list and reorder question
(s) and [count] drop and connect question(s).
You will have [count] minutes to complete the testlet.
For help on how to answer the questions, click the Instuctions button on the question screen.
Overview
Overview
Background
Main Office
Main Office Clusters
The data center has a cluster named cluster1 that runs Windows Server 2012 R2. Cluster1 uses the domain Cluster1.contoso.com. The cluster is partially
configured and has three server nodes.
The cluster uses storage area network (SAN) attached storage. There are no cluster roles assigned.
Cluster1 contains the following domains:
● CLUS1-SRV1.contoso.com
● CLUS1-SRV2.contoso.com
● CLUS1-SRV3.contoso.com
In addition, the environment contains two Windows Server 2012 R2 Hyper-V clusters named
HV-Cluster1 and HV-Cluster2. HV-Cluster1 and HV-Cluster2 use Fibre Channel SAN storage.
The Hyper-V clusters contain server nodes as shown in the following table:
Main office network
Main office network
The main office data center uses a virtual local area network (VLAN) to deploy servers by using PXE boot. The VLAN ID is 30, and it uses the subnet
10.15.30.0/24.
There is a firewall that prevents all inbound connections to all servers in the data center except for the subnet 10.50.50.0/24.
Contoso has two additional VLANs as shown in the following table;
SAN storage configuration for Cluster1
SAN storage configuration for Cluster1
The Windows PowerShell command Get-ClusterSharedVolumeState –name “Cluster1.contoso.com” returns the following data:
Name: Cluster Disk X
VolumeName: \\\\?\\Volume {2297f079-53c2-41e9-94d1-483d61ea67d7}\\
Node: Clus1-Srv1
StateInfo: Direct
VolumeFriendName: Volume1
FileSystemRedirectedIOReason:
BlockRedirectedIOReason:
Name: Cluster Disk Y
VolumeName: \\\\?\\Volume {0312ef48-74c7-4a4d-946e-4bb4a397ab1f}\\
Node: Clus1-Srv2
Statelnfo: FileSystemRedirected
VolumeFriendName: Volume2
FileSystemRedirectedIOReason: UserRequest
BlockRedirectedIOReason: NotBlockedRedirected
Name: Cluster Disk Z
VolumeName: \\\\?\\Volume {c4689cef-83e3-4f47-9eaf-161a9e31c4a0}\\
Node: Clus1-Srv3
Statelnfo: Block Redirected
VolumeFriendName: Volume3
FileSystemRedirectedIOReason: NotFileSystemRedirected
BlockRedirectedIOReason: NoDiskConnectivity
Sales Office
Sales Office
Sales office servers
The data center has the following virtual and physical servers:
● two standalone servers that are not joined to the contoso.com domain named SERVER1 and SERVER2
● two dedicated storage servers that are allocated, but not yet built, named STORAGE1 and STORAGE2
STORAGE1 and STORAGE2 each have 48 GB of RAM and 10 1-TB SAS disks.
Sales office clusters
Sales office clusters
The data center has a cluster named Cluster2 that runs Windows Server 2012 R2. Cluster2 uses the domain Cluster2.contoso.com.
The cluster is partially configured and has three server nodes. The cluster uses SAN attached storage. There are no cluster roles assigned.
Cluster2 contains the following domains:
● CLUS2-SRV1.contoso.com
● CLUS2-SRV2.contoso.com
● CLUS2-SRV3.contoso.com
In addition, the environment contains two Windows Server 2012 R2 Hyper-V clusters named HV-Cluster3 and HV-Cluster4. HV-Cluster3 and HV-Cluster4 use
Fibre Channel SAN storage. The Hyper-V clusters contain server nodes as shown in the following table:
SAN storage configuration for Cluster4
SAN storage configuration for Cluster4
The Windows PowerShell command
Get-ClusterSharedVolumeState –name “Cluster4.contoso.com” returns the following data:
Name: Cluster Disk X
VolumeName: \\\\?\\Volume {09009c16-d33e-49fb-aa6a-abdb31921e76}\\
Node: Clus2-Srv1
StateInfo: Direct
VolumeFriendName: Volume1
FileSystemRedirectedIOReason: NotFileSystemRedirected
BlockRedirectedIOReason: NotBlockedRedirected
Name: Cluster Disk Y
VolumeName: \\\\?\\Volume {a6cedeab-6966-4eb0-b5c1-b819c6c34fbf}\\
Node: Clus2-Srv2
Statelnfo: FileSystemRedirected
VolumeFriendName: Volume2
FileSystemRedirectedIOReason:
BlockRedirectedIOReason:
Name: Cluster Disk Z
VolumeName: \\\\?\\Volume { }\\
Node: Clus2-Srv3
Statelnfo:
VolumeFriendName: Volume3
FileSystemRedirectedIOReason:
BlockRedirectedIOReason:
###EndCaseStudy###
Drag and Drop Question
You need to ensure that all new production Hyper-V virtual machines can be deployed correctly.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the
correct order.
Select and Place:
Answer: 
Incorrect order.
Proper order is:
Create a new logical network
Add a network site
Add an Uplink Port Profile
Create a new logical switch
FYI, there is information missing from this Case Study. The Overview, Background, Main Office Network information.
I made a comment later on in the questions saying DAL-FS1/FS2 are not mentioned. They are in the real Case.
Sorry “Main Office”, not main office network information.
“You will need at least one port profile for uplinks before you can create a logical switch.”
https://technet.microsoft.com/en-us/library/jj628166(v=sc.12)