299-01 Sample Questions Answers

All Service-based application performance policies

All Service-based policies plus all Performance and Availability analytic policies

All Service-based policies plus all Performance and Availability analytic policies plus all User-Defined Policies

All Service-based policies plus all Performance and Availability analytic policies plus all User-Defined Policies plus all Security policies

None of the above

NetFlow version 5 generally support ingress flow export only; NetFlow version 9 supports both ingress and egress export.

NetFlow version 5 is used for Switches, NetFlow version 9 is used for Routers.

NetFlow version 9 includes information about CPU, Power-status and other router performance characteristics; NetFlow version 5 does not.

NetFlow version 9 includes the ability to export the Time-To-Live (TTL); NetFlow version 5 does not.

NetFlow version 9 includes the ability to export the packet latency, NetFlow version 5 does not.

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.

host_name, device_type, read_only_community_string, write_community_string

host_name, IP_address, read_only_community_string, write_community_string

host_name, IP_address, device_type, read_only_community_string, write_community_string

host_name, IP_address, device_type, read_only_community_string, write_community_string, pass phrase

echo "delete from hostinfo where ipaddr = '10.63.32.0/24';" | psql mazu postgres

Edit the Definition and remove the entry for 10.63.32.0/24 Bracknell_UK

echo "delete from hostinfo where group = 'Bracknell_UK;" | psql mazu postgres write_community_string

Go to Host Groups and insert " #10.63.32.0/24 Bracknell_UK"

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.

The numerical order of the interfaces from right to left in the network device chassis.

The SNMP index number of device interfaces where a poll has not yet been performed.

The numerical order of the interfaces from left to right in the network device chassis.

The SNMP index number of device interfaces where a poll has been performed.

Hover your mouse over the name of the view.

Hover your mouse over the icon in front of the view name.

Open context-sensitive help with the view displayed.

Right-click within the main workspace and select "show view tool tip" from the right hand menu.

The flows that are being viewed in Cascade Profiler must be reported by a Shark appliance.

The user's workstation requires a licensed copy of Cascade Pilot.

The user's workstation requires access to the Cascade Shark appliance on the appropriate TCP Port.

If there are multiple capture jobs configured on the Cascade Shark appliance, the user must select which one to apply the trace clip against.

All of the above.

Packeteer Device

Cascade Gateway

Cascade Sensor

Cisco NBAR device

To de-duplicate duplicate flows sent to the Cascade Profiler appliance caused by the way different Cascade Shark ports may see the same UDP/TCP sessions.

To de-duplicate duplicate flows sent to the Cascade Profiler appliance caused by use of the Aggregating Port seeing the same UDP/TCP sessions.

To de-duplicate duplicate packets that may be collected by the Cascade Shark caused by the way Port Mirroring is configured on a switch.

To de-duplicate duplicate packets that may be collected by the Cascade Shark caused by the way filtering is used on a capture job.

All of the above

The time span of the report does not cover any connection set-up points

Server delay is zero.

The protocol used by the application in not TCP-based.

Application traffic was not seen by a Cascade Sensor.

The server plug-in is needed to measure "Server Delay" and not functioning correctly.

Allow user defined policies the ability to dynamically re-configure host IP parameters when the host triggers an event.

Obtain an IP address on the Management interface on initial power-up.

Obtain an IP address on the Auxiliary interface on initial power-up.

Obtain host MAC address.

A, B, C.

Log Only, SNMP Only, Email Only, SNMP and Email

Log Only, Default, Owner, or any defined recipient

Log Only, Default, Owner or any User Account

Log Only, Default, Owner or any User Name obtained via the Identity Integration

Applications, Ports/Protocols, QOS, Servers, Clients

Ports/Protocols, QOS, Servers, Clients

Applications, Ports/Protocols,

Applications, Ports/Protocols, QOS, Servers, Clients, Interfaces

40

65

17

55

425

Internal hosts only

External hosts only

All hosts

Internal and External hosts only

Specified internal hosts plus the non-routable subnets

Symmetric

Radial tree

Vertical client/server dependency

Starburst

Horizontal tree

1

2

3

4

5

Changes are saved only in the View to which the filter has been applied.

The modified filter is saved on the machine on which Cascade Pilot is running.

The modified filter is saved on any Cascade Shark that Cascade Pilot is connected to.

The changes are lost when you close Cascade Pilot.

Applying a very complex filter statement.

Creating a non-sequential time index.

Creating a trace clip file with trend index data.

Interactively connecting charts from 2 or more views.

Creating a PDF report of a view that can be interactively updated.

Cascade is sized based upon the number of sources that will be sending NetFlow to a Gateway, and the number of Gateway's sending data to a Profiler. Each Gateway is sized to handle a certain number of sources, and each Profiler a certain number of Sensors and Gateways.

Cascade is sized by the packet volume across the environment. Each Sensor and Gateway component can handle a certain packet rate.

The primary measures are flow-rate and topology. Flow-rate drives the size of the solution; topology can determine the placement of Sensors. As a secondary sizing method we can use host count and rule-of-thumb host/flows ratio to estimate the flow-rate.

Cascade is sized purely based upon the number of Servers being monitored in the environment.

Per each capture job

Per each trace clip

Per each capture port

Per each capture board/aggregating port

Per each Cascade Shark appliance

Hosts

Peers Group

Host Group Pairs

Peer Group with Ports

Host Pairs

Set the disk space for that data resolution to 0 in Configuration > Flow Log.

Set the disk space for that data resolution to -1 in Configuration > Flow Log.

Set the disk space for that data resolution to -1 in Configuration > General Settings.

Set the disk space for that data resolution to 0 in Configuration > General Settings.

v1 and v5

v7

v9

all of the above

none of the above

View Packets

Error Report

Restart Service

View Switch Port

External Link

Cascade Standard Profiler can provide network reporting without any other Cascade component IF there are Steelhead appliances reporting to it.

Cascade Shark appliance can provide/export pcap files without Cascade Pilot.

Cascade Express Profiler can provide network reporting without any other Riverbed Product.

Cascade Pilot (not Cascade Pilot Personal Edition (PE)) requires Cascade Shark appliance in order to analyze packets.

Cascade Sensor can forward NetFlow to multiple Cascade Profilers.

The Sensor watches TCP-three-way handshakes to measure Network RTT, Server Delay, and Response Time.

The Profiler will measure the delta between packets reported by each Sensor in the path.

The Sensor will measure HTTP page load times.

The Sensor will measure transaction times of over 100 applications using application signatures.

1

2

3

4

5

v5 & v9

v1

v7 & v8

All of the above

None of the above

NetFlow v5/7/9

Cascade Sensor flow data

Sflow

Packeteer Federated Data Records

All of the above

tcp/8443

udp/123

tcp/41017

tcp/42999

tcp/123