QuestionQ49

VerifiedImplement and manage storage

You have an Azure subscription that contains a storage account named account1.

You plan to upload the disk files of a virtual machine to account1 from your on-premises network. The on-premises network uses a public IP address space of 131.107.1.0/24.

You plan to use the disk files to provision an Azure virtual machine named VM1. VM1 will be attached to a virtual network named VNet1. VNet1 uses an IP address space of 192.168.0.0/24.

You need to configure account1 to meet the following requirements:

  • Ensure that you can upload the disk files to account1.
  • Ensure that you can attach the disks to VM1.
  • Prevent all other access to account1.

Which two actions should you perform? Each correct answer presents part of the solution.

NOTE: Each correct selection is worth one point.

Choose two
Explanation

Microsoft Learn states that Azure Storage firewall rules apply to data-plane operations and are enforced on all network protocols, including REST and SMB, but that network rules don't affect virtual machine (VM) disk traffic, including mount and unmount operations and disk I/O. Restricting account1's networking to Selected networks and adding the on-premises range 131.107.1.0/24 as an allowed IP rule permits the disk-file upload from on-premises while blocking all other access; VM1 can still attach the resulting disk without any additional virtual network rule or service endpoint, since that traffic isn't gated by the storage firewall at all. Option B isn't needed because Microsoft.Compute is not on the trusted Azure services list. Options D and E only admit traffic from VNet1, and the on-premises upload doesn't use VNet1. Note that unmanaged disks were fully retired on March 31, 2026; today, uploaded VHD files are used to create managed disks, which are then attached to VM1.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!