What feature would you configure to separate internal and external traffic on an Azure Application Gateway?

What feature would you configure to separate internal and external traffic on an Azure Application Gateway?

• A. Path-based routing
• B. Multi-site listeners
• C. Health probes
• D. SSL offloading

Answer: (A)

The correct feature to configure for separating internal and external traffic on an Azure Application Gateway is path-based routing. This feature allows you to define routing rules based on the URL path of incoming requests. By setting up different routing paths, you can direct traffic to various back-end pools depending on the nature of the request, effectively segmenting internal and external traffic based on their respective paths or endpoints. For example, you could configure one path for requests served from the public internet and another path for requests coming from a specific internal network. This capability is crucial for implementing security best practices and ensuring that different types of traffic are managed correctly. While other options, such as multi-site listeners, health probes, and SSL offloading, play important roles in the functionality of the Application Gateway, they do not specifically address the requirement for traffic separation. Multi-site listeners are used to handle requests for different hosts, health probes monitor the status of back-end services, and SSL offloading deals with decrypting SSL traffic; none of these functionalities are designed for direct traffic separation like path-based routing.

The correct feature to configure for separating internal and external traffic on an Azure Application Gateway is path-based routing. This feature allows you to define routing rules based on the URL path of incoming requests. By setting up different routing paths, you can direct traffic to various back-end pools depending on the nature of the request, effectively segmenting internal and external traffic based on their respective paths or endpoints.

For example, you could configure one path for requests served from the public internet and another path for requests coming from a specific internal network. This capability is crucial for implementing security best practices and ensuring that different types of traffic are managed correctly.

While other options, such as multi-site listeners, health probes, and SSL offloading, play important roles in the functionality of the Application Gateway, they do not specifically address the requirement for traffic separation. Multi-site listeners are used to handle requests for different hosts, health probes monitor the status of back-end services, and SSL offloading deals with decrypting SSL traffic; none of these functionalities are designed for direct traffic separation like path-based routing.