101-01 Riverbed Certified Solutions Associate Free Practice Exam Questions (2025 Updated)

You can log in to a SteelHead with a RADIUS or TACACS+ authentication system for administrative and monitoring purposes. The following methods for user authentication are provided with the SteelHead:

Local

RADIUS

TACACS+

References:

https://support.riverbed.com/bin/support/static/fbunsuuo632vi3jrspe0evbko9/html/u2pi6l52l4drmhq3uhck9tu7hm/sh_9.2_dg_html/index.html#page/sh_9.2_dg%2Fradius_tacacs.html%23ww224339

With flexible SaaS licensing, all supported SaaS applications can be optimized with a single license, and new applications added with a click of a button. Subscriptions are based on the number of users supported, with no restriction as to which SaaS apps are optimized.

References:

http://www.riverbed.com/se/solutions/solutions-by-technology/saas-and-cloud-performance.html

To configure the remote management port

Physically connect the REMOTE port to the network. You cable the remote management port to the Ethernet network in the same manner as the Primary interface.

* Install the IPMItool on the client machine.

* Assuming the IP address is 192.168.100.100, the netmask is 255.255.255.0, and the default gateway is 192.168.100.1, assign an IP address to the remote management port.

References:

Stingray Services Controller Command-Line Interface Reference Manual, Version 2.0, December 2014, page 201

http://www.brocade.com/content/dam/common/documents/content-types/command-reference-guide/brocade-services-director-comamnd-line-interface-reference-manual.pdf

Reference https://support.riverbed.com/bin/support/static/oc1r4qa2pks6172bsj6fte42p4/html/dhatalm0otkq7neeb7h9e9dl8j/sh_ex_4.6_ug/index.html#page/sh_ex_4.6_ug/path_selection.html

To connect a Steelhead appliance to a switch use a straight-through cable.

Note: Make sure that you have connected your cables as follows:

Steelhead appliance to switch: straight-through cable

Steelhead appliance to router: crossover cable

Steelhead appliance to Steelhead appliance: crossover cable

Steelhead appliance to a host: crossover cable

References:

Steelhead Appliance Installation and Configuration Guide, Version 7.0.3, May 2012, page 46

https://support.riverbed.com/bin/support/download?did=614

Once the initial handshake is completed, the interceptor use destination NATs packets to the steelhead so you will not see this traffic if you are filtering on the original client and server address.

References:

https://splash.riverbed.com/thread/5512

Using Riverbed’s unique MX-TCP functionality, combined with its Hierarchical Fair Service Curve (HSFC) QoS technology, users are simultaneously guaranteed bandwidth for their virtual desktop connections and some of the latency impact is mitigated. The results below show operational improvements for particularly common user actions; results will certainly vary based on use case and network design.

With the Riverbed Data Streamlining technology, which applies to all TCP Traffic, including SSL, and to all WAN Traffic(TCP and UDP), redundant bytes are eliminated from transfers. WAN bandwidth utilization is reduced by 60-95 percent.

References:

http://www.wansolutionworks.com/RiOS.asp

References:

https://support.riverbed.com/bin/support/static/5dmuo8qo6ci1inmbo174n3234j/html/iiteb5endqjlbm8a7d9l6pimi/sh_v_9.5_icg_html/index.html#page/SH-v%20Updates/setupAppliance_shutdown.html

A: OOP configuration does not support auto-discovery. You must create a fixed-target rule on the clientside Steelhead.

C: An out-of-path deployment is generally located on the server-side and is often described as a server-side outof-path deployment.

In an out-of-path deployment, only a SteelHead primary interface is required to connect to the network. The SteelHead can be connected anywhere in the LAN. An out-of-path SteelHead deployment does not have a redirecting device. You configure fixed-target in-path rules for the client-side SteelHead. The fixed-target in-path rules point to the primary IP address of the out-of-path SteelHead. The out-of-path SteelHead uses its primary IP address when communicating to the server. The remote SteelHead must be deployed either in a physical or virtual in-path mode.

References:

https://www.google.com/url?sa=t &rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=0ahUKEwjhle6SmMLbAhXTTn0KHez8DqgQFgg4MAI&url=https%3A%2F%2Fsupport.riverbed.com%2Fbin%2Fsupport%2Fdownload%3Fdid%3Do710tf33523mnq0kehinjukrjh%26version%3D9.7.0&usg=AOvVaw3tfCJMb3u8yAYV2umYyeo5

References:

https://sup port.riverbed.com/bin/support/static/oc1r4qa2pks6172bsj6fte42p4/html/dhatalm0otkq7neeb7h9e9dl8j/sh_ex_4.6_ug/index.html#page/sh_ex_4.6_ug/setupAdminAlarms.html