Question
You have an Azure subscription. The subscription contains a virtual network named VNet1. VNet1 contains two virtual machines named VM1 and VM2 that run Windows Server.
You need to ensure that when you sign in to the Azure portal from VM2, you can manage the operating system of VM1. The solution must minimize costs.
Which two settings should you configure for VM1? To answer, select the appropriate settings in the answer area.
NOTE: Each correct answer is worth one point.
Explanation
First setting to configure for VM1: Access control (IAM). Access to Windows Admin Center in the Azure portal is controlled by Azure RBAC. To connect, your account needs the Reader and Windows Admin Center Administrator Login roles on VM1, and installing the extension needs Owner or Contributor. You assign these roles on VM1's Access control (IAM) blade. Owner or Contributor on its own does not let you sign in to the VM through Windows Admin Center.
Second setting to configure for VM1: Windows Admin Center. To manage the operating system from the portal, the Windows Admin Center extension must be installed in VM1. You do this from VM1's Windows Admin Center blade by selecting Install, and afterwards you use Connect on the same blade. Because you sign in to the portal from VM2, which is in the same virtual network, you connect over VM1's private IP address. That needs no inbound port rule, so Network settings does not have to change. Windows Admin Center in the Azure portal costs nothing. Bastion is billed by the hour and does not work with Windows Admin Center in the portal, so it does not meet the minimize-costs requirement.
