Effective Study Techniques for the Riverbed 101-01 Exam

Blocks all traffic.

Routes all traffic.

Passes through all traffic.

Reset Client-Server Connection

Request System Dump

Request TCP Dump

Reset Client-Controller Connection

Request Memory Dump

The SteelHead attempted to optimize the traffic and failed. When the connections proceeded in passthrough they get treated differently than if they had been optimized.

The SteelHead has detected that a path has gone down and therefore re-routed the traffic.

QoS traffic classification has matched a configured application and moved the traffic into a different QoS class.

This is normal operation of using the Application Flow Engine with path selection, as the SteelHead needs to examine several packets before it can identity the traffic.

Templates that allow Steelhead Mobile clients to connect to Steelhead appliances

Configuration templates to configure groups of Steelhead Mobile clients that have the same configuration requirements

Configuration templates to configure groups of Steelhead Mobile clients that have the same datastore requirements

Configuration templates to configure computer-specific software settings on a Linux system

Steelhead Mobile client software default access policies used to connect to all Riverbed devices

Pass

Accept

Discard

Auto

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

Configure either a Delegation or Replication user.

Configure DNS to include an entry for resolution of the SteelHead primary interface IP address.

Enable SMB signing/Encrypted MAPI support.

Ensble NTP and ensure time is synced with domain controllers.

Steelhead appliance has entered admission control

Steelhead appliance is configured with the incorrect speed or duplex on the Primary interface

Steelhead appliance is configured with the incorrect speed or duplex on the in-path interfaces

Steelhead appliance is not able to acquire a “File Hold Key (FHK)”

Steelhead appliance is not able to acquire an “Opportunistic Lock (oplock)”

Steelhead appliance is not able to acquire a “Double Link (doulink)”

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

Four-Port Copper Gigabit-Ethernet PCI-E

Four-Port SX Fiber Gig-E PCI-X

Five-Port Copper Gigabit-Ethernet PCI-E

Two-Port SX Fiber Gigabit-Ethernet PCI-E

Three-Port SX Fiber Gig-E PCI-X