Microsoft AZ-800 Dumps Questions Answers

The DNS chapters in Administering Windows Server Hybrid Core Infrastructure describe conditional forwarders as a way to direct queries for specific namespaces to authoritative DNS servers. The text notes: “A conditional forwarder forwards queries for a designated DNS domain to specified DNS servers,” which is used to “integrate split or private namespaces across sites or forests.” In this design, Server1 hosts contoso.local and delegates east and west to Server2 and Server3. By configuring Server2 and Server3 with a conditional forwarder for contoso.local pointing to Server1 , any query for contoso.local (including child names like east.contoso.local or west.contoso.local when not answered locally) is sent to Server1. Server1, being authoritative for the parent, uses the existing delegations to return referrals/answers from the proper child zones. For Internet hosts , all three server s already use root hints , which the course material confirms remains valid alongside conditional forwarding. The documentation also stresses that “authoritative data is answered locally first; forwarding applies only to names the server is not authoritativ e for,” so Server2 continues to answer east locally while leveraging Server1 to reach parent and sibling zones . This configuration ensures that all servers can resolve all internal namespaces and Internet hosts .

The remoting prerequisites in the AZ-800 curriculum state that WinRM/PowerShell remoting to a target computer is permitted for local Administrators and Remote Management Users on the target. The documentation notes: “Users who are members of the local Administrators group or Remote Management Users group on the destination can establish PowerShell remoting sessions.” In a domain, high-privilege domain administrative groups are, by default, granted local administrator rights on domain-joined servers. Applying this: User3 is in Server2\Administrators (local admin) → allowed. User4 is in Server2\Remote Management Users → allowed. User1 belongs to the domain Administrators group, which confers administrator privileges on domain-joined servers, enabling remoting to Server2. User2, however, is only in the domain “Remote Management Users” group, not the local group on Server2; domain membership alone does not grant the required local right. Therefore, the users who can open a PowerShell remoting session from Server1 to Server2 are User1, User3, and User4.

The DNS planning section of Administering Windows Server Hybrid Core Infrastructure states: “Private internal namespaces are not resolvable via Internet root hints. For resolution across internal DNS zones hosted on different servers, use zone delegation, stub zones, or conditional forwarders so that each server can reach the authoritative source.” In the scenario, Server1 hosts contoso.local , which already con tains delegations to east.contoso.local and west.contoso.local . However, Server2 (east) and Server3 (west) have no knowledge of the parent zone (contoso.local) and, because all servers use only root hints, queries for contoso.local from Server2/Server3 can not be resolved by recursion on the public roots. The proposed fix adds a conditional forwarder on Server2 for west.contoso.local and on Server3 for east.contoso.local , which enables cross-child resolution, but does not provide a path to resolve contoso.lo cal from Server2 or Server3. The guidelines further note: “To ensure all servers can resolve all internal namespaces, configure forwarders (or stub zones/secondaries) to the authoritative servers for each internal zone, including the parent zone.” Because the solution omits a forwarder (or stub/secondary) on Server2 and Server3 for contoso.local , it does not meet the goal.