HOTSPOT
Your network contains an Active Directory domain named contoso.com.
You have a failover cluster named Cluster1 that contains two nodes named Server1 and
Server2. Both servers run Windows Server 2012 R2 and have the Hyper-V server role
installed.
You plan to create two virtual machines that will run an application named App1. App1 will
store data on a virtual hard drive named App1data.vhdx. App1data.vhdx will be shared by
both virtual machines.
The network contains the following shared folders:
An SMB file share named Share1 that is hosted on a Scale-Out File Server.
An SMB file share named Share2 that is hosted on a standalone file server.
An NFS share named Share3 that is hosted on a standalone file server.
You need to ensure that both virtual machines can use App1data.vhdx simultaneously.
What should you do?
To answer, select the appropriate configurations in the answer area.
Answer: 
Explanation:
why dynamically expanding and not differencing?
Windows Server 2012 R2 Storage: Step-by-step with Storage Spaces, SMB Scale-Out and Shared VHDX (Virtual) – http://blogs.technet.com/b/josebda/archive/2013/07/31/windows-server-2012-r2-storage-step-by-step-with-storage-spaces-smb-scale-out-and-shared-vhdx-virtual.aspx
Create your VHDX data files to be shared as fixed-size or dynamically expanding, on the disk where you manually attached the Shared VHDX filter. Old VHD files are not allowed. Differencing disks are not allowed.
A differencing disk is a special type of dynamically expanding VHD file that is associated with a “parent” VHD. In this parent/child storage topology, the parent disk remains unchanged and any write operations made to the “child” differencing disk only. You may use differencing disks in scenarios where you need to maintain a particular baseline configuration and would like to easily test and then rollback changes to the baseline.
App1data.vhdx is containing data has to be used simultaneously by both servers, which will be not given when using differencing disks – each server would create it’s own “child” partition to use. Of course you can merge your child partitions into the parent, but I think it is a common way to meet the requirement.
With that said, the SoFS is a no brainer for HA, and dynamically expanding allows the usege of shared VHDX (which is not supported when using differencing disks).
OOps. Typo:
App1data.vhdx is containing data that has to be used simultaneously by both servers, which will be not given when using differencing disks – each server would create it’s own “child” partition to use. Of course you can merge your child partitions into the parent, but I don’t think it is a common way to meet the requirement.
I think share 1 and dynamically expanding.
Both VM’s need to access the VHDX at the same time so Scale out file server seems obvious to me. Also, Shared VHDX files do not support differencing disks.
Check below, are some totally unrelated internet websites to ours, having said that, they are most trustworthy sources that we use.