DRAG DROP
You have two failover clusters named Cluster1 and Cluster2. All of the nodes in both of the clusters
run Windows Server 2012 R2.
Cluster1 hosts two virtual machines named VM1 and VM2.
You plan to configure VM1 and VM2 as nodes in a new failover cluster named Cluster3.
You need to configure the witness disk for Cluster3 to be hosted on Cluster2.
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.
Answer: 
Explanation:
Note:
* Use the Create Clustered File Server Wizard
When you create a Scale-Out File Server Cluster from existing servers, the Create Clustered File
Server
Wizard does the following:
1. Enables the file server role on the computers (box 1)
2. Enables the Scale-Out File Server role on the cluster (box 2)
3. Adds the provisioned computers as a Scale-Out File Server cluster under VMM management
* VMM provides support for the Microsoft iSCSI Software Target by using an SMI-S provider.
Microsoft iSCSI is now fully integrated into Windows Server 2012.
* Scale-Out File Server– As of System Center 2012 R2, VMM can create a Scale-Out File Server and
manage its storage.How to Create a Scale-Out File Server in VMM
All the nodes run Windows Server 2012 R2, so shared virtual disks are supported. This case falls under Scenario 2 in https://technet.microsoft.com/en-us/library/dn265980.aspx
What you need to do then is:
In Cluster2, install a File Server role
In Cluster2, Specify the SOFS option
In Cluster1, Add a SCSI hard disk drive to VM1, pointing to a file share of Cluster2, create a vhdx there (either fixed size or dynamically expanding), under advanced features tick Enable virtual hard disk sharing. Then add the same vhdx to VM2, as a SCSI hdd, tick Enable virtual hard disk sharing.
In one of the VMs, bring the disk online and initialize it.
Create the guest cluster
Add available storage.
f_idiot, you say add a SCSI hdd but when I look at Scenario2 on the link you provided it states:
Scale-Out File Server:
The servers must have access to block-level storage, which you can add as shared storage to the physical cluster. This storage can be iSCSI, Fibre Channel, SAS, or clustered storage spaces that use a set of shared SAS JBOD enclosures.
Shouldn’t it be iSCSI?
This is a Hyper-V cluster, so you’ll need to use a shared Virtual Hard Disk for both machines.
We need to add the HD from the settings of VM1 and VM2 in Cluster1.
You can only add disks to the SCSI controller from there. So it’s SCSI.
How would you add an iSCSI disk to VMs anyway?
You would at least need to add the iSCSI target role to the cluster.
I have yet to encounter a question where SCSI is a valid option or an option at all before this one,due to the fact that iScsi is microsofts own technology that they are trying to push it should be an indication as to what the answer is,if it is possible to achieve with ISCSI then ISCSI it is,period.
So the sequence is:
-On Cluster2, Install File Server Role service.
-On Cluster2, Install Scale-Out File Server for application data option
-On Cluster1, ADD a SCSI hdd to VM1 and VM2
Seems so