Explain logging and monitoring concepts in MDC3?

• A. Ignore logs for performance.
• B. Only monitor system uptime.
• C. Logging replaces security controls.
• D. Logging/monitoring collect and analyze logs/metrics; enable observability, anomaly detection, and compliance in MDC3.

Answer: (D)

Logging and monitoring are about turning raw events and measurements into visibility. Logs record what happened, when, where, and by whom; metrics summarize system health and performance over time. In MDC3, collecting these logs and metrics from applications, services, and infrastructure, then storing and analyzing them, lets you see how the system behaves, detect unusual patterns, and provide auditable evidence for compliance. This combination—logs, metrics, and traces—gives observability, so you can investigate incidents, pinpoint root causes, and understand end-to-end flows. Anomaly detection uses expected behavior to flag deviations, while compliance is supported through retained, secure, and auditable logs and activity records.

Ignoring logs removes crucial visibility and hampers incident response. Focusing only on uptime ignores performance issues and security events. And logging does not replace security controls; it supports detection and verification but isn’t a substitute for preventive measures.