Which two network addresses are required to be static, non-dhcp addresses when using the Grid Naming?

Answer: A
Explanation:
In a configuration, all the addresses are assigned by administrative action and given names that resolve with whatever name service is provided for the environment. This is universal historic practice, as there has been no realistic alternative. One result is significant turn around time to obtain the address, and to make the name resolvable. This is undesirable for dynamic reassignment of nodes from cluster to cluster and function to function
DHCP provides for dynamic configuration of the hosts IP address but doesn’t provide a good way to produce good names that are useful to external clients. As a result, it is rarely used in server complexes because the point of a server is to provide service, and the clients need to be able to find the server. This is solved in the current release by providing a service (GNS) for resolving names in the cluster, and defining this to the DNS service used by the clients. To properly configure GNS to work for clients, it is necessary to configure the higher level DNS to forward or delegate a subdomain to the cluster and the cluster must run GNS on an address known to the DNS, by number. This GNS address is maintained as a VIP in the cluster, run on a single node, and a GNSD process that follows that VIP around the cluster and service names in the subdomain. To fully implement GNS, you need four things.
1. DHCP service for the public network in question;
[b]2. A single assigned address in the public network for the cluster to use as the GNS VIP.[/b]
3. A forward from the higher level DNS for the cluster to the GNS VIP.
4. A running cluster with properly configured GNS
D60488GC11
Edition 1.1
September 2010
D65231