Q: 4
A technician is adding some Windows 10 workstations to the corporate domain. A script was able to
add the majority of the workstations, but failed on a couple. Which of the following menus should
the technician check in order to complete the task manually?
Options
Discussion
B. Official study guide and labs cover this-worth reviewing if you're rusty on domain joins.
B . User Accounts might look right but that's a common trap, domain join is only in System Properties.
B . User Accounts looks tempting but you can't actually join a domain from there, only System Properties has that option.
B tbh. System Properties is where you join a Windows machine to a domain manually. Makes sense for this scenario.
System Properties is where you actually join a machine to the domain, so B. The others don't let you change domain membership. Pretty sure this is right but let me know if I missed something obvious.
Nah, D is a trap here. System Properties is what you'd use to manually join the domain, so B.
B , since System Properties is where you actually join a PC to a domain manually. Network and Sharing helps if there's connectivity trouble, but this sounds like it's just about finishing the add process. Could be wrong if network was the issue, though.
Wouldn't D (Network and Sharing) be the place to check if the script failed due to some network config? On a few practice tests, I saw similar scenarios where fixing adapter or sharing settings was key. Or is that too much troubleshooting for this step?
D since Network and Sharing can be key if the script failed because of connectivity or sharing settings. I've seen similar questions in practice sets highlight this menu. Not 100% sure though, maybe B?
For joining a domain manually after a script fails, it's B. System Properties has the option to join or change domains directly. Network settings (D) matter only if you can't reach the domain at all, but for actually adding it, System Properties is the spot. Pretty sure on this one, anyone disagree?
Be respectful. No spam.
