READ Free Dumps For Checkpoint- 156-215
| Question ID 18743 | Your SmartCenter Server fails and does not reboot. One of your remote Security Gateways |
| Option A | Since the SmartCenter Server is not available, the remote Gateway cannot fetch the Security Policy. Therefore, no traffic is allowed through the Gateway. |
| Option B | Since the SmartCenter Server is not available, the remote Gateway cannot fetch the Security Policy. Therefore, all traffic is allowed through the Gateway. |
| Option C | The remote Gateway fetches the last installed Security Policy locally, and passes traffic normally. The Gateway will log locally, since the SmartCenter Server is not available. |
| Option D | Since the SmartCenter Server is not available to the remote Gateway, fetching the Security Policy and logging will both fail. |
| Option E | Since the SmartCenter Server is not available, the remote Gateway uses the local Security Policy, but does not log traffic. |
| Correct Answer | C |
| Question ID 18744 | Sarah is the Security Administrator for a sporting-goods manufacturer. Sarah has |
| Option A | The Rule Base includes a rule accepting FTP to any source, and from any destination. |
| Option B | The SmartDefense > Application Intelligence > FTP Security Server screen does not have the radio button set to "Configurations apply to all connections". |
| Option C | The FTP Service Object > Advanced > Blocked FTP Commands list does not include CWD and FIND. |
| Option D | The Web Intelligence > Application Layer > FTP Settings list is configured to allow, rather than exclude, CWD and FIND commands. |
| Option E | The Global Properties > Security Server > "Control FTP Commands" box is not checked. |
| Correct Answer | B |