###BeginCaseStudy###

Testlet 1
Overview
Contoso, Ltd. is a manufacturing company.
Contoso has a main office and six branch offices. The main office is located in Toronto. The branch offices are
located in New York, Seattle, Miami, Montreal, Los Angeles, and Vancouver.
Existing Environment
Active Directory Environment
The network contains an Active Directory forest named contoso.com. The forest contains a child domain for
each office.
Active Directory currently contains 7,500 user accounts and 15,000 computer accounts.
Network Infrastructure
All servers are located in a data center in Toronto. The data center contains multiple subnets that are separated
by firewalls.
The Toronto data center contains a cluster that runs Microsoft SQL Server 2008 Enterprise Service Pack 1
(SP1).
Four servers are unused and are being considered as potential Hyper-V hosts. The servers are configured as
shown in the following table.

All of the servers being considered as potential Hyper-V hosts have both locally attached storage and access to
a SAN.
Help Desk Environment
Contoso uses a help desk ticketing system that was developed in-house. Fifty help desk agents have access to
the ticketing system.
The ticketing system currently tracks:
An average of two new incidents per month, per client computer
An average of 2,000 change requests per month
Disaster Recovery Environment
Contoso uses a third-party backup solution. Backups are scheduled for the servers in the Seattle office as
follows:
The daily incremental backups total 10 GB.
The total size of data to back up is 100 GB.
Backed up data is retained for 10 business days.
Problem Statements
The original developers of the help desk ticketing system are no longer employed by Contoso and maintenance
of the system is becoming an issue.
RequirementsPlanned Changes
Contoso plans to move the IT infrastructure to a private cloud.
Whenever possible, hardware and software costs must be minimized.
Contoso plans to open a small office in Beijing. System Center 2012 App Controller will be used to manage
applications. The display names of the applications will be in Simplified Chinese Pinyin IME.
New physical servers will be deployed by using System Center 2012 Configuration Manager from a server
named Server5. Server5 will also be a PXE service point.
The current backup solution will be replaced with System Center 2012 Data Protection Manager (DPM).
A public key infrastructure (PKI) will be deployed to issue and manage certificates. The PKI deployment must
be made as secure as possible.
Hardware load balancers will be deployed for use in the deployment of private cloud services.
Cloud Requirements
Contoso plans to implement a cloud solution that meets the following requirements:
Stores all virtual machines on the SAN only.
Uses SAN copy to provision the virtual machines.
Provides the ability to manage the resolution of incidents.
Contains managed virtual machines across both private and public clouds.
Provides the ability to customize the settings of management packs provided by Microsoft.
Collects security events from all of the servers running in the private cloud and provides centralized
reporting on the events.
App1 Requirements
A new application named App1 will be deployed to the private cloud. App1 is a three-tier application that
contains the following components:
A front-end tier that runs a web server. The tier must be highly available and capable of being quickly scaled
out if required.
A middle tier that runs an application server.
A back-end tier that runs a database.
App2 Requirements
An application named App2 will be deployed to the public cloud. Users will be authenticated by using the onpremises Active Directory. The users must be able to access App2 without being prompted for authentication
again.

###EndCaseStudy###

DRAG DROP
You need to configure the storage fabric to support the deployment of the virtual machines. The solution must
meet the cloud requirements.
Which three actions should you perform in sequence? (To answer, move the appropriate three actions from the
list of actions to the answer area and arrange them in the correct order.)
Select and Place:

Answer:

Explanation:
Note:
We configure the iSCSI initiator in VMM to connect to the SAN.
Then we run the Add Storage Devices Wizard to add the SAN as a storage device.
Then we can assign the storage to host groups (not directly to the hosts).
* From scenario:
/ Stores all virtual machines on the SAN only.
/ Uses SAN copy to provision the virtual machines.
* The following list describes the workflow used to discover, classify, and assign storage using VMM:
/ After configuring storage and assigning to host groups, you can assign the storage to Hyper-V hosts and
clusters as shared (Cluster Shared Volume) or available storage. Note that all nodes in the cluster should have
access to the storage array using host bus adapters (HBA) or iSCSI. If you allocated a storage pool to a host
group, you can create and optionally assign logical units directly from the Properties dialog box of a host or host
cluster. If the storage array supports iSCSI host connectivity, you can create iSCSI sessions to the storage
array from the Properties dialog box of a host.
/ In addition to discovery and management of iSCSI arrays with static targets, System Center 2012 SP1 adds
support for the discovery and management of iSCSI target arrays that support dynamic and manual targets (for
example Starwind, HP P2000, HP Lefthand, Dell EqualLogic, and Microsoft iSCSI Software Target).
* You can use host groups to group virtual machine hosts in meaningful ways, often based on physical site
location and resource allocation.
* Storage allocation — You can allocate available storage pools and LUNs to defined host groups that can
represent business groups, locations and so on. Resources typically need to be allocated on the host grouplevel before they can be assigned to hosts.
* You can create a private cloud from resources in host groups. When you create a private cloud, you select
which host groups will be part of the private cloud. You can then allocate all or some of the resources from the
selected host groups to the private cloud.