Hello ITPro, ran into a practice question that goes as follows. I've researched a ton and can't seem to pick out an answer that seems to cover it. What do you guys think?
You have two servers that run Windows Server 2016. The servers are configured as shown in the following table:
Server Name | Workgroup | DNS Suffix
Server1 | Workgroup1 | None
Server2 | Workgroup2 | wrkgrp.local
You need to create a failover cluster that contains both servers.
Which command should you run?
A. wmic ComputerSystem Set Workgroup="Workgroup2" | ----I tested this in the lab and it didn't seem to make any impact on the DNS suffix configuration.
B. New-Cluster -Name Cluster1 -Node Server1,Server2 -AdministrativeAccessPoint DNS | ----This should be the correct command to build the cluster once each node has a DNS suffix configured. Not a complete solution.
C. New-Cluster -Name Cluster1 -Node Server1,Server2 -AdministrativeAccessPoint ActiveDirectoryAndDNS | ----This is the incorrect command for a Workgroup cluster.
D. New-Cluster -Name Cluster1 -Node Server1,Server2 -AdministrativeAccessPoint None | ----I'm not sure when you would use this command, but it doesn't seem to apply to creating Workgroup clusters.
E. netdom computername Server1 /MakePrimary:server1.wrkgrp.local | -------This seemed like a promising way to set the DNS suffix for Server1, but it just errors out in my lab.
Reference material used:
It seems that the only DNS requirement for Workgroup clusters is that each server has a DNS suffix. From what I can tell they don't even have to be the same DNS suffix. Just as long as they can each resolve each others FQDN.
So it would seem that the first step given the question would be to set a DNS suffix for Server1, but based on the options provided, I am thinking this is a bad question.
Any other input or thoughts would be welcome!