Free and Premium Riverbed 299-01 Dumps Questions Answers

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.

The Profiler assigns a host to all overlapping custom groups.

The Profiler assigns a host to the custom group whose definitions has the shortest matching prefix.

The Profiler assigns a host to the custom group whose definitions has the longest matching prefix.

An error message is generated.

Hosts

Peers Group

Host Group Pairs

Peer Group with Ports

Host Pairs

The flow includes the UDP protocol.

The traffic was not reported by a Cascade Sensor or Cascade Shark appliance.

The traffic was not reported by a Steelhead appliance's CascadeFlow

The start time for the connection was prior to the timeframe selected for the traffic query.

The packets involved in the initial setup of the TCP connection were not seen by a Cascade Sensor or Cascade Shark appliance.

1 second on a local System, 10 milliseconds on Cascade Sharks.

1 millisecond for any View.

1 millisecond for specific Views.

Generally minimum 1 second, maximum 1 day.

It obtains L2 retransmissions from switches and routers via SNMP.

It obtains TCP retransmissions by tracking TCP sessions via the Cascade Sensor.

Cascade does not track retransmissions.

Cascade obtains retransmissions from NetFlow and/or sFlow marked with the TCP push flag.

Connect a cross-over cable from your laptop to the Ethernet management port and connect through the Web browser to the default IP Address of 192.168.1.10.

Connect a cross-over cable from your laptop to the Auxiliary Ethernet port and connect through the Web browser to the default IP Address of 192.168.1.10.

Connect by KVM or Serial Console and run the command line tool, sa_wizard, to perform the initial configuration.

Connect to the appliance using the Riverbed Central Management Console (CMC) on its default IP Address and perform the initial configuration.

Through Radius Server(s)

From Domain Controller(s)

Through LDAP queries

Via SNMP queries

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

Per each capture job

Per each trace clip

Per each capture port

Per each capture board/aggregating port

Per each Cascade Shark appliance

Any active timeout can be used; Cascade will calculate the statistics accordingly and update the dashboard accordingly.

60 Seconds.

60 Milliseconds.

15 Minutes.

1

2

3

4

Unlimited

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.

Top Hosts

Top URLs

Watched Interfaces

Current Events

Active time-out setting for flows should be set to 600 seconds.

Inactive time-out setting should be set to 15 seconds.

NTP should be configured on the device.

Active time-out setting for flows should be set to 60 seconds.

They appear in the my-views main directory.

Views that take advantage of the trending/indexing data load faster.

The file icon includes a colored-lightning bolt.

The file loads faster into Wireshark.

Additional pre-defined filters and watches are available.

You must consider how many capture cards are required.

You must consider how much disk space is required.

You must consider the write-to-disk speed required.

You must consider how many Cascade Pilot consoles will be connecting.

You must consider how many Cascade Profilers the appliance will export to.

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.

Cascade Shark

Router

Layer 3 switch

Steelhead appliance

Cascade Sensor

10.0.0.0/23 United_States

0.0.0.0/0.0.0.0 Worldwide

24.32.8.43/32 CEO_Printer

192.168.0.5/255.0.255.0 Printers

10.38.14.1/255.255.255.255 My Computer

11 for the Cascade Profiler, 3 Cascade Gateways

10 for the Cascade Profiler, 3 Cascade Gateways

11 for the Cascade Profiler, 5 Cascade Gateways

10 for the Cascade Profiler, 5 Cascade Gateways

12 for the Cascade Profiler, 4 Cascade Gateways

Unlimited

Ten

Four

Twenty

Traffic between Virtual machines is not switched; it is routed by the standard vRouter included with ESXi

A standard or distributed vSwitch which comes with ESXi must be used, there is not 3rd party software available

A 3rd party virtual switch is required such as the CISCO Nexus 1000v as no standard vSwitch exists with ESXi

The included standard vSwitch of the CISCO Nexus 7000

The included standard vSwitch or the CISCO Nexus 1000v

When the traffic flow matches more than one Application signature. This indicates that the one Application may have been tunneled over the other.

When an Application runs over a non-standard port (such as TELNET traffic on Port 80).

When a "port definition" is non-standard (e.g. when you change tcp/80's definition from http to telnet).

When a Layer-4 Application Mapping is defined.

SNMPv1 Only

SNMPv2 Only

SNMPv1 and SNMPv2

SNMPv1 and SNMPv3

User name

Host IP address

Host MAC address

The physical switch port a specific host is connected to

Switch port traffic levels

Switch port status

SNMP traps from the switch

Under the traffic reports Advanced Tab, place "192.168.1.100" in the Host field – select "Acting as Server" in the drop down, enter "tcp/25" in the Protocol field and select "Hosts" in the "report-by" pull down.

Under the traffic reports Advanced Tab, place "192.168.1.100" in the Host field – select "Acting as Server" in the drop down, enter "tcp/25" in the Protocol field and select "Peers Hosts" in the "report-by" pull down.

Under the traffic reports Advanced Tab, place "192.168.1.100" in the Host field – select "Acting as Client and Server" in the drop down, enter "tcp-25" in the Protocol field and select "Hosts" in the "report-by" pull down.

Under the "Quick Reports" pull down from the dashboard page, select "Host" enter the IP Address and hit return.

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.

You can connect directly to the Cascade Shark with Cascade Pilot to begin analysis.

You can connect directly to the Cascade Shark with Cascade Gateway to begin analysis.

You can start analysis on the Cascade Profiler based upon flow data that has been sent from Cascade Shark to Cascade Profiler.

You can export data from a capture job directly to a packet capture (pcap) file and open in any tool that accepts pcap format.

You can start by loading views of the data from the Cascade Shark Appliance Web GUI before export to Wireshark.

1-d; 2-b; 3-c; 4-a; 5-b

1-e; 2-c; 3-d; 4-a; 5-b

1-d; 2-c; 3-e; 4-b; 5-a

1-d; 2-c; 3-e; 4-a; 5-b

1-e; 2-d; 3-c ; 4-b; 5-a

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.

Appear with a red lightning bolt icon within Cascade Pilot.

Appear with a lock icon within Cascade Pilot.

Appear with a grey lightning bolt icon within Cascade Pilot.

Appear with a yellow lightning bolt icon within Cascade Pilot.

Appear with the trace clip name in red text within Cascade Pilot.

Average drops

Average retransmits

Average response time

Average utilization

Total bandwidth bits

Longest Match

Shortest Match

IP & Port

IP

Unlimited

Ten

Four

Twenty

Is either a BPF or Wireshark Display filter only.

Can be created from a chart.

Can be changed after applying a View.

Is the equivalent of the Wireshark "display filter input".