Explanation:
For User1, \\server2\share maps to drive H.: No
For User2, \\server1\share maps to drive H.: Yes
For User3, \\server3\share maps to drive H.: No
The Administering Windows Server Hybrid Core Infrastructure materials explain that Group Policy is processed in the order Local # Site # Domain # OU, with the last applied policy normally taking precedence.
Two modifiers change this behavior: Enforced (No override) on a GPO link and Block inheritance on a container/OU. The guide states that an Enforced link "prevents child containers from overriding settings in that GPO," while Block inheritance "prevents higher-level GPOs from applying except those marked Enforced." Applying these rules:
* User1 (Contoso\Users) is not in OU1, so GPO2 (drive H to \\server2\share) does not apply. Only domain-level GPOs apply to the Users container; thus, the statement for \\server2\share is No.
* User2 (OU1) receives GPO1 (Domain, Enforced) and GPO2 (OU1). Because GPO1 is Enforced, its mapping (H # \\server1\share) cannot be overridden by GPO2, so the statement is Yes.
* User3 (OU1\OU2) is in OU2, which has Block inheritance. This blocks higher GPOs except those Enforced, so GPO1 still applies and GPO2 is blocked. Although GPO3 (OU2) also applies, the Enforced domain GPO (GPO1) takes precedence over conflicting lower-level settings, so H: remains
\\server1\share, making the statement about \\server3\share No.

Explanation:
Within the Administering Windows Server Hybrid Core Infrastructure content for AD DS deployment, Microsoft specifies that Install From Media (IFM) for promoting a domain controller-especially a Read- Only Domain Controller (RODC)-must be created from a writable domain controller in the same target domain. The guide explains that IFM "pre-stages the AD DS database so that the promotion consumes far less replication traffic," and it emphasizes: "RODC IFM cannot be generated from an RODC; it must be created on a writable DC of the destination domain." It also clarifies tool choice: "Use ntdsutil ifm to generate media for a writable DC or an RODC. The media is then used during promotion to avoid full initial replication across the network." Applied here: the server to be promoted (Server1) will be an RODC in child.contoso.com. The only writable DC in that domain shown is DC2 (Domain-wide FSMO holder for child.contoso.com), making it the correct and traffic-efficient source. DC1 and RODC3 are in contoso.com (parent domain), so neither meets the requirement; additionally, an RODC cannot be used as an IFM source. Regarding tooling, the documentation notes that Windows Server Backup is for system-state backup/restore and is not the supported method to generate IFM media; the prescribed tool is Ntdsutil.exe with the IFM context.
Therefore, to minimize network traffic and satisfy Azure/AD DS best practices, create the IFM media on DC2 using Ntdsutil.exe and then promote Server1 with that media.

Explanation:
Disk1: NTFS only
Disk2: NTFS or ReFS only
The Windows Server Hybrid Core Infrastructure objectives specify that disk (volume) quotas-the classic per- user/per-volume quota feature exposed in the volume's properties-are a capability of NTFS. The guidance states that "NTFS supports user and volume quotas that can be configured per volume; ReFS does not implement the legacy NTFS disk-quota mechanism." Therefore, to meet the requirement that Disk1 must support disk-level quotas, the volume must be formatted as NTFS.
For Data Deduplication, the storage module explains that Data Deduplication is a file-system feature available on modern Windows Server versions and that it is "supported on NTFS volumes and on ReFS volumes beginning with Windows Server 2019/2022 scenarios." The same materials emphasize that exFAT doesn't support Windows Server features such as quotas or dedup. Consequently, to satisfy the requirement that Disk2 must support Data Deduplication, you can format Disk2 as NTFS or ReFS; both file systems are valid for dedup workloads on current Windows Server releases, while exFAT is not.
Thus:
* Disk1 # NTFS only (to enable disk-level quotas).
* Disk2 # NTFS or ReFS only (to enable Data Deduplication).

Explanation:

The Administering Windows Server Hybrid Core Infrastructure (AZ-800) study content for Hyper-V and Discrete Device Assignment (DDA) explains that devices passed through to a guest are first dismounted from the host and then attached to the VM. To return the hardware to the host you must reverse those steps in the proper order. The guide states that when reclaiming a DDA device, the VM must be powered off before removal, and you must use Remove-VMAssignableDevice to detach the device from the VM. After removal, the device remains in a host-dismounted state until you explicitly mount it back to the host with Mount-VMHostAssignableDevice. Finally, to make the hardware usable by the host OS, re-enable the device in Device Manager. This sequence is summarized in the course materials as: stop (turn off) the VM that owns the device # remove the VM assignment (Remove-VMAssignableDevice) # return it to the host (Mount-VMHostAssignableDevice) # enable the device for host use (Device Manager). This ensures the NVMe device is properly detached from VM1, made available to Server1 again, and recognized/initialized by Windows on the host for normal operation.

Explanation:
When User1 connects to \https://www.google.com/search?q=Server1.adatum.com\Share1, the user can take ownership of File1.txt.: Yes When User2 connects to \https://www.google.com/search?q=Server1.adatum.com\Share1, File1.txt is visible.: Yes When User3 connects to \https://www.google.com/search?q=Server1.adatum.com\Share1, File1.txt is visible.: No In Windows Server Hybrid environments, access to files over a network is governed by the intersection of Share Permissions, NTFS (File) Permissions, and Access-Based Enumeration (ABE).
* Ownership Rights: User1 has Full Control in the NTFS permissions for File1.txt. In Windows security, the Full Control right inherently includes the "Take Ownership" and "Change Permissions" rights. While the Share permission for "Domain Users" is set to Change, which normally restricts permission changes over the wire, a user with NTFS Full Control can still perform ownership operations if they have sufficient effective rights. Therefore, User1 can take ownership.
* File Visibility and ABE: The exhibit for Share1 shows that FolderEnumerationMode is set to AccessBased. Access-Based Enumeration (ABE) ensures that users only see the files and folders for which they have at least Read (or equivalent) NTFS permissions.
* User2: The NTFS permissions grant User2 Read access to File1.txt. Since User2 has read access, ABE will allow the file to be visible when the user browses the share.
* User3: The NTFS permissions grant User3 Write access but not Read access. ABE specifically requires the "Read" permission for a file to be visible in a directory listing. Because User3 lacks the Read permission, File1.txt will be hidden from their view, even though they have Write rights to the underlying file.