You are preparing to deploy Azure Bastion to secure administrative access to virtual machines in a virtual network named ProductionVNet. You plan to secure the deployment using a custom Network Security Group (NSG) associated with the Bastion subnet. To prevent deployment validation failures, you must ensure the NSG is fully configured with the mandatory rules before the Azure Bastion host is provisioned. Which five actions should you perform in sequence?
- 1Create a subnet named AzureBastionSubnet in ProductionVNet with an address prefix of /26.
- 2Create a public IP address configured with the Standard SKU and Static allocation.
- 3Create a Network Security Group (NSG) and define the mandatory inbound and outbound rules for Bastion traffic.
- 4Associate the Network Security Group (NSG) with the AzureBastionSubnet.
- 5Provision the Azure Bastion host in the AzureBastionSubnet, specifying the Standard SKU public IP address.
Cevap
The correct order of actions is to first create the AzureBastionSubnet with a /26 prefix, create a Standard SKU static public IP address, create a Network Security Group (NSG) with the mandatory rules, associate that NSG with the AzureBastionSubnet, and finally provision the Azure Bastion host.
The correct sequence begins with creating the dedicated subnet named exactly AzureBastionSubnet of size /26 or larger, followed by creating the prerequisite Standard SKU public IP address. Next, the NSG must be created and populated with the mandatory Azure Bastion rules. The NSG is then associated with the AzureBastionSubnet. Finally, the Azure Bastion host is provisioned using both the subnet and the public IP, passing the platform's configuration and NSG validation rules.
Adım Adım Çözüm
Anahtar Kavram
Azure Bastion deployment requires a dedicated subnet named AzureBastionSubnet of size /26 or larger, a Standard SKU static public IP, and an NSG configured with specific mandatory inbound and outbound rules associated with the subnet to pass deployment validation.