An administrator must protect an application on multiple domains or hosts. What should the administrator configure to complete this action?

In PingAccess, a Virtual Host is the component that defines the combination of a hostname and port that PingAccess listens on for incoming requests. To protect an application that is accessible via multiple domains or hosts (e.g., app.company.com and app.company.net), the administrator must configure Virtual Hosts for each of these hostnames. These Virtual Hosts then direct traffic to the appropriate back-end application, allowing a single application to be served and protected across multiple domains.

A. Sites: Sites are used to group application resources by their context paths (e.g., /app, /api), not by their hostnames or domains.

C. Redirects: Redirects are a type of rule action used to send a user's browser to a different URL; they do not configure PingAccess to listen on multiple domains.

D. Rules: Rules contain the logic and conditions for granting or denying access to a resource; they do not define the network endpoints (hostnames) for an application.

1. Ping Identity Documentation, PingAccess 7.3 Administrator's Guide, "Virtual hosts" section: "A virtual host is a combination of a host name and a port that PingAccess listens on for incoming requests. When a request is received, PingAccess matches the host and port in the request to a configured virtual host to determine which application to send the request to." This section explicitly states that Virtual Hosts are the mechanism for handling requests based on hostnames.

2. Ping Identity Documentation, PingAccess 7.3 Administrator's Guide, "Sites" section: "A site is a collection of context paths that represent a logical grouping of resources on a back-end server." This confirms that Sites are concerned with the URL path, not the host.

3. Ping Identity Documentation, PingAccess 7.3 Administrator's Guide, "Adding an application" section: The application configuration workflow shows that an application is associated with one or more Virtual Hosts and a Site, clearly separating the function of each component. A single application can be mapped to multiple Virtual Hosts to serve it on different domains.