###BeginCaseStudy###
Case Study: 10
Fabrikam Inc
Scenario
COMPANY OVERVIEW
Fabrikam Inc. is a manufacturing company that has a main office and a branch office.
PLANNED CHANGES
You plan to deploy a failover cluster named Cluster1 in the branch office. Cluster1 will be
configured to meet the following requirements:
• The cluster will host eight virtual machines (VMs).
• The cluster will consist of two nodes named Node1 and Node2.
• The quorum mode for the cluster will be set to Node and Disk Majority.
• A user named Admin1 will configure the virtual switch configuration of the VMs.
• The cluster nodes will use shared storage on an iSCSI Storage Area Network (SAN).
You plan to configure a VM named File2 as a file server. Users will store confidential files
on File2. You plan to deploy a Microsoft Forefront Threat Management Gateway (TMG)
server in each site. The Forefront TMG server will be configured as a Web proxy.
EXISTING ENVIRONMENT
The research department is located in the branch office. Research users frequently travel to
the main office.
Existing Active Directory/Directory Services
The network contains a single-domain Active Directory forest named fabrikam.com. The
functional level of the forest is Windows Server 2008. The relevant organizational units
(OUs) for the domain are configured as shown in the following table.
The relevant sites for the network are configured shown in the following table.
The relevant group policy objects (GPOs) are configured as shown in the following table.
Existing Network Infrastructure
All users run windows server 2008 R2. The relevant servers are configured as shown in
following table.
WSUS2 is configured as a downstream replica server. File1 contains a share named
Templates. Users access the Templates share by using the path \\fabrikam.com\dfs\templates
TECHNICAL REQUIREMENTS
File1 has the Distributed File System (DFS) Replication role service and the DFS
Namespaces role service installed.
• Fabrikam must meet the following requirements:
• Minimize the cost of IT purchases.
• Minimize the potential attack surface on the servers.
• Minimize the number of rights assigned to administrators.
• Minimize the number of updates that must be installed on the servers.
• Ensure that Internet Explorer uses the local ForeFront TMG server to connect to the
Internet.
• Ensure that all client computers continue to receive updates from WSUS if a WSUS
server fails.
• Prevent unauthorized users from accessing the data stored on the VMs by making
offline copies of the VM files.
Fabrikam must meet the following requirements for the Templates share:
• Ensure that users access the files in the Templates share from a server in their local
site.
• Ensure that users always use the same UNC path to access the Templates share,
regardless of the site in which the users are located.
###EndCaseStudy###
You need to recommend the minimum number of logical unit numbers (LUNs) that must be
provisioned for Cluster1. The recommendation must support the company’s planned changes.
Which number should you recommend?
A.
1
B.
2
C.
8
D.
9
Explanation:
LUN Stands for “Logical Unit Number.” LUNs are used to identify SCSI devices, such as external hard
drives, connected to a computer. Each device is assigned a LUN, from 0 to 7, which serves as the
device’s unique address.
LUNs can also be used for identifying virtual hard disk partitions, which are used in RAID
configurations. For example, a single hard drive may be partitioned into multiple volumes. Each
volume can then be assigned a unique LUN.
A failover cluster is a group of independent computers that work together to increase the availability
of applications and services. The clustered servers (called nodes) are connected by physical cablesand by software. If one of the cluster nodes fails, another node begins to provide service (a process
known as failover).
Users experience a minimum of disruptions in service.
In simple terms, the quorum for a cluster is the number of elements that must be online for that
cluster to continue running. In effect, each element can cast one “vote” to determine whether the
cluster continues running. The voting elements are nodes or, in some cases, a disk witness or file
share witness. Each voting element (with the exception of a file share witness) contains a copy of the
cluster configuration, and the Cluster service works to keep all copies synchronized at all times.
There are four quorum modes:
Node Majority: Each node that is available and in communication can vote. The cluster functions
only with a majority of the votes, that is, more than half.
Node and Disk Majority: Each node plus a designated disk in the cluster storage (the “disk witness”)
can vote, whenever they are available and in communication. The cluster functions only with a
majority of the votes, that is, more than half.
Node and File Share Majority: Each node plus a designated file share created by the administrator
(the “file share witness”) can vote, whenever they are available and in communication. The cluster
functions only with a majority of the votes, that is, more than half.
No Majority: Disk Only: The cluster has quorum if one node is available and in communication with a
specific disk in the cluster storage.
Choosing the quorum mode for a particular cluster
The following table describes clusters based on the number of nodes and other cluster
characteristics, and lists the quorum mode that is recommended in most cases.
A “multi-site” cluster is a cluster in which an investment has been made to place sets of nodes and
storage in physically separate locations, providing a disaster recovery solution.
as the Quorum will be set to Node And Disk Majority this means we need an even number of nodes
which we have (node1 & node2)
