Pass the Riverbed RCSP-APM 499-01 Questions and answers with ExamsMirror

AppTransaction Xpert

AppResponse Xpert

Riverbed Performance Management Dashboards

AppSensor Xpert

Both provide average data, but AppInternals Xpert has data at 1-second granularity while AppResponse Xpert has data at 1-minute granularity.

Measuring common requests, AppResponse Xpert data provides network and server processing delay while AppInternals Xpert provides server processing delay only.

Assuming response time is being evaluated for a common request available from both data sources, AppInternals Xpert data is the maximum response during each 1-second bucket while AppResponse Xpert data is averaged over a 1-minute bucket.

AppInternals Xpert "Max. Active" metrics on Servlet/JSP/Web Aggregate metrics should exactly match AppResponse Xpert "Connections" metric.

All products must use the same OAS server.

The fully qualified domain name (FQDN) all products use has a common "cookie domain."

The users' web browsers need to send the OAS cookies, which affects the choice of common "cookie domain."

All possible FQDNs must be registered within OAS to allow them to work.

The Web tier is the bottleneck because it has the most open requests waiting for a response.

The DB tier is the bottleneck because it is the lowest tier that is clearly not handling requests in time.

The App tier is the bottleneck because it is the first tier not handling the same number of requests as the tier above it.

The Web tier is the bottleneck because at an Offered Load of 300, there are still 50 requests waiting from the Web tier, and it never recovers. The lower tiers do not get the requests passed to them because the Web tier is not processing fast enough.

The App tier is the bottleneck because the DB tier is handling everything the App tier sends it.

Transaction Trace Warehouse and AppTransaction Xpert

BrowserMetrix and AppResponse Xpert Web Transaction Analysis

AppResponse Xpert HTTP Application and AppInternals Xpert metric data

AppResponse Xpert Web Transaction Analysis and AppTransaction Xpert

BrowserMetrix and Transaction Trace Warehouse

TCP window scaling

Maximum transmission unit (MTU)

TCP maximum segment size

Packet size

It is best to instrument at all tiers for maximum visibility.

It is best to instrument at the web tier, since that is typically the client entry point into the application.

It is best to instrument at the application tier, since it sits between the web and database tiers.

It is best to instrument at the database tier, since it holds the data the client is requesting.

AppInternals Xpert

AppResponse Xpert

AppSQL Xpert

Riverbed Performance Management Dashboards

Look at the waterfall view for individual page views in AppResponse Xpert and verify it has the beacon.gif request to the BrowserMetrix Collector.

View the page source of a page that should be tracked in the browser to ensure it has the initial JavaScript snippet loaded.

Analyze network packets from the browser workstation with AppTransaction Xpert to verify it makes a request to the BrowserMetrix Collector.

View the transaction details from Transaction Trace Warehouse (assuming the back-end is also instrumented with AppInternals Xpert) to check the HTTP headers for presence of a BrowserMetrix cookie.

Look at AppResponse Xpert data for requests to the BrowserMetrix Collector process to validate they occur.

Enable the X-Forwarded-for field.

Route clients around the load balancer.

Create a firewall rule to ensure the client IP addresses are seen.

Specify a route in the router for the client IP addresses.