Exam AZ-104 topic 5 question 147 discussion

Subnet size: /26 The recommended subnet size for Azure Bastion is /26 "Subnet size must be /26 or larger (/25, /24 etc.)." "For host scaling, a /26 or larger subnet is recommended. Using a smaller subnet space limits the number of scale units" "For Azure Bastion resources deployed on or after November 2, 2021, the minimum AzureBastionSubnet size is /26 or larger (/25, /24, etc.)" Public IP: Standard SKU with a static allocation Only Azure Bastion Standard SKU supports 'Host scaling' and 'Upload or download files'. Besides that, Public IP address recomended by Microsoft must be Standard and Static References: https://learn.microsoft.com/en-us/azure/bastion/configuration-settings https://learn.microsoft.com/en-us/azure/bastion/bastion-faq

Answer is correct. /26 https://learn.microsoft.com/en-us/azure/bastion/configuration-settings Standard SKU with a static allocation https://learn.microsoft.com/en-us/azure/bastion/configure-host-scaling

Answer is correct how many bastion hosts available if subnet size is /26 When you create an AzureBastionSubnet with a size of /26, you have a total of 64 IP addresses. However, Azure reserves the first four and the last IP address in each subnet for internal use, leaving you with 59 usable IP addresses. Each Bastion host instance within the subnet will require a single IP address. Therefore, with a /26 subnet, you can host up to 59 Bastion hosts.

/26 and Standard SKU. The answer is always the better SKU almost 100% of the time it seems.

CORRECT

I found this!! Subnet is /26 Reference: https://learn.microsoft.com/en-us/azure/bastion/configuration-settings Azure Bastion subnet When you deploy Azure Bastion using any SKU except the Developer SKU, Bastion requires a dedicated subnet named AzureBastionSubnet. You must create this subnet in the same virtual network that you want to deploy Azure Bastion to. The subnet must have the following configuration: Subnet name must be AzureBastionSubnet. Subnet size must be /26 or larger (/25, /24 etc.). For host scaling, a /26 or larger subnet is recommended. Using a smaller subnet space limits the number of scale units. For more information, see the Host scaling section of this article. The subnet must be in the same virtual network and resource group as the bastion host. The subnet can't contain other resources.

The subnet is used for Bastion host scale units (instances) and not by the number of SSH or RDP connections, thus a /64 is recommended and should be enough for a Standard SKU.

Given answer is right

For Azure Bastion resources deployed on or after November 2, 2021, the minimum AzureBastionSubnet size is /26 or larger (/25, /24, etc.) https://learn.microsoft.com/en-us/azure/bastion/configuration-settings#subnet:~:text=How%2Dto-,Azure%20Bastion%20subnet,-Important to meet the goal of host scaling it is safe to choose /24 Public IP: Standard SKU with a static allocation

1- you need subnet size /25 = 128IPs that can host upto 126 vms since /25 is not in the answer box then then best answer here is /24=256 which can host upto 254 vms. 2- sku should be standard with static allocation

Subnet size: /24. The problem with /26 is that it provides only 64 IPs (minus the 5? that Azure reserves). There are 50 VMs on each VNET that must be supported. If we assume that means with simultaneous connections, 100 IPs are required and /26 is too small.