You plan to deploy a highly available SAP HANA system in a scale-out configuration with standby to Azure virtual machines. You need to implement shared storage volumes by using Azure NetApp Files…

Question

Options

• Aa service endpoint
• Ba private link
• Ca delegated subnet
• Da private endpoint

• A
  2% (1)
• B
  5% (3)
• C
  91% (53)
• D
  2% (1)

Explanation

Azure NetApp Files requires a delegated subnet as a prerequisite before any volumes can be created - you must delegate a subnet within your VNet specifically to the Microsoft.NetApp/volumes service, which grants NetApp the permissions to inject network interfaces into that subnet and provision storage volumes there.

Why the distractors are wrong:

• A (Service endpoint) connects Azure services to your VNet over the Azure backbone, but NetApp Files doesn't use service endpoints for its integration model - it uses subnet delegation.
• B (Private link) creates a private connection to a specific resource instance, which is a different connectivity pattern not used by Azure NetApp Files.
• D (Private endpoint) is similar to Private Link - it maps a service to a private IP in your VNet, but Azure NetApp Files doesn't use this mechanism; it uses delegation instead.

Memory tip: Think of subnet delegation as "granting Azure NetApp Files a reserved parking spot" in your VNet - without reserving that spot first (delegating the subnet), NetApp Files has nowhere to park its storage volumes, so nothing else can be configured.

No community discussion yet for this question.