101-01 Riverbed Certified Solutions Associate Questions and Answers

Create a specific in-path rule for this application, and enable auto kickoff.

Configure an ‘application definition’ for the application, and place it in an application group where kickoff is applied.

Enable ‘Reset Existing Client Connections on Start Up’ in the general service settings.

Create an ‘application definition’ for the application and select ‘enable kickoff ‘in the application properties.

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.

Create a trust relationship between the SteelHeads.

Install the SSL server certificate and key or proxy server certificate on the server side SteelHead.

Create an in-path rule on the client side SteelHead.

Install a proxy server certificate on the client side SteelHead.

Enable HTTP optimization on both SteelHeads.

With degraded, only one alarm has been triggered, whereas with critical, two or more alarms were triggered

With degraded, the Steelhead appliance is still optimizing traffic, whereas with critical the Steelhead may or may not be optimizing

With degraded, there is no optimization due to a software problem, whereas with critical there is no optimization due to a hardware problem

With both degraded and critical, optimization functions as normal however administrator attention is required

LRU (Least Recently Used)

FIFO (First In First Out)

LIFO (Last In First Out)

MRU (Most Recently Used)

ADH (Arbitrary Data Hits)

riverbedcmc

cmcsteelhead

cmcriverbed

steelheadcmc

Concurrent usage

Per seat

Hybrid per seat/concurrent usage

Steelhead Mobile does not use a licensing model as long as you do not exceed the capacity of the SMC

1

2

3

4

Logical In-path / Physical In-path

Server-side out-of-path / Physical In-path

Server-side out-of-path / Logical In-path

All methods above can be configured on a single Steelhead appliance simultaneously

Version 1

Version 2

Version 9

Version 12.2.18

Remote path

Username

CMC hostname

Password

RADIUS authentication

Number of simultaneous optimized connections

The maximum optimized WAN bandwidth

The size of datastore

The number of applications used by the enterprise

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

Application performance

Data transfer speed over the WAN

Data transfer speed over the LAN

Quality of service

WORM stability

Prototyping

Cloud portal is a resource that registers SteelHeads, allowing them to use SteelHead SaaS.

Cloud portal is a resource where the SaaS certificates are managed.

Cloud portal is troubleshooting resource to which all SteelHeads report data.

Cloud Portal collects data reduction and netflow statistics for SaaS applications.

Cloud Portal collects data reduction statistics for SaaS applications.

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

RiOS 8.0 for SteelHead and 4.0 for Interceptor

The SCC must have joined the Windows domain

Pre-trusted SSL certificates on the devices and SCC

The serial number of the managed device to be preconfigured in the SCC

The name “riverbedcmc” to be an entry in DNS resolving to the SCC primary IP address

SCC does not support multi-tenancy. A virtual or physical SCC would need to be provisioned for each customer.

The SSL certificate for SCC management would need to be distributed to the customers.

RADIUS or TACACS+ would need to be used to offload the authentication to achieve the privileges required.

HTTP server should be disabled for the web UI and only SSL used.

Each customer would have to be configured with privileges for their own SteelHeads and no others.

Primary

WAN

LAN

AUX

Console

Primary

LAN

Inpath0_0

Auxiliary

WAN

Rapid deployment of distributed Steelhead appliances

Simplifies ongoing configuration and management of distributed Steelhead appliances

Health monitoring of distributed Steelhead appliances

Performance reports of distributed Steelhead appliances

All of the above

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.

Profiler export

Quality of Service bandwidth allocation

Subnet side rules

Secure Transport

Path Selection

FAT

NTFS

FAT32

UFS

EXT3

An auto-discover rule with the IP address of the server-side Steelhead appliance

A fixed-target rule with the Primary IP address of the server-side Steelhead appliance

A fixed-target rule with the IP address of the destination server

No configuration is required

To speed up certain applications

To reduce the number of connections used

To reduce WAN utilization

To make UDP faster

In-Path Rules

Peering Rules

Connection Forwarding

Services

Simplified Routing

0

1

2

3

GUI

CLI

RADIUS/TACACS+

Can be done via the Central Management Console

DNS server

Number of connections per second

Data deduplication

Bandwidth

Latency

TCP window size

Optimization

The amount of disk space available for Scalable Data Referencing (SDR) use

The amount of disk space available for optimization use

The amount of memory available for optimization use

The amount of memory available for SDR use

The amount of CPU available for optimization use

Weighted Random Early Discard

Weighted Fair Queuing

Hierarchical Fair Service Curve

Class Base Weighted Fair Queuing

Reduces transport protocol inefficiencies

Prioritizes application traffic

Virtually expands TCP windows

Reduces WAN round trips at the application layer

1

2

3

4

5