156-915.77

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

Question 121

Included in the customer's network are some firewall systems with the Performance Pack in use. The customer wishes to use these firewall systems in a cluster (Load Sharing mode). He is not sure if he can use the Sticky Decision Function in this cluster. Explain the situation to him.

  1. Sticky Decision Function is not supported when employing either Performance Pack or a hardware-based accelerator card. Enabling the Sticky Decision Function disables these acceleration products.
  2. Cluster XL always supports the Sticky Decision Function in the Load Sharing mode.
  3. The customer can use the firewalls with Performance Pack inside the cluster, which should support the Sticky Decision Function. It is just necessary to enable the Sticky Decision Function in the Smart Dashboard cluster object in the Cluster XL page, Advanced Load Sharing Configuration window.
  4. The customer can use the firewalls with Performance Pack inside the cluster, which should support the Sticky Decision Function. It is just necessary to configure it with the Cluster XL_SDF_enable command.

Question 122

A connection is said to be Sticky when:

  1. The connection information sticks in the connection table even after the connection has ended.
  2. A copy of each packet in the connection sticks in the connection table until a corresponding reply packet is received from the other side.
  3. A connection is not terminated by either side by FIN or RST packet.
  4. All the connection packets are handled, in either direction, by a single cluster member.

Question 123

How does a cluster member take over the VIP after a failover event?

  1. Broadcast storm
  2. iflist -renew
  3. Ping the sync interface
  4. Gratuitous ARP

Question 124

Check Point Clustering protocol, works on:

  1. UDP 500
  2. UDP 8116
  3. TCP 8116
  4. TCP 19864

Question 125

A customer is calling saying one member's status is Down. What will you check?

  1. cphaprob list (verify what critical device is down)
  2. fw ctl pstat (check sync)
  3. fw ctl debug -m cluster + forward (forwarding layer debug)
  4. tcpdump/snoop (CCP traffic)