Question 700
An operations team administers VM payroll01 by RDP and VM api01 by SSH directly over their existing public NIC IPs. Company policy now prohibits Internet-exposed management ports but requires administrators to retain browser-based management from the Azure portal through a supported Bastion deployment. Which TWO changes satisfy the requirement? Select TWO answers.
Explanation
Correct Answers
Removing direct public management exposure closes the forbidden Internet RDP/SSH path. Confirm that each public NIC address serves no unrelated approved function before removal and restrict any network security group rules that otherwise still allow those management ports from the Internet. This change is separate from providing an alternative management path; Azure Bastion allows administrators to connect through private VM addresses after the public exposure is removed.
Azure Bastion provides supported RDP and SSH connectivity to Azure VMs without requiring the VMs themselves to have public management IPs. Deploy it with the required dedicated AzureBastionSubnet and supported configuration, confirm routing and access authorization, and connect from the portal to the VMs’ private IPs. Bastion is the replacement administration path; merely removing public access without it could strand operators, so both selected changes are needed to satisfy the complete requirement.
Incorrect Answers
Changing SSH to a nonstandard public port does not remove Internet-facing remote administration. Public attackers can still reach a listening SSH service, and the organization explicitly prohibits Internet-exposed management access. The supported replacement uses a private VM path through Bastion and closes the original exposed endpoints rather than relying on port obscurity.
An Azure Policy exemption affects how a policy assignment evaluates designated resources; it does not change public IP assignments or network security group packet filtering. Exempting the VMs would neither close their existing management ports nor create an alternative secure admin path. The policy objective remains unmet.
Publishing private-address hostnames in public DNS does not make RDP or SSH private. The VM still has its public NIC endpoint and permissive network policy unless those are removed or restricted. Public DNS is a naming mechanism, not a Bastion tunnel or management-port firewall. Use the private Bastion path and explicitly eliminate unwanted public exposure.