You need to implement a solution that meets the resiliency requirements of the customers.
What is the best approach to achieve the goal?
(More than one answer choice may achieve the goal. Select the BEST answer.)

Case Study Title (Case Study):
Case Study 6 – Fabrikam, Inc
Overview
Fabrikam, Inc. is an IT services and hosting provider. Fabrikam has two main data centers. The data centers are located in New York and Montreal. The data
centers connect to each other by using high-bandwidth, low latency WAN links. Each data center connects directly to the Internet.
Existing Environment
The network contains an Active Directory forest named fabrikam.com that is dedicated to hosting services. All of the servers in the forest run Windows Server
2012 R2. The network contains a System Center 2012 R2 infrastructure that includes the following components:
– Windows Azure Pack for Windows Server
– Virtual Machine Manager (VMM)
– Service Provider Foundation
– Operations Manager
– OrchestratorFabrikam has implemented Hyper-V Network Virtualization in the hosting environment. All storage is either SAN-based or direct-attached storage (DAS).
All VMM library servers use DAS storage. None of the VMM library servers are managed as VMM Hyper-V hosts.
Each Hyper-V host has four 10-GbE network adapters.
Requirements
Business Goals
Fabrikam plans to provide hosting services to two customers named Customer1 and Customer2. Customer1 is based in New York and Customer2 is based in
Montreal. IT services will include assistance managing the services in the following table.

The internal network of Customer1 contains a System Center 2012 R2 infrastructure that includes the following components:
– Operations Manager
– App Controller
– VMM
Customer1 plans to deploy multi-tier VMM services that run Internet Information Services (IIS), .NET applications, and Microsoft SQL Server. Customer1 plans to
deploy non- clustered virtual machines only.
Planned Changes
Fabrikam plans to implement the following changes to the network:
Deploy a Remote Desktop Gateway (RD Gateway) virtual machine. Replace the SAN by using iSCSI targets on servers that run Windows Server 2012 R2.
General Requirements
Fabrikam identifies the following requirements for the planned deployment:
– Hyper-V hosts must remain available if a single network adapter fails. You must be able to control the amount of
bandwidth allocated to iSCSI traffic and Failover Clustering redirected traffic.
– Virtual machines that run in the Fabrikam data centers must remain available if a single data center fails. The
recovery point objective (RPO) must be 30 seconds.
– The IT staff at Fabrikam must be able to mount iSCSI target logical units on Hyper-V hosts directly from the Virtual
Machine Manager console.
– Hyper-V management and storage traffic must be separated from the network traffic generated by virtual machine guests.
– Virtual machines must be deployed by using a SAN copy.
– If a site fails, a failover must be invoked manually.Customer1 Requirements
Fabrikam identifies the following requirements for Customer1:
– Customer1 will use Hyper-V Network Virtualization in its hosted environment.
– Customer1 will require the ability to manage all of its cloud services from a single interface.
– Each deployment of a virtual machine for Customer1 must trigger the execution of a runbook by using the Orchestrator
web service. The runbook must execute before any user account logs on to the virtual machine.
Customer2 Requirements
Fabrikam identifies the following requirements for Customer2:
– Customer2 must be able to connect to the console of the hosted virtual machines.
– All of the metadata for any of the virtual machines of Customer1 must not be stored in Windows Azure.

A.
Hyper-V Recovery Manager

B.
Multi-site Failover Clustering with synchronous, block-level storage replication

C.
Multi-site Failover Clustering with asynchronous, block-level storage replication

D.
Hyper-V Replica and Orchestrator runbooks

Explanation:
/ All of the metadata for any of the virtual machines of Customer1 must not be stored in Windows Azure. So we can’t use Hyper-V Recovery Manager.