Free Riverbed 299-01 Practice Exam with Questions & Answers | Set: 5

Cascade Sensor only

Cannot get QoS data on Cascade

Cascade Sensor and Cascade Gateway

CascadeFlow traffic only

NetFlow and IPFIX traffic only

Increase in Server Delay

Decrease in Average Connection Application-level Throughput

Increases in the number of TCP retransmissions

Decreases in the number of new connections to the application servers

Increase in the number of Active Connections

Cascade Profiler local database

User account specifies authentication by RADIUS

TACACS

RADIUS server to authenticate the user

Views should always be applied directly to the job trace.

Trace clips should first be created, and views applied to them.

Packets should be exported from the capture job trace before beginning analysis.

The capture job trace should first be indexed by right-clicking on it and selecting "Index".

You must have at least three days of history of 15 minute rollups before saving the analytic.

You must have at least three days of history of 15 minute rollups before the analytic initializes.

If you include all possible metrics, but there is no possibility of measuring response time due to lack of Sensor coverage, the analytic will fail to initialize.

The analytic will not alert for a minimum of 1 week during baseline collection.

Both B and C.

By setting intelligent static thresholds for Application metrics and Interface metrics, tolerance can be determined. Cascade will use these thresholds and tolerances to report on deviations indicative of performance problems.

The Customer only needs to identify their critical hosts, interfaces and/or applications, and Cascade will automatically baseline their behavior and report on deviations indicative of performance problems.

The Performance Analytics use knowledge of hosts, interfaces, and/or applications are able to detect security threats such as host scans and worms.

After baselining is completed, Cascade can re-route congested traffic to avoid congested application delivery paths.

Apply a View on the live interface and then start a Capture Job on the capture port to analyze traffic later.

Start a Capture Job on the capture port with a BPF filter and apply a View on the live interface for the same capture job.

Start a Capture Job on the capture port, apply a View on the live interface and create a trace clip for the time window of interest.

Never create a Capture Job to prevent packet drops.

The smallest bandwidth and packet count recorded by the five devices.

The largest bandwidth and packet counts recorded by one of the interfaces on one of the five devices.

The mean bandwidth and packet count recorded by the five devices.

The highest LAN packet count recorded by either Steelhead.

None of the above – the flow records store only the first byte and packet count reported by any of the reporting devices.

When the file is opened in Cascade Pilot for analysis.

When the file is imported into Cascade Pilot for analysis.

When the first view is applied to the file.

When "Add Trend Index" is selected from a right-click menu within Cascade Pilot.

When the file is copied onto a Cascade Shark appliance.

No.

Yes, you can do this with the "ARIN" lookup in "external links". The customer can also add additional external links if they have other sites they use to look up IP Addresses.

This is available as a column in any report that displays the IP Address.

This is available under IP Host Group Type.