Watchguard Network Security Practice Test

How should you define a destination in your HTTP-proxy policy for a site with multiple subdomains?

1. Configure a host name for update.example.com.

2. Configure an FQDN for *.example.com.

3. Add IP addresses for each software update server.

4. Create an alias for all subdomains and known IP addresses.

The correct answer is: Configure an FQDN for *.example.com.

Defining a destination in an HTTP-proxy policy for a site with multiple subdomains is best accomplished by configuring a Fully Qualified Domain Name (FQDN) that utilizes a wildcard, such as *.example.com. This approach allows the proxy to recognize all subdomains under the main domain (example.com) without the need for individual entries for each subdomain. The reason this method is effective is that it provides a single, comprehensive rule that covers all current and future subdomains, making management easier and ensuring that any subdomain traffic is processed according to the policy. With a wildcard, if new subdomains are added, they will automatically be included in the policy without requiring additional configuration. This contrasts with defining specific hostnames for individual subdomains, which can lead to increased administrative overhead and the potential for errors if subdomains are added or modified later. Adding IP addresses could also be unmanageable due to the dynamic nature of subdomains, and creating an alias for all subdomains can complicate the configuration and may not provide adequate coverage for future modifications. Thus, using an FQDN with a wildcard is the most efficient and practical solution for managing access to websites with multiple subdomains.