After deploying the Steelhead appliances in-path, you are not seeing any optimization between 10.11.0.128 and
10.11.23.18.

Look at the following trace in the exhibit and explain why: (HINT: Look at the SYN packet)

You enabled port transparency but noticed that active FTP connections are failing. What may be the problem?

Refer to the exhibit.

Corp-A and Corp-B have overlapping address space and therefore the network administrator implemented NAT
to overcome this. Users from Corp-A NAT to 172.16.1.0/24 and users from Corp-B NAT to 172.16.2.0/24.
Users in Corp-A use the destination address of 172.16.2.0/24 to access the resources in Corp-B. The servers
in Corp-B use the client IP for authentication. You deploy the Steelhead appliance using the default WAN
visibility mode but noticed all the connections are passed-through. What is the likely problem?

Refer to the exhibit.

Corp-A and Corp-B have overlapping address space and therefore the network administrator implemented NAT
to overcome this. Users from Corp-A NAT to 172.16.1.0/24 and users from Corp-B NAT to 172.16.2.0/24.
Users in Corp-A use the destination address of 172.16.2.0/24 to access the resources in Corp-B. The servers
in Corp-B use the client IP for authentication. What do you need to do in order to make this deployment work?
(Select 2)

To increase the high availability of a site at a remote office, you decided to install a second Steelhead appliance
as an active/active serial cluster. However, after installing the second Steelhead appliance at the remote site,
users started complaining about slow access to the data center. You have verified that this is not a duplex
issue. At the data center location all users access the Internet which pass-through the Steelhead appliances.
What is the most likely problem?

A customer noticed that after deploying the Steelhead between their switch and router, OSPF takes much
longer to re-converge after the router fails. Which RiOS feature can you enable to reduce the convergence
time?

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?

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

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?

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