Question
Your network contains an Active Directory Domain Services (AD DS) domain named contoso.com. The domain contains a server named Server1 that has the
DFS Namespaces role service installed. Server1 hosts a domain-based Distributed File System (DFS) Namespace named Files.
The domain contains a file server named Server2. Server2 contains a shared folder named Share1. Share1 contains a subfolder named Folder1.
In the Files namespace, you create a folder named Folder1 that has a target of \\Server2.contoso.com\Share1\Folder1.
You need to configure a logon script that will map drive letter M to Folder1. The solution must use the path of the DFS Namespace.
How should you configure the command to map the drive letter? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
Explanation
net use m: (namespace server): \\contoso.com — Files is a domain-based namespace, so its UNC path begins with the fully qualified domain name of the AD DS domain that hosts it (\\contoso.com\...), and clients resolve that name through a domain controller to a referral list of namespace servers. Using \\Server1.contoso.com would work only as a stand-alone/server-based path that hard-codes one namespace server and loses the fault tolerance and referral behavior of the domain-based namespace, and \\Server2.contoso.com would bypass DFS entirely by pointing straight at the folder target instead of the namespace; \\files.contoso.com is not a valid form because "Files" is the namespace name, not a DNS host name.
net use m: (folder path): \files\folder1 — After the domain name, a domain-based namespace path continues with the namespace root name (Files) and then the namespace folder name (Folder1), producing \\contoso.com\Files\Folder1. The namespace hides the physical target, so the share and subfolder names on the file server (Share1\Folder1) do not appear in the path — that is why \files\share1\folder1 and \share1\folder1 are incorrect — and \folder1 alone is wrong because it omits the namespace root that must follow the domain name.
