Subnet1 is associated with a service endpoint policy named Policy1 that includes a single resource referencing storage1. An Azure Batch pool (Pool1) is deployed into Subnet1. To ensure the compute nodes in Pool1 can access storage1, what should you do?

Service endpoint policies allow you to filter egress traffic from a virtual network to Azure services, specifying which storage accounts are accessible. By adding storage1 to Policy1, you explicitly permit compute nodes in Pool1 (which is in Subnet1 associated with Policy1) to access storage1. Adding an alias to Policy1 is not the correct action; aliases are used to define custom service endpoint policies, not to directly grant access to a specific resource. Adding the storage service as a service endpoint on Subnet1 is a prerequisite for using service endpoint policies, but it doesn't, by itself, restrict or permit access to specific storage accounts. Delegating Subnet1 to a specific service is for scenarios like Azure Container Instances or Azure Databricks, not for controlling storage account access via service endpoint policies.