###BeginCaseStudy###
Case Study: 6
Contoso Ltd Case C
Background
Overview
Contoso, Ltd., is a manufacturing company. The company has offices in Chicago and Seattle.
Each office contains two data centers. All of the data centers and sites for the company have
network connectivity to each other. The company uses a single Active Directory Domain
Services (AD DS) domain.
Contoso is growing rapidly and needs to expand its computer infrastructure.
Current Environment Chicago Office
The Chicago office contains a primary data center and a backup data center. A Hyper-V
cluster named Clusterl.contoso.com resides in the primary data center. The cluster has a
multiple network path configured. The cluster includes two unused SQL Server virtual
machines (VMs) named SQL-SERVER1 and SQL-SERVER2. The cluster also includes a
Hyper-V Host group named Chi-Primary.
Clusterl.contoso.com contains the following servers:
• CHI1-HVNODE1.contoso.com
• CHI1-HVNODE2.contoso.com
• CHI1-HVNODE3.contoso.com
• CHI1-HVNODE4.contoso.com
The backup data center for the Chicago office is located on a Hyper-V cluster named
Cluster2.contoso.com. The cluster has a single network path configured. The cluster includes
a Hyper-V Host group named Chi-Backup.
Cluster2.contoso.com contains the following servers:
• CHI2-HVNODEl.contoso.com
• CHI2-HVNODE2.contoso.com
• CHI2-HVNODE3.contoso.com
• CHI2-HVNODE4.contoso.com
In addition, the Chicago office contains two standalone Hyper-V servers named CHIHVSERVER1.contoso.com and CHI-HVSERVER2.contoso.com.
There are also four newly built servers:
• CHI-SERVERl.contoso.com
• CHI-SERVER2.contoso.com
• CHI-SERVER3.contoso.com
• CHI-SERVER4.contoso.com
All the servers in the Chicago office run Windows Server 2012. Any future servers that are
deployed in the Chicago office must also run Windows Server 2012.
All servers in the Chicaoo office use the subnet 10.20.xx.
Current Environment Seattle Office
The Seattle office contains a primary data center and a backup data center. The primary data
center is located on a Hyper-V cluster named Cluster3.contoso.com. The cluster has a
multiple network path configured. The cluster includes two unused SQL Server virtual
machines named SQL-SERVER3 and SQL-SERVERS The cluster includes a Hyper-V Host
group named Sea-Primary.
Cluster3.contoso.com contains the following servers:
• SEA3-HVNODEl.contoso.com
• SEA3-HVNODE2.contoso.com
• SEA3-HVNODE3.contoso.com
• SEA3-HVNODE4.contoso.com
The backup data center for the Seattle office is located on a Hyper-V cluster named
Cluster4.contoso.com. The cluster has a single network path configured. The cluster includes
a Hyper-V Host group named Sea-Backup.
Cluster4.contoso.com contains the following servers:
• SEA4-HVNODEl.contoso.com
• SEA4-HVNODE2.contoso.com
• SEA4-HVNODE3.contoso.com
• SEA4-HVNODE4.contoso.com
In addition, the Seattle office contains two standalone Hyper-V servers named SEAHVSERVERl.contoso.com and SEA-HVSERVER2.contoso.com.
There are also four newly built servers:
• SEA-SERVERl.contoso.com
• SEA-SERVER2.contoso.com
• SEA-SERVER3.contoso.com
• SEA-SERVER4.contoso.com
All servers in the Seattle office run Windows Server 2012 R2. Any future servers that are
deployed in the Seattle office must also run Windows Server 2012 R2.
All servers in the Seattle office use the subnet 10.10.x.x.
Business Requirements
Apps
Contoso plans to deploy new applications to make its departments more efficient.
App1
Contoso must create a new application named App1 for the human resources (HR)
department. The infrastructure for App1 must reside in a virtual environment and the data
files for App1 must reside on a single shared disk. In addition, the infrastructure for App1
must meet the following requirements:
• maximize data protection
• withstand the loss of a single guest virtual machine
• withstand the loss of a single physical server
To support App1, Contoso must deploy a new cluster named Applcluster.contoso.com. The
cluster has the following requirements:
• It must span multiple sites.
• It must support dynamic quorums.
• It must prevent failures caused by a 50% split.
App2
Contoso must create a new application named App2. To support App2, Contoso must deploy
a new SQL Server cluster. The cluster must not be part of the domain.
The server deployment team that will install the cluster has limited permissions. The server
deployment team does not have the ability to create objects in Active Directory.
Virtualization and Storage
New VMs
Any new VMs that are deployed to the Hyper-V cluster in Cluster3.contoso.com have the
following requirements:
• New SQL Server VMs must be deployed only to odd-numbered
servers in the cluster.
• All other new VM guests must be deployed to any available server in
the cluster.
New VDE
The company needs a highly available file share cluster for a new Virtual Desktop
Environment (VDE). It has the following requirements:
• The file share cluster must withstand the loss of a single server.
• The file share cluster must withstand the loss of a single network path.
• The file share cluster must use the least amount of disk space.
New virtualized SQL Server cluster
Contoso must create a new application for manufacturing. The company needs a new
virtualized SQL Server cluster named VM-SQLclusterl.contoso.com. It has the following
requirements:
• The cluster must use a shared virtual hard disk.
• The cluster must have two nodes named VM-SQLNODE1.contoso.com and VM-SQL-NODE2.contoso.com.
Highly available storage solution
The company is deploying new hardware that will replace the existing Hyper-V clusters. The
new file share cluster must have a highly available storage solution for a Hyper-V
environment. It has the following requirements:
• The new file share cluster must support guest VM clusters.
• The storage cannot reside on any of the physical Hyper-V hosts.
###EndCaseStudy###
You need to implement a new highly available storage solution for the Hyper-V environment. Which
servers should you include in the scale-out file cluster?
A.
CHI-SERVER1 and CHI-SERVER2
B.
SEA3-HVNODE1 and SEA3-HVNODE2
C.
SEA-SERVER1 and SEA-SERVER2
D.
CHIl-HVNODE1 and CHI1-HVNODE2
why B and not D ?
Business Requirement:
It must support dynamic quorums.
It must prevent failures caused by a 50% split.
https://technet.microsoft.com/en-us/library/dn265972.aspx
In Windows Server 2012 R2, if the cluster is configured to use dynamic quorum (the default), the witness vote is also dynamically adjusted based on the number of voting nodes in current cluster membership. If there are an odd number of votes, the quorum witness does not have a vote. If there is an even number of votes, the quorum witness has a vote.
Both nodes got to be Windows Server 2012 R2.
It does not make sense to me to have 2 nodes of a cluster provide storage to the remaining cluster nodes.
Answer C makes more sense to me.
C: SEA-SERVER1 and SEA-SERVER2 are on a stand-alone Hyper-V cluster.
I would go with B since they are in the domain and are Win 2012 R2.
Also, Dynamic Quorum is a 2021 R2 feature:
https://technet.microsoft.com/en-us/library/dn265972.aspx
This is a tricky one but I think they are trying to ensure you understand that wherever possible loopback configurations for Hyper-V over SMB should be avoided
http://blogs.technet.com/b/josebda/archive/2012/11/14/windows-server-2012-file-server-tip-avoid-loopback-configurations-for-hyper-v-over-smb.aspx
The servers must be on the Seattle network (For Dynamic Quorum in 2012 R2)
SEA3-HVNODE1 and SEA3-HVNODE2 are a Hyper-V cluster and should be avoided if the reason above is true
So we are left with C as the answer
SEA-SERVER1 and SEA-SERVER2 are newly built servers in the domain and can be configured as a separate SoFS cluster thus avoiding loopback
What’s the reasoning for no one considering A as a possibility? This is what the premium dump has listed after updating the answer from B.
JamesL has the best reasoning for this tricky question. Two concepts being tested, so might have a lot of weight if it’s on the test: Dynamic Quorum and Loopback config
Chicago servers are running 2012
Seattle servers are running 2012 R2 (Dynamic Quorum requires 2012 R2)
=That rules out Chicaco servers
Hyper-V should not be installed on the same server as a File server (creates the “Loopback Configuration” Microsoft advises against).
=Rules out the HVNODEs
Only answer left is the newly built servers SEA-SERVER1, SEA-SERVER2, SEA-SERVER3, SEA-SERVER4. So C. is the correct answer.
Dynamic Quorum was introduced in Windows 2012. It is just enabled by default in Windows 2012 R2.
The answer is correct which is C, however not because of Dynamic Quorum being a new feature in Windows 2012 R2. But because of Tie breaker for 50% node split which is a new feature in Windows 2012 R2. It was misunderstood that the statement “It must prevent failures caused by a 50% split” meant dynamic quorum. But it actually is referring to the Tie Breaker.
https://technet.microsoft.com/en-us/library/dn265972(v=ws.11).aspx#BKMK_TieBreak
Yes, c is the correct answer
The new file share cluster must support guest VM clusters.
• The storage cannot reside on any of the physical Hyper-V hosts.
###EndCaseStudy###
This rules out all non R2 servers (Chicago) and all Hyper-V hosts.
Only C is left
C is correct.
1. The new file share cluster must support guest VM clusters.
Rules out none R2 options, so only on Seattle’s servers.
Reference https://technet.microsoft.com/en-us/library/dn281956(v=ws.11).aspx .
2. The storage cannot reside on any of the physical Hyper-V hosts.
Rules out HY host machines.