The correct answer is B. Per connection logging generates a log entry for each connection in a session, while per session logging reduces log volume by generating one log for the overall session. This distinction matters in high-volume environments because connection-level logging can provide granular visibility but increases log volume and indexing/storage load. Session-level logging is more efficient but provides less per-connection detail. Option A is incorrect because the concept is not limited to only URL Filtering in the manner stated. Option C is unrelated and confuses application identification and Content Awareness with the log-generation mode. Option D reverses the meaning. Administrators choose tracking/log behavior based on investigation requirements, compliance needs, and performance
/storage considerations. For ordinary access rules, per-session logging may be sufficient; for sensitive or heavily investigated traffic, per-connection logging may be preferable. Reference topics: Tracking Options, per-connection logging, per-session logging, SmartConsole Logs & Events.