SiteScope's evaluation 01-2011 v1

The purpose of this test, is evaluate you knowledge in SiteScope.

published on January 10, 201152 responses 1 3.0★ / 5

SiteScope is an agent less tool because:

You need an agent and data collection is synchronous
You don’t need an agent and data collection is asynchronous
You need an agent and data collection is asynchronous
You don’t need an agent and data collection is synchronous

Which is the hardware requirement recommended to install SiteScope in a physical server?

2 GB Memory, 2 GB Hard Disk
4 GB Memory, 10 GB Hard Disk
2 GB Memory, 10 GB Hard Disk
4 GB Memory, 2 GB Hard Disk

SiteScope for Load Runner has the following behavior:

You can run low frequencies and reports cannot be generated.
You can run high frequencies and reports can be generated.
You can run low frequencies and reports can be generated.
You can run high frequencies and reports cannot be generated.

SiteScope 11 can be installed in the following operating systems:

Windows 2008 R2 Hyper-V, Sun Solaris 10, Red Hat AS 5.4
Windows 2008 R2, Sun Solaris 8, Red Hat ES 5.4
Windows 2008 Standard, Sun Solaris 9, Red Hat AS 3.0
Windows 2000 Professional, Sun Solaris 10, Red Hat AS 3.0

In SiteScope 8.x, groups and persistency has the following behavior:

Groups is not a duplicated of groups.
Persistency is not a duplicated of groups.
Groups is a duplicated of groups.
Persistency is a duplicated of groups.

In SiteScope 10.0, the following statement is correct:

Classic UI is available and port 8888 is not being used.
Classic UI is not available and port 8888 is being used.
Classic UI is available and port 8888 is being used.
Classic UI is not available and port 8888 is not being used.

The documents where can be find information about compatibility between monitors and applications are:

“SiteScope Monitor Metrics” and “Release Notes”
“Deployment Guide” and “Using SiteScope Guide”
“SiteScope Monitor Metrics” and “Using SiteScope Guide”
“Deployment Guide” and “Release Notes”

Windows Remote Connections can be configured to use the following methods:

SSH, WMI, NetBIOS
WMI, NetBIOS, Rlogin
NetBIOS, Telnet, WMI
SSH, Telnet, NetBIOS

Two options available for Unix Remote Connections using SSH v1 or SSH v2 are:

“Disable Connection Cache” and “SSH Keep Alive Mechanism”
“Disable Connection Cache” and “SSH authorization method”
“SSH Keep Alive Mechanism” and “SSH authorization method”
“SSH Version 2 Only” and “SSH Port Number”

To configure a Windows Event Log Monitor is required:

Key File or authenticated access to the remote server.
Domain Privileges or Guess access to the remote server.
Domain Privileges or authenticated access to the remote server.
Guess access or Key File.

“Collection method” option in Windows Resources Monitor is not available for the following connection methods:

Telnet and SSH
NetBIOS and Telnet
WMI and NetBIOS
WMI and SSH

A valid regular expression to match only the service called “Server” on Windows Service State monitor is:

/(Server\n)/
/(Server.*)/
/(Server)/
/(^Server$)/

The parameter in Windows Registry to identify which is the JMX Console port is:

-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.authenticate
-Dcom.sun.management.jmxremote.port
-Dcom.sun.management.jmxremote.portConnector

Which is the JAVA specification followed by the JMX monitor:

JSR 003
JSR 160
JSR 262
JSR 255

Which Technologies are supported by the Web Service monitor:

SOAP 1.1 and WDSL 1.2
SOAP 2.0 and WDSL 2.0
SOAP 1.2 and WDSL 1.1
SOAP 1.1 and WDSL 2.0

What are two valid reasons to use WinInet in URL monitors:

When the website use HTTP 1.1 and ASP 1.0
When the website use Kerberos authentication and trusted client side certificates.
When the website is running over an application server like Weblogic or WebSphere.
When the website is using AJAX.

The correct location to copy the JDBC files in order to use Database Monitors is:

<SiteScope folder>\java\lib
<SiteScope folder>\WEB-INF\lib\Lib
<SiteScope folder>\java\lib\ext
<SiteScope folder>\WEB-INF\lib

Which protocol must be enabled on WebLogic server in order to get JMX monitor working:

Remote Method Invocation
Remote Procedure Calls
Internet Inter-ORB Protocol
Java Remote Method Protocol

To avoid problems sending data to BAC, the following parameter must be into master.config:

_topazLogTimeCache=60
_topazSyncFrequency=300
_topazLogMonitorCache=100
_topazEnforceUseDataReduction=false