At a hotel, an analyst has four records from last night's guest traffic and must pick the one that is transaction data rather than session data. Which record is transaction data?
Select an answer to reveal the explanation.
Short Explanation
A receipt lists the order, while a trip log only says the cab moved. You want the HTTP method, host, and URL when the record has to be transaction data rather than a session summary. The trap is choosing addresses with byte counts, a weekly chart, or a disk-image hash.
Full Explanation
Session data describes a conversation: who talked, how much moved, and how long it lasted. Transaction data describes the application action inside that conversation. For one guest web request, the transaction record is The HTTP method, the host header, and the URL recorded for one guest request. Those fields say what was requested, not merely that two addresses exchanged bytes. Source address, destination address, byte count, and duration for one conversation is the session summary, and that is the contrast this question draws. A weekly chart of total bytes moved across the hotel guest wireless network is statistical data, an aggregate over time, not one application action. A cryptographic hash of a full laptop disk image taken at the front desk identifies a disk image and is neither a web transaction nor a session. Exam caveat: a flow's byte count does not become transaction data merely because the flow carried web traffic. The transaction is the method, host, and URL, or a similar application action. Operational check: open the web record and confirm the method, host, and URL are present, and keep the flow record beside it when you also need size and duration.