700-281 · Question #40
Which S-Series CLI command can help troubleshoot WCCP?
The correct answer is D. tail proxylogs. tail proxylogs surfaces real-time proxy log output, which captures WCCP-redirected traffic and any errors generated when the S-Series processes (or fails to process) connections arriving via WCCP - making it the right tool when diagnosing whether traffic is being forwarded…
Question
Which S-Series CLI command can help troubleshoot WCCP?
Options
- Aweep debug enable
- Bshow weep
- Ctail accesslogs
- Dtail proxylogs
How the community answered
(24 responses)- A8% (2)
- B4% (1)
- D88% (21)
Explanation
tail proxylogs surfaces real-time proxy log output, which captures WCCP-redirected traffic and any errors generated when the S-Series processes (or fails to process) connections arriving via WCCP - making it the right tool when diagnosing whether traffic is being forwarded, dropped, or mishandled.
Why the distractors are wrong:
- A. weep debug enable - Not a valid CLI command; "weep" is a misspelling of WCCP and this syntax doesn't exist on the S-Series.
- B. show weep - Similarly invalid; there is no
show weepcommand in the S-Series CLI. - C. tail accesslogs - Access logs record completed user transactions at the application layer, not the WCCP control/forwarding plane, so they won't reveal protocol-level redirection problems.
Memory tip: Think "WCCP delivers traffic to the proxy, so proxy logs are where you look." The word proxy in proxylogs maps directly to the role WCCP plays - redirecting traffic to the proxy appliance.
Topics
Community Discussion
No community discussion yet for this question.