During analysis of a scenario, you realize that the throughput becomes flat as Vusers continue to increase. What is the likely cause?
Bandwidth problem
A database server problem
A web server connection problem
An application server connection problem
Which Analysis graph shows the number of transactions against transaction response times?
Transactions per Second
Average Transaction Response Time
Transaction Response Time Under Load
Transaction Response Time (distribution)
Which HTTP error code indicates that an individual business process is failing under load or the web application itself has crashed?
400
401
403
500
What could be the possible reason/reasons for poor response time bottleneck
• High percentage of CPU usage
• Poor logical database design, such as bad table design
• Inefficient session and state management
• High queue length on server side
Which one amongst the following is not the important performance counter for identifying Memory related bottleneck
Available Memory Bytes
Committed Memory Bytes
Memory Pages / seconds
% User Time
What is the recommended transaction monitoring frequency
5 Seconds
10 Seconds
15 Seconds
30 Seconds
What is the primary reason Ramp Down functionality is used?
• To let all Vusers stop at once
To gradually release resources of the system after a heavy load
To monitor Performance Center servers
None of these
Which one amongst the following counters are referred to identify Disk related performance issues
Disk sec / Transfer
Network Interface\ Bytes Total/sec
Server\ Bytes Received/sec
Packets Received Errors
When , in the analysis graph you see the committed bytes keep on increasing and available bytes decreasing, what could be possible reason behind it
Disk Issues
Network Bandwidth issues
Memory Leaks
Process Bottlenecks
Which is considered best practice on selecting components in the Application Under Test (AUT) to monitor?
monitor just the Database server
monitor just the Application server
monitor all system components present in your AUT
use the performance summary instead of monitoring individual components