Diagnostic sessions are critical for capturing snapshots. Which scenario is best suited for this approach?

Question

Options

• ABefore deploying new features
• BWhen a performance degradation is detected
• CDuring scheduled maintenance
• DAfter resolving an issue

• A
  12% (4)
• B
  79% (27)
• C
  6% (2)
• D
  3% (1)

Explanation

Diagnostic sessions are designed to capture system state at the moment a problem is occurring, making option B the correct choice - when performance degradation is detected, a diagnostic snapshot preserves the exact conditions (memory usage, thread states, slow queries, etc.) needed to pinpoint the root cause. Option A is incorrect because pre-deployment captures baseline state for comparison, not diagnosis of an active problem. Option C (scheduled maintenance) is planned downtime, not a reactive diagnostic trigger. Option D is wrong because capturing a snapshot after resolution means the problem conditions are gone, making the data useless for diagnosis.

Memory tip: Think of a diagnostic session like a crime scene photo - you need it while the crime is happening, not before or after.

No community discussion yet for this question.