Weekend Special Limited Time 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code = simple70

Home
Riverbed
RCSP-APM
499-01
Riverbed Certified Solutions Professional – Application Performance Management Questions and Answers

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

Practice at least 50% of the questions to maximize your chances of passing.

Exam 499-01 Premium Access

View all detail and faqs for the 499-01 exam

Go to Exam

447 Students Passed

87% Average Score

94% Same Questions

Viewing page 1 out of 6 pages

Viewing questions 1-10 out of questions

Questions # 1:

How do you control the overhead of AppInternals Xpert agents?

Options:

Install agents on a limited number of machines.

Restart the server.

Agents self tune so there is no need to control the overhead.

Never install more than 5 agents.

Use multiple consoles.

Unplug the server.

Answer

Questions # 2:

Which metrics help the user perform heap analysis? (Select 3)

Options:

Percent of free heap

Percent of time garbage collecting

Percent of usage

Average number of live objects

Answer

A, B, D

Questions # 3:

In AppInternals Xpert consoles, you can click on a transaction trace or metric to open the line of source code that defines the generic class.method that generated that transaction or metric when applicable. Which statements are true regarding linking between source code and AppInternals Xpert data? (Select 3)

Options:

You can toggle back and forth between the source code and the AppInternals Xpert performance data to examine selected class/method transactions that exceed a particular duration.

You can open the source code directly into Transaction Trace Warehouse.

In Visual Studio or Eclipse source code, you can click on the name of a generic method or click inside the code for the method and link to traces on transactions that the .NET or Java code generated, and display those transactions in Transaction Trace Warehouse.

You can click on the name of a generic method or click inside the code for the method and link to AppInternals Xpert metrics that the method generated, displaying in the desktop console.

You can open the source code directly into Transaction Trace Analysis.

Answer

A, C, D

Questions # 4:

What useful information can you get from AppResponse Xpert (ARX) database browsing insights? (Select 3)

Options:

Response time for SQL statements

Database usage by application and user

It tracks throughput in terms of database calls, transactions, rows, bytes, and active sessions.

A link to "View Database SQL queries" insights

Answer

A, B, C

Questions # 5:

What granularity of data is available on the Service Management Platform (SMP)? (Select 2)

Options:

1 minute

5 minutes

1 second

15 minutes

Answer

C, D

Questions # 6:

By default, the analysis engine uses a "moving-window" algorithm to determine dynamic limits. You can change the algorithm by changing the DynamicLimitsAlgorithm attribute to any of these values, except:

Options:

MovingWindowPercentile

MovingWindowSigma

HourlyLimits

HistoricalBaseline

HardLimits

Answer

Questions # 7:

JIDA automatically collects metrics from predefined categories of classes except:

Options:

EJBs: classes that implement the javax.ejb.EntityBean or javax.ejb.SessionBean interfaces

JDBC - classes that implement any of several interfaces in the java.sql package

JNDI - classes that implement the javax.naming.Context or javax/naming/directory/DirContext interfaces

Portlets - classes that implement the javax.portlet.Portlet interface

Generic classes

Answer

Questions # 8:

What is the maximum number of managed nodes indicated per symmetric multiprocessor (SMP)?

Options:

100

200

Answer

Questions # 9:

Which tab in the AppInternals Xpert interface do you use to enable continuous tracing for JIDA and .Net data adapter instances?

Options:

Metric Filters

Schedule

Users

Configure Groups

Answer

Questions # 10:

Which statement is incorrect about how dynamic sampling agents (DSAs) manage 1-second data storage?

Options:

By default, the DSA attempts to keep 1-second data for 2 hours. The length of this time period is specified by the RawDataPersistDuration attribute in the dsa.xml file.

The DSA deletes the oldest 1-second data from the database If there is less than 10 percent of free disk space (the default for the RawDataPersistFreeSpaceTargetPercent attribute)

The DSA deletes the oldest 1-second data from the database if the database file is larger than specified in the RawDataPersistMaxDiskTarget attribute (unlimited as default).

If both the RawDataPersistFreeSpaceTargetPercent and RawDataPersistMaxDiskTarget attributes are satisfied, the DSA deletes data, if necessary, to retain only as much data as specified by RawDataPersistDuration.

At startup, and every 2 hours thereafter (or the frequency specified by RawDataPersistPurgeInterval), the DSA deletes the oldest 1-second data from the database.

Answer

Viewing page 1 out of 6 pages

Viewing questions 1-10 out of questions