nerdexam
Splunk

SPLK-1002 · Question #166

When using the transaction command, how are evicted transactions identified?

The correct answer is A. Closed_txn field is set to o, or false. When the transaction command processes events, a transaction can be 'evicted' (forcibly closed) before it meets its defined end condition - for example, due to memory pressure or reaching the maxevents or maxpause limits. These incomplete/evicted transactions are flagged by…

Correlating Events

Question

When using the transaction command, how are evicted transactions identified?

Options

  • AClosed_txn field is set to o, or false.
  • BMax_txn field is set to O, or false.
  • CTxn_field is set to 1, or true.
  • Dopen_txn field is set to 1, or true.

How the community answered

(22 responses)
  • A
    91% (20)
  • C
    5% (1)
  • D
    5% (1)

Explanation

When the transaction command processes events, a transaction can be 'evicted' (forcibly closed) before it meets its defined end condition - for example, due to memory pressure or reaching the maxevents or maxpause limits. These incomplete/evicted transactions are flagged by setting the closed_txn field to 0 (false), indicating the transaction did not close cleanly. A properly completed transaction has closed_txn=1 (true). This field allows analysts to filter out or separately handle incomplete transaction groups in their analysis.

Topics

#transaction command#evicted transactions#Closed_txn field#event correlation

Community Discussion

No community discussion yet for this question.

Full SPLK-1002 Practice