AZ-500 Secure networking Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  1. Navigate to the Key Vault in the Azure portal. 2. Under Settings, select Networking. 3. In the Firewalls and virtual networks tab, add the desired virtual network. 4. Click Save.

  Why this is correct

  This sequence is correct because Azure Key Vault firewall configuration is performed under the Networking settings of the vault resource. After selecting the 'Firewalls and virtual networks' tab, you can add a virtual network rule (using a service endpoint or existing virtual network) to define allowed traffic sources. Saving commits the rule changes, updating the vault's access policy enforcement. This order respects the portal workflow: navigate, open settings, configure, then apply.

• ✗

  1. Navigate to the Key Vault. 2. Click Save. 3. Then go to Networking. 4. Add virtual network.

  Why it's wrong here

  This order is invalid because the Save command is not a stand-alone navigation action; it only persists changes made within an open configuration blade. Clicking Save before even opening the Networking blade means no firewall rule is created, and the click has no effect on the vault's firewall settings. Additionally, you cannot add a virtual network rule until you have accessed the Networking pane, so placing 'Go to Networking' after Save reverses the required dependency. Properly, you must open Networking, configure the rule, and then save.

• ✗

  1. Navigate to the Key Vault. 2. Select Networking. 3. Save the current firewall settings. 4. Then add virtual network.

  Why it's wrong here

  This sequence incorrectly saves existing (default) firewall settings before adding the new virtual network rule. The Save operation writes only the current state of the Firewalls and virtual networks tab, so if you save first, your subsequent rule addition remains unsaved and the vault continues to enforce the prior config. The correct procedure is to add the desired virtual network in the Networking blade and then click Save to commit that change; saving early may also briefly apply an unintended status if selected addresses are empty. Thus the rule must be added prior to the final save.

• ✗

  1. Navigate to the Key Vault. 2. Add virtual network. 3. Select Networking. 4. Save.

  Why it's wrong here

  This is incorrect because you cannot add a virtual network rule without first going to the Networking settings. The option to add a virtual network is located within the Firewalls and virtual networks tab, which is part of Networking.

Go deeper

Related to this question