Exam AZ-104 topic 5 question 118 discussion

D is the answer. https://learn.microsoft.com/en-us/azure/bastion/configuration-settings#instance When you configure Azure Bastion using the Basic SKU, two instances are created. If you use the Standard SKU, you can specify the number of instances. This is called host scaling. Each instance can support 20 concurrent RDP connections and 40 concurrent SSH connections for medium workloads. Once the concurrent sessions are exceeded, an additional scale unit (instance) is required.

Just one advice here - read, think and ONLY after post. Standard SKU for bastion support up to 50 instances. /26 it have 64 IPs, with 59 usable. That it means the IPs are ENOUGH to deploy maxim supported number of bastion instances. The relation between number of session and required IPs in the bastion subnet is not 1 to 1 - is 25 to 1. That means one IP is used for one instance that can support up to 25 concurrent sessions. For 100 sessions, you need 4 instances that will need 4 IPs. I hope I bring some clarity here.

D is correct

Azure Bastion Standard and Azure Bastion Premium start with 2 instances as part of base pricing. You need 2 instances for 100 concurrent ssh user

D is right

both A and D are true, and as always, quite many of these questions are so badly formulated or even worse they are conceived to trick you into giving a wrong answer. this is so bad

Agree with D: In the first instance, bastion should be update from basic to standard as per comments here. This is due to bastion only 2 max instances with 40 ssh connections each. With standard this can be up to 50 instances to meet the request with 40 SSH sessions each instance. https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-bastion-limits https://learn.microsoft.com/en-us/azure/bastion/configuration-settings#instance A is incorrect as it's not what you would FIRST do.

Answer: D Basic SKU: 2 instances (50 connections at most) Standart SKU: you can specify the number of instances between 2-50 (25 connections by instance at most). https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-bastion-limits

i think subnet can`t be resize? need to re-create the Bastion to others larger subnet?

/26 just support 64ip. We need 100 concurrent connections.

D. Upgrade Bastion1 to the Standard SKU. To support 100 concurrent SSH users, you need to upgrade the Basic SKU Azure Bastion to the Standard SKU. The Basic SKU only supports 10 concurrent SSH users, while the Standard SKU supports up to 100 concurrent SSH users. Resizing the subnet of Bastion1 or creating an NSG would not directly address the need to support more concurrent SSH users, and host scaling is not applicable in this scenario.

/26 just support 64ip. We need 100

is it new question?

In general when you deploy the Azure Bastion Basic SKU Microsoft deploys two instances which supports 20-24 concurrent sessions which means each instance support 10-12 sessions. https://reimling.eu/2021/07/azure-bastion-supports-scalability-for-ssh-rdp-connections-with-the-new-standard-sku/