156-585 無料問題集「CheckPoint Check Point Certified Troubleshooting Expert」

（A）the C2S client uses Browser based SSL vpn and cant be debugged

（B）there is no difference

（C）the C2S VPN uses a different VPN deamon and there a second VPN debug

（D）the C2S VPN can not be debugged as it uses different protocols for the key exchange

（A）capture traffic on both tunnel members and collect kernel debug for fw module with vm, crypt, conn and drop flags

（B）capture traffic on both tunnel members and collect kernel debug for fw module with vm, crypt, conn and drop flags, then collect debug of IKE and VPND daemon

（C）collect debug of IKE and VPND daemon and collect kernel debug for fw module with vm, crypt, conn and drop flags

（D）capture traffic on both tunnel members and collect debug of IKE and VPND daemon

（A）>set core-dump enable
>save config

（B）# set core-dump enable
# save config

（C）$FWDIR/scripts/core-dump-enable.sh

（D）service core-dump start

（A）tedex

（B）scrubd

（C）extractd

（D）tex

（A）Tunnel fails on partner site. It is likely that the Cisco ASA 5540 will reject the Phase 2 negotiation. Check Point continues to present its own encryption domain as 192.168.14.0/23, but the peer expects the two distinct networks 192.168.14.0/24 and 192.168.15.0/24.

（B）Tunnel fails on Joey's site, because he misconfigured IP address of VPN peer.

（C）Tunnel falls on partner site. It is likely that the Cisco ASA 5540 will reject the Phase 2 negotiation. Check Point continues to present its own encryption domain as 192.168.14.0/24 and 192.168.15.0/24, but the peer expects the one network 192.168.14.0/23

（D）Tunnel falls on partner site. It is likely that the Cisco ASA 5540 will reject the Phase 2 negotiation due to the algorithm mismatch.

（A）The authentication on Phase 1 is causing the problem.
Pre-shared key on local gateway encrypted by the hash algorithm created in Packet 3 and Packet 4 doesn't match with the hash on the peer gateway generated by encrypting its pre-shared key

（B）The authentication on Quick Mode is causing the problem
Pre-shared key on local gateway encrypted by the hash algorithm created in Packets 3 and 4 doesn't match with the hash on the peer gateway generated by encrypting its pre-shared key

（C）The authentication on Phase 1 is causing the problem
Pre-shared key on local gateway encrypted by the hash algorithm doesn't match with the hash on the peer gateway generated by encrypting its pre-shared key created in Packet 1 and Packet 2

（D）The authentication on Phase 2 is causing the problem
Pre-shared key on local gateway encrypted by the hash algorithm created in Packets 1 and 2 doesn't match with the hash on the peer gateway generated by encrypting its pre-shared key

（A）CoreXL

（B）SecureXL

（C）Traffic Warping

（D）HyperThreading

（A）-d

（B）-i

（C）-0

（D）-i

（A）rad_settings.C

（B）rad_control.C

（C）rad_services.C

（D）rad_scheme.C

（A）This file contains all the host name settings for the online application detection engine

（B）This file contains RAD proxy settings

（C）This file contains the information on how the Security Gateway reaches the Security Managers RAD service for Application Control and URL Filtering

（D）This file contains the location information tor Application Control and/or URL Filtering entitlements