101-01 Riverbed Certified Solutions Associate Questions and Answers

In-path rules

Optimization rules

Load balancing rules

Peering rules

TCP rules

Acceleration policies

Drop the new data

Create a tunnel to optimize the data

Scalable Data Referencing creates and sends new reference pointers to the peer Steelhead appliance

Compress the data using Lempel-Ziv and sends it to the peer Steelhead appliance

Sends only the references for the data to the counterpart Steelhead appliance

On the Home page of the Steelhead appliance

Go to Configure > Optimization > General Service Settings

Use the “show module” CLI command

Go to Reports > Maintenance > System Info

Go to Configure > Configurations > Boot Order Info

In-Path Rules

Peering Rules

Connection Forwarding

Services

Simplified Routing

All optimized connections flow over the OOB splice.

The OBB splice is only used by SteelHead mobile clients.

The OBB splice is only used to check the peer SteelHead is available.

It is control channel that is used to exchange version and feature information between SteelHeads.

Remote control using a modem or ISDN device

IPMI “lights out” Remote control management

Export of netflow statistics

SteelFusion Edge device connection

Data store synchronization

Transparent Proxy

MAPI Prepopulation

MAPI Offline Optimization

Connection Pooling

MAPI Tunneling

Cold, the data now travels in another direction so the Steelhead appliance needs to relearn the data

Cold, the file has been changed to the file needs to be stored again

Warm, all the data has been seen by the Steelhead appliances before

Warm, the transaction prediction module of the Steelhead appliance can detect the application and accelerate the transfer

Partially warm, the Steelhead appliances only need to learn the new data

Flat

Hierarchical

WRED

LLQ

FEC

GUI

CLI

RADIUS/TACACS+

Can be done via the Central Management Console

DNS server

On the LAN side branch office Steelhead

Directly connected to the AUX interface

On the same switch as the WAN side interface

In the same subnet as the file server

It can never be done

Only Port Transparent

Only Correct Addressing

Only Full Addressing

Full Transparency, Port Transparency and Correct Addressing can be configured simultaneously

1

2

3

4

It depends on the WAN visibility mode

Optimizes VoIP flowing through proxy servers

Removes the need for specific servers in the branch offices

Allows for continued operations of specific functionality in the event of a WAN failure

Provides parallel forwarding domains for asymmetrical routing

Pass

Accept

Discard

Auto

Load Balancing

Redirection

Peer Affinity

Optimization

Store SDR data

Booted partition

Backup partition

Both the boot and backup partitions

The image is only installed into a partition after a reboot (from a temporary location)

Upgrades can only be done from the CLI

TACACS+ authentication

RADIUS authentication

Secure Vault

Datastore encryption

Reduces transport protocol inefficiencies

Prioritizes application traffic

Virtually expands TCP windows

Reduces WAN round trips at the application layer

Blocks all traffic.

Routes all traffic.

Passes through all traffic.

Fast as the data patterns are recognized by SDR regardless of direction or which unencrypted application protocol is used

Slow as the data is being transported via a different protocol and the SteelHead needs to learn the new patterns

Fast as the SteelHead now has a local copy of the file in the web proxy cache

Slow as the data is travelling in a different direction and the SteelHead needs to learn the new patterns

1

2

3

4

Primary

LAN

Inpath0_0

Auxiliary

WAN

Transport Streamlining

Application Streamlining

Data Streamlining

Storage Streamlining

Load balances connections across Steelhead appliances

Provides redundancy in case of Steelhead appliance failure

Maintains stateful connection table if a Steelhead appliance fails

Allows clustering of multiple Steelhead appliances

Windows 2000

PDA

Windows XP

Vista-32

Linux

100

256

512

2000 and above

CIFS

WCCP

MAPI

ATP

Lotus Notes

Location Awareness

Data store synchronization

Fixed-target rules

Branch Warming

E, Connection Forwarding

WAN0_0

LAN0_0

Inpath0_0

Primary

Every SteelHead is configured with a registration key included in a RiOS upgrade.

All the configuration is done from the Riverbed Cloud Portal.

Every SteelHead is configured with a new license in the standard form LK1-SHSaaS-XXX.

Every SteelHead is configured with the same registration key copied from the Riverbed Cloud Portal.

MXTCP

SDR

LZ

Optimization blades

HSTCP

In direct mode, the cloud optimized traffic is encapsulated at the branch-side SteelHead appliance.

Direct mode cannot be used if the internet traffic exit points is centralized at the customer data center and not available from the branch.

In backhaul mode the cloud-optimized traffic is encapsulated at the data center but the SSL optimization starts at the branch.

Backhaul mode allows to optimize traffic to the cloud from the data center without the need of a branch SteelHead.

Using the Riverbed public support site

Contacting VMware

Virtual Steelhead appliance license keys are included in the install package

Base licenses are not required

Only SSL licenses are not included