Which option best contrasts log aggregation with log correlation as activities supported by a modern monitoring platform?
- AAggregation rewrites raw log records so that sensitive fields are redacted before storage, while correlation forwards the redacted records to analysts over encrypted channels.
- BAggregation signs each log entry with the source's private key, while correlation verifies those signatures before any rule evaluation can run on the platform.
- CAggregation runs only on the originating endpoint and ships compressed archives nightly, while correlation runs only inside cloud SaaS platforms over the same archives.
- DAggregation collects and centralises log records from many sources into a common store, while correlation analyses relationships between those records to identify patterns of interest. Correct
Why A is wrong: Field redaction is a data protection or tokenisation concern, not the definition of aggregation. Correlation is not a forwarding activity, so the contrast misrepresents both terms.
Why B is wrong: Digital signing of log entries is a log integrity concern handled by specific transport or storage features, not the defining work of aggregation. Correlation does not depend on signature verification.
Why C is wrong: Aggregation routinely uses near real-time collectors, not nightly archives, and correlation is not restricted to SaaS environments. The geography described is not part of either definition.
Why D is correct: This is the standard contrast: aggregation is the collection and centralisation step, and correlation is the analytical step that links related events across sources and time to detect meaningful activity.