To create a scheduled runbook to increase the processor performance of VM1 at the end of each month, you need to modify the VM size property of VM1. This will allow you to scale up the VM to a larger size that has more CPU cores and memory. You can use Azure Automation to create a PowerShell runbook that changes the VM size using the Set-AzVM cmdlet. You can then schedule the runbook to run at the end of each month using the Azure portal or Azure PowerShell. For more information, see How to resize a virtual machine in Azure using Azure Automation1.

When Azure schedules maintenance for a virtual machine, you can proactively move it to a new physical host by performing a self-service redeploy.
The Redeploy feature in the Azure portal allows you to:
* Move the VM to a new host node.
* Keep the same network interface, disks, and configuration.
* Resolve underlying host-level or platform issues proactively.
This action satisfies the requirement to move VM1 to a different host immediately and minimizes downtime.
This is explicitly documented in the Microsoft Learn - Redeploy Windows virtual machine to new Azure node guide.
# Final Verified Answer: A. Yes

D: Seamless SSO works with any method of cloud authentication - Password Hash Synchronization or Pass- through Authentication, and can be enabled via Azure AD Connect.
B: You can gradually roll out Seamless SSO to your users. You start by adding the following Azure AD URL to all or selected users' Intranet zone settings by using Group Policy in Active Directory: https://autologon.
microsoftazuread-sso.com

Explanation:
# ACR Tasks: ContReg1 and ContReg2 only
# Private endpoints: ContReg1 only
Azure Container Registry (ACR) provides multiple service tiers (SKUs)-Basic, Standard, and Premium- each offering different capabilities for scalability, performance, and features. These tiers determine what functionalities are available, including ACR Tasks and Private Link (Private Endpoints) integration.
Here's how each tier differs according to Microsoft Azure Administrator documentation (AZ-104 Exam Study Guide and Azure Docs):
Feature
Basic
Standard
Premium
ACR Tasks (Build automation, image building, and updating)
# Supported
# Supported
# Supported
Private Link / Private Endpoints (Private access via Azure backbone)
# Not Supported
# Not Supported
# Supported
Geo-replication
# Not Supported
# Not Supported
# Supported
Content trust and RBAC integration
# Supported
# Supported
# Supported
Analysis:
ACR Tasks:
ACR Tasks allow you to automate image builds and updates when base images or application code changes.
Supported in Standard and Premium tiers (as per Microsoft Docs: "ACR Tasks are available in Standard and Premium service tiers.").
Therefore, ContReg1 (Premium) and ContReg2 (Standard) support ACR Tasks.
ContReg3 (Basic) does not support advanced tasks automation at scale.
# Answer: ContReg1 and ContReg2 only
Private Endpoints:
Private Link (Private Endpoints) enables private network connectivity to the ACR from a virtual network.
According to Azure documentation:
"Private Link for Azure Container Registry is supported only in the Premium service tier." This ensures that access to the registry occurs via Azure's backbone, preventing exposure to the public internet.
# Answer: ContReg1 only (Premium)
Verified Microsoft Documentation Extract:
From Microsoft Learn: Azure Container Registry service tiers overview:
"The Premium tier provides advanced capabilities such as geo-replication, content trust, customer-managed keys, and Private Link support."
"ACR Tasks is available in both Standard and Premium tiers for continuous integration workflows and automated image building."

When you move an Azure virtual machine to another resource group, Azure Resource Manager treats the virtual machine as a resource that has required dependencies. For an IaaS VM, the VM resource depends on its network interface (NIC) for connectivity and its managed disks (OS disk and any data disks) for storage.
Microsoft Azure Administrator guidance for resource moves explains that a move operation must include any dependent resources that are required for the resource to function after the move. If you attempt to move only the VM object while leaving required dependencies behind, the move would be blocked or the VM would be left in a nonfunctional state.
In this scenario, NIC1 is the network interface used by VM1, and Disk1 is the OS disk used by VM1; both are core dependencies and are moved along with the VM. VNet1 is a separate networking resource that typically hosts multiple subnets and can be shared by many resources; it is not required to move to move a VM, and moving the VNet would be unnecessary and potentially disruptive. Therefore, after moving VM1 from RG1 to RG2, the resources present in RG2 are VM1, NIC1, and Disk1, but not VNet1.