299-01 Exam Dumps - Riverbed Certified Solutions Professional - Network Performance Management

Application_Servers

ByFunction

ByLocation

Automatic

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

A combination of IP Address and Port Number

One or more protocol/port combinations mapped to a name

Names mapped to IP subnets

Layer-2 switch ports grouped into a logical name

NetFlow interfaces grouped into a logical name

At least three days of data available.

At least three weeks of data available.

The application specialist available.

Some historical data and some starting point (a server, port, application).

A customer network diagram available.

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.

Save a time window to a trace file for post-capture analysis.

Save a time window and apply Views to analyze a portion of a Capture Job.

Analyze an indexed capture job with Views that support indexing.

Clip a trace file to your desktop.

Watched items (where items are hosts, interface, etc.)

Top items (where items are hosts, interface, etc.)

Top usernames

Unacknowledged Events

Current Events

Last Day Events

One minute flow records are deleted from the file system FIFO (oldest first) once the appliance has filled the space that is allocated.

There is a fixed amount of space on the filesystem for completed reports.

A report template can be marked "keep until I delete it" so that any reports that are scheduled with this template are not automatically deleted from the filesystem.

When the flows or rollup records have been deleted from the filesystem, any saved report that was generated from those flow sources is no longer available.

Users have the ability to allocate additional space to the 1 min flow logs in order to increase retention. This is done at the expense of other rollup resolutions.

sourceIP, destIP, protocol, sourcePort, destPort, QoS

sourceIP, destIP, protocol, destPort

sourceIP, destIP, protocol, sourcePort, destPort

destIP, protocol, destPort

sourceIP, destIP, protocol

About 34 hours with a captured length of 65535 bytes and a packet rate of 400kbps

About 9 hours with a captured length of 1000 bytes and an average traffic rate of 1Gbps.

About 18 hours with a captured length of 65535 bytes and an average traffic rate of 500Mbps.

About 20 hours with a captured length of 500 bytes and an average packet rate of 400kbps.

ARP table on a layer 3 device (router)

CAM (Content Addressable Memory) on a layer 2 device (switch)

Both the ARP and CAM tables from a layer 2 device (switch)

All of the above

None of the above

No, this cannot be done with Cascade.

Set up the query to ask for all hosts between: Hosts "Within" a group "ByInternalHosts: All" (where All is a host grouping containing all inside address space) and for Peers set to "Outside oF. ByInternalHosts:All".

Configure query as B above but also add the Proxy Server to the "Outside" list.

Configure query as B above but also add the Proxy Server as a "not" in the Traffic Expression field. The expression to add would be "not host proxyhost " where proxyhost is the IP Address of the proxy.

The top applications for the previous week.

Only the IPs that a user is authorized to see.

Bandwidth for a host group over the previous day.

Bandwidth for interfaces from devices NOT sending flow data.

Connections for interfaces from devices sending flow data.

SNMP polling from the Gateway

SNMP polling from the Profiler

SYSLOG

All of the above

None of the above

Layer 1 information. For example, for Ethernet tap points this includes signal levels and attenuation.

Layer 2 information. For example, for Ethernet with 802.1Q encapsulation this includes the VLAN identifier and frame size between MAC Addresses

Layer 3 information. For example, for IPv4 this includes the protocol, time-to-live (TTL), and IP Identifier between IP Addresses

Layer 4 Transport information. For example, for TCP this includes TCP flags, size in bytes, and sequence number between IP Addresses.

Application header information. For example, for Web traffic this includes HTTP methods and message numbers (e.g. "200", "404").

Traffic is being sent across the router's interfaces configured for flow export.

There are no firewalls blocking communication between router and Cascade Gateway.

There are no firewalls blocking communication between Cascade Gateway and Cascade Profiler.

The port being used for export on the router matches that which has been configured on the Cascade Gateway.

All of the above.

25%

50%

75%

100%

None of the above

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

An ACL might exist on the flow source (router) and the Cascade Standard Profiler IP address is not in it.

SNMP is not enabled.

The correct IP address of the flow source was not entered into the GUI.

The SNMP read string provided and entered might not be correct.

The flow source is not using the same NTP source as the Cascade Gateway.

No, because a link analytic can monitor only a single interface.

Yes, one can define separate link congestion analytic policies for each WAN interface.

No, because one can only define specific ports to include on a link congestion policy.

Yes, because one can define a port group that includes every UDP and TCP port except for those that include the expected traffic, and that port group can be used for the link congestion analytic policy.

No, and both A and C include valid reasons.

Capturing packets from a SPAN-Port/Port-Mirror whose configuration may generate duplicate packets

Capturing packets from an aggregating TAP

Removing duplicate flows across multiple interfaces

Capturing packets from a 10GB link

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.

Can be created from a single applied View.

Can work on local trace files only.

Can include more than two charts.

Is not available in the regular Cascade Pilot installation.

Cache the most recent 500 IPs.

Obey DNS TTLs.

Cascade does not cache DNS responses.

For 24 hours.

192.168.66.* Web Servers

192.168.0.100/255.255.0.255 Database_Servers

192.168.14.0/24 Mail_Servers

192.168.*.* Boston

Manually configure the interface speeds on the Devices/Interfaces page.

Configure and enable SNMP access to the reporting devices on the Devices/Interfaces page.

Enable NBAR on the routers.

Check the "Interface Utilization" box under the Devices/Interfaces page for each router and/or Steelhead desired.

Configure the appropriate Device Interface Analytic.

Host Groups must be configured.

Cascade Profiler must be successfully polling Steelhead appliances via SNMP.

The WAN-Steelhead interface group must be populated with WAN interfaces for all Steelhead appliances.

The Profiler baseline collection must be complete.

A WAN Optimization reporting template must be configured.

By listing lost packets in the expert window

By using dotted-dashed lines for out-of-sequence segments

By placing error names on the messages within the diagram

By color-coding the messages on the diagram

By using a thicker line for messages that include errors

A Cascade Standard Profiler

An Cascade Enterprise Class Profiler (only from the Dispatcher Module)

A Cascade Shark appliance

A Cascade Gateway

A Cascade Express Profiler

Administrator

Operator

Monitor

Dashboard Viewer

dbadmin

Event Viewer

View Packets

Error Report

Restart Service

View Switch Port

External Link

Identify connection duration.

Look for high server side packet counts.

Look for high number of reset.

Run a report with a Connection Graph.

Run a report on the WAN Interface of the Steelhead.

Run a report with Flow List and look at the topology columns.

Allows Cascade Pilot to load views that take advantage of the Index more quickly.

Includes the number of bytes and packets for each conversation seen by the Cascade Shark appliance.

It is configured on a per-port basis.

It is configured using the sa-wizard as part of the initial configuration.

It is enabled by default per capture job.