QUESTION: 153

While looking at the Current Connections page on a client-side Steelhead, you noticed that there is more CIFS traffic on the WAN than on the LAN for some connections. What may be the problem?

1) The source data is compressed or encrypted
2) File server not located on the same subnet as the server-side Steelhead
3) The Steelhead is counting both CIFS optimized and unoptimized traffic
4) CIFS read-ahead
5) CIFS write-behind

1, 4
4, 5
1, 2, 3
1, 2, 5
3, 5

Answer(s): A

Reveal Solution Next Question

QUESTION: 154

In an in-path deployment, if a naked SYN packet arrives on the WAN interface of Steelhead, what probe option is added to this SYN packet for auto-discovery?

Option-76
Option-78
SACK
WSCALE
None of the above

Answer(s): E

Reveal Solution Next Question

QUESTION: 155

If using Fixed-target rules, what Steelhead specific probe options are associated with the SYN packet?

Option-76 (0x4c)
Option-78 (0x4e)
Client-side Steelhead's in-path IP address
Client-side Steelhead's port number
No probes are sent with fixed-target rules

Answer(s): E

Reveal Solution Next Question

QUESTION: 156

Given four Steelheads are deployed in a WCCP cluster and all Steelheads are optimizing traffic to and from the data center. Steelhead-A fails and only Steelhead-B and Steelhead-C are intercepting new connections while Steelhead-D is NOT optimizing any traffic. What is the likely problem?

The load balancing algorithm on the router is broken
Simplified routing is not enabled
Steelhead-B and Steelhead-C are missing the “in-path neighbor continue-intercept” command
Steelhead-D is missing the “in-path neighbor allow-failure” command
Need to issue the command “in-path accept connections” on Steelhead-D

Answer(s): D

Reveal Solution Next Question

Free 830-01 Exam Braindumps (page: 40)

QUESTION: 153

QUESTION: 154

QUESTION: 155

QUESTION: 156

830-01 Discussions & Posts