AZ-700 Question 200
Single answerYou have an existing Azure Application Gateway that currently handles traffic for example.com. Your organization introduces a new domain, store.example.com, which must be routed to a different backend pool than example.com for merchandising services. How should you configure your Application Gateway listeners to accommodate both domains?
- A
Create a new multi-site listener that specifies store.example.com as the Host name, associate it with a dedicated HTTP setting, and link it to a new backend pool.
- B
Use a single basic listener for all HTTP traffic, then rely on path-based routing in the backend pool to separate traffic by domain.
- C
Configure a new IP-based listener for store.example.com on a different public IP address, referencing the same backend pool as example.com.
- D
Enable a wildcard domain listener that accumulates all traffic for multiple domains and forwards requests according to the path property.
Show answer and explanation
Correct answer: A
Explanation
In Azure Application Gateway, multi-site hosting allows you to direct traffic from different domains to separate backend pools. This requires creating listeners with a unique Host name for each additional domain. Refer to Microsoft� documentation at https://learn.microsoft.com/azure/application-gateway/multiple-site-overview for detailed steps on configuring multi-site listeners.
- A. Correct.
Correct. For multi-site hosting, you must create a separate listener specifying the new domain name (store.example.com) in the Host name field. Then, point this listener to a dedicated HTTP setting (with the Host name field matching store.example.com) and a distinct backend pool so that traffic for store.example.com is properly routed.
- B. Incorrect.
Incorrect. A single basic listener without host-based routing rules cannot discern between multiple domains. Path-based routing alone does not differentiate by domain name, so it would fail to send store.example.com traffic to a separate backend.
- C. Incorrect.
Incorrect. You typically don�t need a new public IP or an IP-based listener just because you have an additional domain. A multi-site listener (using the same Application Gateway IP) can distinguish traffic by the Host name instead.
- D. Incorrect.
Incorrect. A wildcard domain listener is not a supported feature for multi-site hosting in Azure Application Gateway. Each site/domain requires a properly configured listener and associated routing rule.