You are working as a SOC analyst for a cloud-based service provider that relies on...

In PostgreSQL, the configuration parameter that enables writing logs to files via the logging collector process islog_collector. When enabled, PostgreSQL can collect stderr output from backend processes and route it into log files, which is foundational for centralized log shipping and retention. From a SOC standpoint, turning on log collection is necessary but not sufficient: you typically also need to configure what gets logged (authentication failures, statement duration thresholds for slow queries, and error verbosity), define log line prefixes for consistent parsing, and set rotation/retention to meet operational and compliance needs. However, the question specifically asks which parameter should be enabled to ensure PostgreSQL captures and stores logs, and log_collector is the correct parameter name and casing. The other options include incorrect naming or formatting. Once enabled, the SOC team can forward PostgreSQL logs to the SIEM to correlate database activity with identity, endpoint, and network signals—critical for detecting brute force attempts, suspicious administrative actions, and anomalous query behavior.