To manage Microsoft updates on an on-premises server via Azure Arc, you must leverage the Azure Update Management solution. According to official Administering Windows Server Hybrid Core Infrastructure study guides, Azure Arc-enabled servers allow you to manage your non-Azure Windows and Linux machines as if they were native Azure resources. To facilitate update management, the infrastructure relies on a connection between the machine, an Azure Automation account, and a Log Analytics workspace.
First, you must install the Azure Monitor agent (or the Legacy Log Analytics agent, though AMA is the current standard) on Server1. This agent is responsible for collecting inventory data and the status of available updates, then sending that metadata to the Log Analytics workspace. Azure Arc simplifies this deployment by allowing the agent to be installed as an extension directly from the Azure portal.
Second, you must enable Update Management from the Automation account. The Update Management solution uses the data collected by the agent to assess the update status of the server. Once enabled, you can create update deployments to schedule the installation of updates during defined maintenance windows. This integrated approach ensures that hybrid servers-those residing on-premises but managed via Azure Arc- receive the same governance and patching consistency as cloud-native virtual machines. Option A is incorrect as Sentinel is for security orchestration, and Option D is incorrect because Arc-enabled servers are not connected through the "Virtual machines" data source used for native Azure VMs.

Explanation:

The Windows Server Hybrid Core Infrastructure curriculum explains that AD DS clients and DCs are site- aware and their placement is governed by site and subnet objects. To place a new RODC in a specific datacenter and ensure it belongs to a new site, you must first create the site and associate the correct IP subnet.
The guide states that "subnet-to-site mapping determines the site membership of domain controllers and clients," ensuring Server1 is in RemoteSite1 after promotion. Next, to control replication, the guidance under
"Configure sites, subnets, and site links" specifies that inter-site replication schedules and costs are configured on site links; adjusting the site link gives you granular control over when the hub site (your existing site) replicates with RemoteSite1. Finally, to meet the principle of least privilege and allow a non-Domain Admin to install an RODC, the module "Deploy and manage RODCs" describes pre-staging (pre-creating) an RODC account and delegating installation to a designated user. It notes that "an RODC can be pre-created and an installer account assigned so that a local administrator at the branch can run the AD DS installation wizard without requiring domain-wide administrative rights." With these three steps-site/subnet, site link, and pre- created RODC with delegated installer-User1 can promote Server1 to an RODC in RemoteSite1 while you retain control of replication and adhere to least privilege.

When building Windows container images, the base image determines both compatibility and image size. The hybrid core curriculum emphasizes that Nano Server is the smallest Windows base image, intended for headless, app-only workloads such as .NET (/.NET Core) applications. .NET Core's modular, self-contained approach enables it to run on Nano Server images designed for Windows containers, yielding significantly smaller images and faster pull/start times than Server Core or Windows Server (Full) bases. Server Core includes additional components (GUI-less but still broad OS surface) and is used when you need APIs or frameworks not present in Nano. "Windows" or "Windows Server (Full)" are not container base images for modern Windows containers and would produce unnecessarily large layers. To meet the requirement "the image must be as small as possible" for a .NET Core app, the guidance is to select Nano Server as the base (for matching architecture and Windows version), then layer the .NET runtime or self-contained app on top.
This choice aligns with best practices for minimizing footprint, improving density, and reducing network transfer during CI/CD.

Explanation:

The Windows Server Data Deduplication section of the Administering Windows Server Hybrid Core Infrastructure course explains that deduplicated volumes require the deduplication components on any system that needs to read them: "Data Deduplication is implemented as a filter driver. To access a deduplicated volume on another server, you must install the Data Deduplication role service; otherwise files may appear as reparse points and cannot be opened." It also clarifies that "when the role is present, the system transparently rehydrates data on access without requiring a restore." In your scenario, Disk2 was deduplicated on Server1 and is now attached to Server2. To regain immediate access to all files as quickly as possible, install the Data Deduplication role service on Server2 so the filter can interpret the chunk store and metadata and make the files readable instantly. Creating a storage pool is irrelevant because the disk already exists and is readable; FSRM does not interpret dedup data; and restoring from Azure Backup would be slower and unnecessary since the original deduplicated volume is intact. Hence, the fastest, correct action is to install Data Deduplication on Server2.https://docs.microsoft.com/en-us/windows-server/storage/data-deduplication
/overview