MENU
On a snapshot flow map, which three metrics indicate why the snapshot might have been taken? (Choose three.)
A snapshot flow map presents execution-specific timing information that helps explain why AppDynamics captured that particular transaction instance. The relevant metrics are Thread Blocking Time, Execution Time, and Asynchronous Activity Processing Time.
Execution Time shows the elapsed processing time for the transaction segment and helps determine whether the request exceeded slow or very slow transaction thresholds. Thread Blocking Time identifies time during which the executing thread was blocked or waiting, potentially because of lock contention, synchronization, resource availability, or another thread-related delay. A substantial blocking value can explain why an otherwise ordinary code path produced a slow snapshot.
Asynchronous Activity Processing Time represents time consumed by asynchronous work associated with the transaction, such as executor tasks, callbacks, or background processing correlated with the originating request. Excessive asynchronous processing can materially increase end-to-end completion time and trigger snapshot collection.
Tier Response Time and Node Response Time are aggregated performance metrics across multiple transactions. They provide useful operational context but do not directly describe the timing characteristics of one captured transaction execution.
Relevant CAAPA Study Guide topics include Transaction Snapshots, Snapshot Flow Maps, Execution Time, Thread Blocking, Asynchronous Transaction Tracking, and Slow Transaction Diagnostics.