Performance Metrics interview questions — Medium

496 medium-level Performance Metrics questions from our Performance Testing bank, each with the correct answer and an explanation of why it is correct.

What this covers

Performance Metrics appears throughout Performance Testing interviews. At medium level, interviewers are typically checking that you have used it in practice: what you configured, what broke, and how you knew it worked. Work through these, then explain your answer out loud; the second part is what interviews actually test.

20 example questions

  1. 1. "Maximum sustainable throughput within response-time targets" — in Metrics, this describes which of the following?

    • A. P50 (median).
    • B. Capacity.correct
    • C. Coordinated omission.
    • D. Baseline test.

    Why: capacity: Maximum sustainable throughput within response-time targets.

  2. 2. "Delay until the first response byte arrives" — in Metrics, this describes which of the following?

    • A. TPS.
    • B. Little's Law.
    • C. Time to first byte (TTFB).correct
    • D. Connection pool exhaustion.

    Why: time to first byte (TTFB): Delay until the first response byte arrives.

  3. 3. "Bottleneck when no free connections remain" — in Metrics, this describes which of the following?

    • A. Capacity.
    • B. Baseline test.
    • C. Connection pool exhaustion.correct
    • D. Garbage collection pause.

    Why: connection pool exhaustion: Bottleneck when no free connections remain.

  4. 4. "L = λ × W relating concurrency, arrival rate, and time in system" — in Metrics, this describes which of the following?

    • A. Time to first byte (TTFB).
    • B. Garbage collection pause.
    • C. Little's Law.correct
    • D. SLO.

    Why: Little's Law: L = λ × W relating concurrency, arrival rate, and time in system.

  5. 5. "Service-level objective, e.g., 99% of requests under 300ms" — in Metrics, this describes which of the following?

    • A. SLO.correct
    • B. Connection pool exhaustion.
    • C. Coordinated omission.
    • D. Time to first byte (TTFB).

    Why: SLO: Service-level objective, e.g., 99% of requests under 300ms.

  6. 6. "JVM stop-the-world event inflating tail latency" — in Metrics, this describes which of the following?

    • A. Coordinated omission.
    • B. SLO.
    • C. Time to first byte (TTFB).
    • D. Garbage collection pause.correct

    Why: garbage collection pause: JVM stop-the-world event inflating tail latency.

  7. 7. "Reference run against which future results are compared" — in Metrics, this describes which of the following?

    • A. TPS.
    • B. Coordinated omission.
    • C. Baseline test.correct
    • D. SLO.

    Why: baseline test: Reference run against which future results are compared.

  8. 8. Which of the following statements about Metrics is TRUE?

    • A. The average is always the most reliable single latency statistic.
    • B. Tail latency is irrelevant for systems with many users.
    • C. Concurrency is the number of in-flight users or requests at a moment.correct
    • D. Error rate measures how fast successful requests complete.

    Why: Little's Law relates concurrency, throughput, and response time.

  9. 9. Identify the accurate statement about Metrics:

    • A. Error rate measures how fast successful requests complete.
    • B. Throughput and latency are the same metric with different names.
    • C. Monitoring server resources during a load test provides no useful information.
    • D. Apdex scores summarize user satisfaction from response-time thresholds.correct

    Why: Apdex buckets samples into satisfied, tolerating, frustrated.

  10. 10. "Transactions processed per second" — in Metrics, this describes which of the following?

    • A. Time to first byte (TTFB).
    • B. Capacity.
    • C. TPS.correct
    • D. Garbage collection pause.

    Why: TPS: Transactions processed per second.

  11. 11. Which statement correctly describes Metrics?

    • A. Throughput and latency are the same metric with different names.
    • B. P95 latency means 95% of requests failed.
    • C. The average is always the most reliable single latency statistic.
    • D. Throughput measures completed requests or transactions per unit time.correct

    Why: Requests/second quantifies processing capacity.

  12. 12. In the context of Metrics, which of the following is a correct statement?

    • A. Error rate measures how fast successful requests complete.
    • B. Averages mislead because a few very slow requests can hide behind a good mean.correct
    • C. P95 latency means 95% of requests failed.
    • D. The average is always the most reliable single latency statistic.

    Why: Skewed distributions make percentiles more informative than means.

  13. 13. In Metrics, which of the following is described as: "Delay until the first response byte arrives"?

    • A. Garbage collection pause.
    • B. Time to first byte (TTFB).correct
    • C. TPS.
    • D. Baseline test.

    Why: time to first byte (TTFB): Delay until the first response byte arrives.

  14. 14. In Metrics, which of the following is described as: "JVM stop-the-world event inflating tail latency"?

    • A. Connection pool exhaustion.
    • B. Time to first byte (TTFB).
    • C. Coordinated omission.
    • D. Garbage collection pause.correct

    Why: garbage collection pause: JVM stop-the-world event inflating tail latency.

  15. 15. Which Metrics concept matches this description: "Value splitting the faster and slower half of requests"?

    • A. Coordinated omission.
    • B. SLO.
    • C. P50 (median).correct
    • D. Connection pool exhaustion.

    Why: p50 (median): Value splitting the faster and slower half of requests.

  16. 16. In Metrics, which of the following is described as: "Reference run against which future results are compared"?

    • A. Garbage collection pause.
    • B. Baseline test.correct
    • C. Coordinated omission.
    • D. Capacity.

    Why: baseline test: Reference run against which future results are compared.

  17. 17. Which Metrics concept matches this description: "Service-level objective, e.g., 99% of requests under 300ms"?

    • A. SLO.correct
    • B. Connection pool exhaustion.
    • C. TPS.
    • D. Capacity.

    Why: SLO: Service-level objective, e.g., 99% of requests under 300ms.

  18. 18. Which Metrics concept matches this description: "Maximum sustainable throughput within response-time targets"?

    • A. Connection pool exhaustion.
    • B. Little's Law.
    • C. Capacity.correct
    • D. TPS.

    Why: capacity: Maximum sustainable throughput within response-time targets.

  19. 19. In Metrics, which of the following is described as: "Service-level objective, e.g., 99% of requests under 300ms"?

    • A. P50 (median).
    • B. SLO.correct
    • C. TPS.
    • D. Little's Law.

    Why: SLO: Service-level objective, e.g., 99% of requests under 300ms.

  20. 20. Which Metrics concept matches this description: "JVM stop-the-world event inflating tail latency"?

    • A. Garbage collection pause.correct
    • B. Baseline test.
    • C. Capacity.
    • D. P50 (median).

    Why: garbage collection pause: JVM stop-the-world event inflating tail latency.

Related Performance Testing topics