156-915.77

156-915.77 practice questions, page 29 of 34, with answer review and explanations.

Question 141

When using Cluster XL in Load Sharing, what is the default method?

  1. IPs, Ports, SPIs
  2. IPs
  3. IPs, Ports
  4. IPs, SPIs

Question 142

If Cluster XL Load Sharing is enabled with state synchronization enabled, what will happen if one member goes down?

  1. The connections are dropped as Load Sharing does not support High Availability.
  2. The processing of all connections handled by the faulty machine is dropped, so all connections need to be re-established through the other machine(s).
  3. There is no state synchronization on Load Sharing, only on High Availability.
  4. The processing of all connections handled by the faulty machine is immediately taken over by the other member(s).

Question 143

In the following cluster configuration; if you reboot sglondon_1 which device will be active when sglondon_1 is back up and running? Why?

  1. Sglondon_1, because it is up again, sglondon_2 took over during reboot
  2. Sglondon_2 because I has highest IP
  3. Sglondon_2 because it has highest priority
  4. Sglondon_1 because it the first configured object with the lowest IP

Question 144

What is a "sticky" connection?

  1. A Sticky Connection is one in which a reply packet returns through the same gateway as the original packet.
  2. A Sticky Connection is a VPN connection that remains up until you manually bring it down.
  3. A Sticky Connection is a connection that remains the same.
  4. A Sticky Connection is a connection that always chooses the same gateway to set up the initial connection.

Question 145

Your network includes Cluster XL running Multicast mode on two members, as shown in this topology: Your network is expanding, and you need to add new interfaces: 10.10.10.1/24 on Member A, and 10.10.10.2/24 on Member B. The virtual IP address for interface 10.10.10.0/24 is 10.10.10.3. What is the correct procedure to add these interfaces?

  1. 1. Use the ifconfig command to configure and enable the new interface. 2. Run cpstop and cpstart on both members at the same time. 3. Update the topology in the cluster object for the cluster and both members. 4. Install the Security Policy.
  2. 1. Disable "Cluster membership" from one Gateway via cpconfig. 2. Configure the new interface via sysconfig from the "non-member" Gateway. 3. RE. enable "Cluster membership" on the Gateway. 4. Perform the same step on the other Gateway. 5. Update the topology in the cluster object for the cluster and members. 6. Install the Security Policy.
  3. 1. Run cpstop on one member, and configure the new interface via sysconfig. 2. Run cpstart on the member. Repeat the same steps on another member. 3. Update the new topology in the cluster object for the cluster and members. 4. Install the Security Policy.
  4. 1. Use sysconfig to configure the new interfaces on both members. 2. Update the topology in the cluster object for the cluster and both members. 3. Install the Security Policy.