AD DS Domain Controller Promotion and Replication
HOTSPOT
Overview
Contoso, Ltd. is a company that has a main office in Seattle and two branch offices in Los Angeles and Montreal.
Existing Environment
AD DS Environment
The network contains an on-premises Active Directory Domain Services (AD DS) forest named contoso.com. The forest contains two domains named contoso.com and canada.contoso.com.
The forest contains the domain controllers shown in the following table.
All the domain controllers are global catalog servers.
Server Infrastructure
The network contains the servers shown in the following table.
A server named Server4 runs Windows Server and is in a workgroup. Windows Defender Firewall on Server4 uses the private profile.
Server2 hosts three virtual machines named VM1, VM2, and VM3.
VM3 is a file server that stores data in the volumes shown in the following table.
Group Policies
The contoso.com domain has the Group Policies Objects (GPOs) shown in the following table.
Existing Identities
The forest contains the users shown in the following table.
The forest contains the groups shown in the following table.
Current Problems
When an administrator signs in to the console of VM2 by using Virtual Machine Connection, and then disconnects from the session without signing out, another administrator can connect to the console session as the currently signed-in user.
Requirements
Technical Requirements
Contoso identifies the following technical requirements:
Change the replication schedule for all site links to 30 minutes.
Promote Server1 to a domain controller in canada.contoso.com.
Install and authorize Server3 as a DHCP server.
Ensure that User1 can manage the membership of all the groups in Contoso\OU3.
Ensure that you can manage Server4 from Server1 by using PowerShell remoting.
Ensure that you can run virtual machines on VM1.
Force users to provide credentials when they connect to VM2.
On VM3, enable Data Deduplication on all volumes that support the feature.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Community Insight
The question tests whether you can verify if a server is eligible for promotion based on its OS version, network connectivity, and DNS configuration relative to the target domain.
This scenario tests the prerequisites for promoting a server to a domain controller in a specific child domain and configuring site link replication schedules. It establishes that Server1 meets all technical requirements to be promoted to canada.contoso.com.
Candidates often overlook the requirement that the server must have proper forward lookup zones or DNS resolution for the target domain's domain controller locations before it can be promoted.
Community Discussion (2 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Server1 is running Windows Server 2019 Standard, which supports being a domain controller for the Canada.contoso.com domain. The prompt states that all domain controllers are global catalog servers, implying the forest functional level is high enough (likely 2016 or higher) to support modern DCs. Since Server1 is on the same network (implied by the ability to connect and manage), it can resolve the DNS records for canada.contoso.com. Therefore, the statement 'Yes' is correct.Why Other Candidate Answers Are Wrong
Selecting 'No' would imply Server1 lacks the necessary permissions, OS version, or connectivity to join the domain. Since no such restrictions are listed (e.g., it is not a member of a restricted workgroup preventing AD integration, nor is it running an unsupported OS), there is no valid reason to reject the promotion.Community Comment Notes
One user suggested the answer should be 'Yes', aligning with the technical feasibility. Another user commented that GPO settings only apply to the default domain policy, which is irrelevant to the DC promotion question but shows confusion about GPO scope versus infrastructure capabilities.Official Reference
Exam Strategy
When evaluating DC promotion scenarios, always check the OS compatibility first, then verify network connectivity and DNS resolution for the target domain. Ignore unrelated requirements like DHCP or File Shares unless they directly impact the DC's ability to communicate with existing DCs.
Frequently Asked Questions
What are the minimum requirements to promote a server to a domain controller?
The server must run a supported version of Windows Server, have TCP/IP configured, and be able to resolve DNS records for the domain.
Can I promote a server to a child domain without it being a Global Catalog?
Yes, but it is recommended to make it a Global Catalog for better login performance and authentication across domains in the forest.
Related Analysis
Practice All AZ-802 Questions
Access 125 questions with complete answers and detailed explanations.
View Full AZ-802 Practice Test →