156-587 · Question #7
What is the correct syntax to turn a VPN debug on and create new empty debug files?
The correct answer is B. vpn debug truncon. Option B (vpn debug truncon) is the correct Check Point firewall CLI command because it uses the exact syntax required: vpn debug (two separate words) followed by truncon (a single compound argument meaning "truncate + on"), which simultaneously enables VPN debugging and…
Question
What is the correct syntax to turn a VPN debug on and create new empty debug files?
Options
- Avpn debuq trunkon
- Bvpn debug truncon
- Cvpndebug trunc on
- Dvpn kdebug on
How the community answered
(38 responses)- B92% (35)
- C5% (2)
- D3% (1)
Explanation
Option B (vpn debug truncon) is the correct Check Point firewall CLI command because it uses the exact syntax required: vpn debug (two separate words) followed by truncon (a single compound argument meaning "truncate + on"), which simultaneously enables VPN debugging and creates fresh, empty debug log files by truncating any existing ones.
Why the distractors fail:
- A (
vpn debuq trunkon) has a typo - "debuq" misspells "debug" with aq, andtrunkonis not a valid argument. - C (
vpndebug trunc on) mergesvpnanddebuginto one word, and splitstrunconinto two words - both errors make this syntactically invalid. - D (
vpn kdebug on) useskdebug, which is not the correct subcommand for this operation; it references a different (nonexistent) keyword.
Memory tip: Think of truncon as "truncate + on" - it clears old logs and switches debug on in one step. Pair that with vpn debug (always two words, just like how you'd say it aloud) and the full command clicks into place: "VPN debug: trunc on."
Topics
Community Discussion
No community discussion yet for this question.