When analyzing collected data to determine the root cause of a problem in BIG-IP APM, what should be compared to identify discrepancies?

Question

Options

• AExpected vs. actual behaviors
• BNumber of concurrent users vs. licensed users
• CTotal session count vs. session timeout settings
• DApplication response times vs. user access times

• A
  79% (30)
• B
  3% (1)
• C
  5% (2)
• D
  13% (5)

Explanation

Comparing expected vs. actual behaviors is the foundation of root cause analysis - you define what the system should do, observe what it actually does, and the gap between them points directly to the fault. In BIG-IP APM troubleshooting, this means examining logs, session variables, policy results, and access reports to find where behavior deviates from your intended configuration. Options B, C, and D describe metrics that might indicate a problem exists (capacity limits, timeouts, latency), but they don't constitute a root cause analysis framework - they're symptoms, not a diagnostic method. Memory tip: Think "Expected vs. Actual = E.A. = Evidence Analysis" - root cause analysis is always about closing the gap between what should happen and what did happen.

No community discussion yet for this question.