Hotspot Question You have an Azure subscription that contains the storage accounts shown in the following table. You need to create private endpoints for the target sub-resources of the storage…

Question

Exhibits

Answer Area

• storage11
  12345
• storage21
  12345

Explanation

This question tests knowledge of Azure private endpoints and how many endpoints are required per storage account sub-resource type. Each sub-resource (blob, file, queue, table, dfs, web) requires its own dedicated private endpoint.

Approach. In Azure, a private endpoint maps to exactly one sub-resource of a storage account. If a storage account supports multiple sub-resources (e.g., blob, file, queue, table), you need one private endpoint per sub-resource you want to expose privately. For a general-purpose v2 storage account with all services enabled, you would need up to 6 private endpoints (blob, file, queue, table, dfs for Data Lake Gen2, web for static websites). For a storage account with only specific services enabled, the count matches the number of active sub-resources. The minimum number of private endpoints equals the number of target sub-resources that need private access - typically: StorageV2 with blob+file+queue+table = 4, a Blob-only account = 1, a Data Lake Storage Gen2 account with blob+dfs = 2, etc. Without the actual table data showing specific accounts, the key rule is: one private endpoint per sub-resource per storage account.

Concept tested. Azure Private Endpoints for Storage Accounts - specifically that each storage sub-resource (blob, file, queue, table, dfs, web) requires its own individual private endpoint, so the minimum number of private endpoints equals the number of sub-resources that must be privately accessible on each storage account.

Reference. https://learn.microsoft.com/en-us/azure/storage/common/storage-private-endpoints

No community discussion yet for this question.