AZ-700 · Question #238
You have an Azure Private Link service named PL1 that uses an Azure load balancer named LB1. You need to ensure that PL1 can support a higher volume of outbound traffic. What should you do?
The correct answer is B. Increase the number of NAT IP addresses assigned to PL1. Azure Private Link service uses Source NAT (SNAT) to translate the source IP of consumer traffic before it reaches the provider's backend. Each NAT IP address supports a finite number of concurrent SNAT connections (approximately 64,000 per IP). To scale outbound throughput and…
Question
You have an Azure Private Link service named PL1 that uses an Azure load balancer named LB1. You need to ensure that PL1 can support a higher volume of outbound traffic. What should you do?
Options
- AIncrease the number of frontend IP configurations for LB1.
- BIncrease the number of NAT IP addresses assigned to PL1.
- CDeploy an Azure Application Gateway v2 instance to the source NAT subnet.
- DRedeploy LB1 with a different SKU.
How the community answered
(51 responses)- A2% (1)
- B82% (42)
- C10% (5)
- D6% (3)
Explanation
Azure Private Link service uses Source NAT (SNAT) to translate the source IP of consumer traffic before it reaches the provider's backend. Each NAT IP address supports a finite number of concurrent SNAT connections (approximately 64,000 per IP). To scale outbound throughput and connection capacity, you assign additional NAT IP addresses to the Private Link service. Adding frontend IPs to the load balancer or changing its SKU does not affect Private Link SNAT capacity. An Application Gateway is unrelated to Private Link NAT scaling.
Community Discussion
No community discussion yet for this question.