Your network contains an Active Directory domain named contoso.com. The domain contains four servers on a test network.
The servers are configured as shown in the following table.
Server1 uses the storage shown in the following table.
You perform the following tasks:
– On Server2, you create an advanced SMB share named Share2A and an applications SMB share named Share2B.
– On Server3, you create an advanced SMB share named Share3.
– On Server4, you create an applications SMB share named Share4.
You add Server3 and Server4 to a new failover cluster named Clus1. On Clus1, you configure the File Server for general use role, you create a quick SMB share
named Share5A, and then you create an applications SMB share named Share5B.
You plan to create a failover cluster of two virtual machines hosted on Server1. The clustered virtual machines will use shared .vhdx files. You need to
recommend a location to store the shared .vhdx files.
Where should you recommend placing the virtual hard disk (VHD)?
A.
\\\\Clus1\\Share5A
B.
\\\\Server2\\Share2A
C.
\\\\Server4\\Share4
D.
the D drive on Server1
Explanation:
vhdx files can be housed on a continuously-available SMB share on a Windows Storage Server 2012 R2 failover cluster.
This is correct. Previous versions states that the \\Clus1\Share5A were correct but that is wrong due to the fact that it is a quick SMB share/File Server for General use and you cannot host shared .vhdx files on that type of share.
Application share on SoFS is the way to go. \\server4\share4
SMB Share – Applications: This profile creates an SMB file share with settings appropriate for Hyper-V, certain databases, and other server applications.
The Application SMB Share is perfect for this Guest Failover Clustering