You can only attach virtual machines that are in the same location and on the same virtual network as the LB.
Virtual machines must have a standard SKU public IP or no public IP.
The LB needs to be a standard SKU to accept individual VMs outside an availability set or vmss. VMs do not need to have public IPs but if they do have them they have to be standard SKU. Vms can only be from a single network. When they don't have a public IP they are assigned an ephemeral IP.
Also, when adding them to a backend pool, it doesn't matter in which status are the VMs.
Note: Load balancer and the public IP address SKU must match when you use them with public IP addresses.

A Recovery Services vault is a logical container that stores the backup data for each protected resource, such as Azure VMs. When the backup job for a protected resource runs, it creates a recovery point inside the Recovery Services vault.
Scenario:
There are three application tiers, each with five virtual machines.
Move all the virtual machines for App1 to Azure.
Ensure that all the virtual machines for App1 are protected by backups.
References: https://docs.microsoft.com/en-us/azure/backup/quick-backup-vm-portal
Topic 2, A Datum Corporation
Overview
A Datum Corporation is a consulting firm that has a main office in Montreal and branch offices in Seattle and New York.
Azure Environment
A Datum has an Azure subscription that contains three resource groups named RG1. RG2, and RG3. The subscription contains the storage accounts shown in the following table.

The subscription .contains the virtual machines shown in the following table.

The subscription has an Azure container registry that contains the images shown in the following table.

The subscription contains the resources shown in the following table.

The subscription contains an Azure key vault named Vaultl.
Vault! contains the certificates shown in the following table.


Vaultl contains the keys shown in the following table.
Microsoft Entra Environment
A Datum has a Microsoft Entra tenant named adatum.com that is linked to the Azure subscription and contains the users shown in the following table.
The lenant contains the groups shown in the following table.

The adatum.com tenant has a custom security attribute named Attribute1.
Planned Changes
A Datum plans to implement the following changes:
* Configure a data collection rule {DCR) named DCR1 to collect only system events that have an event ID of
4648 from VM2 and VM4.
* In storage1, create a new container named cont2 that has the following access policies:
o Three stored access policies named Stored 1, Stored2, and Stored3 o A legal hold for immutable blob storage
* Whenever possible, use directories to organize storage account content.
* Grant User1 the permissions required to link Zone1 to VNet1.
* Assign Attribute1 to supported adatum.com resources.
* In storage2, create an encryption scope named Scope"1.
* Deploy new containers by using Image1 or Image2.
Technical Requirements
A Datum must meet the following technical requirements:
* UseTLSforWebApp1.
* Follow the principle of least privilege.
* Grant permissions at the required scope only.
* Ensure that Scope1 is used to encrypt storage services.
* Use Azure Backup to back up cont1 and share1 as frequently as possible.
* Whenever possible, use Azure Disk Encryption and a key encryption key (KEK) to encrypt the virtual machines.

Explanation:
WebApp1 can communicate with VM2. No, this is not correct. According to the tables, WebApp1 is integrated with VNet1, which has a peering connection with VNet2. However, VM2 is in VNet3, which is not peered with VNet1 or VNet2. Therefore, WebApp1 cannot communicate with VM2 across different virtual networks1.
NSG1 controls inbound traffic to WebApp1. No, this is not correct. According to the tables, NSG1 is associated with Subnet1 in VNet1, which is integrated with WebApp1. However, network security groups only control outbound traffic from App Service apps to virtual networks, not inbound traffic to App Service apps from virtual networks2. Therefore, NSG1 does not control inbound traffic to WebApp1.
WebApp2 can communicate with VM1. Yes, this is correct. According to the tables, WebApp2 is integrated with VNet3, which has a peering connection with VNet2. VM1 is in Subnet2 in VNet2, which has a network security group named NSG2 that allows inbound traffic from any source on port 803. Therefore, WebApp2 can communicate with VM1 on port 80 across peered virtual networks.

Explanation:
Box 1 = max value
Box 2 = 20
Explanation:
Use max for platformFaultDomainCount
2 or 3 is max value, depending on which region you are in.
Use 20 for platformUpdateDomainCount
Increasing the update domain (platformUpdateDomainCount) helps with capacity and availability planning when the platform reboots nodes. A higher number for the pool (20 is max) means that fewer of their nodes in any given availability set would be rebooted at once.
References:
https://www.itprotoday.com/microsoft-azure/check-if-azure-region-supports-2-or-3-fault-domains-managed- disks
https://github.com/Azure/acs-engine/issues/1030

Option A (Create an Azure Resource Manager template): This wouldn't circumvent the policy enforcement.
Even with a template, you cannot create resources that the policy explicitly denies.
Option B (Add a subnet to VNET1): Adding a subnet does not address the policy restriction on creating virtual machines. Also, the existing VNET1 can already have multiple subnets.
Option C (Remove Microsoft.Network/virtualNetworks from the policy): This isn't necessary because you're not trying to create a new virtual network; you are connecting to an existing one, VNET1.
Option D (Remove Microsoft.Compute/virtualMachines from the policy): This is the correct action because it directly addresses the restriction that is preventing you from creating a new virtual machine in RG1.
Removing the virtual machine resource type from the not allowed list in the policy will enable you to create VM2.
Remember, changes to policies might take a few minutes to propagate. After updating the policy, you should be able to create the new virtual machine VM2 and connect it to VNET1.