How to Securely Export Filtered Logs to an On-Prem SIEM?
Short answer
C Create a log sink for the relevant logs, send them to Pub/Sub, and use Dataflow to securely push the filtered stream to the on-premises SIEM.
Question
Key Takeaways
Tests secure log export architecture; the common trap is selecting log views or storage buckets instead of a filtered sink with a managed streaming pipeline.
Learn how to securely export a filtered subset of Google Cloud logs to an on-premises SIEM using log sinks, Pub/Sub, and Dataflow. This page establishes why this streaming architecture is the correct PCSE exam answer.
Common mistake: Candidates often select log views (B) assuming they handle external delivery, but log views only control IAM access within GCP and cannot stream data to on-premises systems.
Expert Analysis
Why the Answer Is Correct
Log sinks enable precise filtering at the collection layer, ensuring only relevant logs leave the environment and directly addressing the requirement to minimize data exposure. Publishing those filtered logs to Pub/Sub provides a secure, scalable, and real-time messaging layer that decouples collection from consumption. Dataflow then processes and reliably forwards the stream to the on-premises SIEM without requiring long-lived credentials or bulk archival storage.
Why the Other Options Are Wrong
Option A streams all logs to BigQuery first, violating the subset requirement and introducing unnecessary query costs and potential exposure before filtering occurs. Option B relies on log views, which only manage IAM permissions for viewing logs within GCP and lack native export capabilities to external systems. Option D recommends storing logs in Cloud Storage and distributing service account keys, which creates a high-severity credential leak risk and lacks real-time streaming.
Community Comment Notes
Several candidates debated between B and C, noting that log views simplify access control but fail to address the actual export mechanism. As BPzen highlighted, the sink filtering combined with Pub/Sub and Dataflow ensures only necessary data travels externally. Other voters acknowledged that while B feels simpler, it does not solve the external SIEM integration requirement.
Official Reference
- https://cloud.google.com/logging/docs/export/configure_export_v2
- https://cloud.google.com/pubsub/docs/overview
- https://cloud.google.com/dataflow/docs/guides/templates/provided-streaming#loggingexporter
These links open the official vendor documentation in a new tab.
Exam Strategy
Always map the requirement to the data flow first: filter at the source (sink), transport securely (Pub/Sub), and process/deliver reliably (Dataflow). Avoid options that recommend hardcoding credentials or over-collecting data before filtering.
Frequently Asked Questions
Why can't I use a log view to export logs to my SIEM?
Is Dataflow required to send logs to an external SIEM?
Community Votes
57% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 7 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 7
-
BPzen 👍 2 Answered CWhy C is Correct: Log Sink for Filtering: A log sink allows you to filter and export only the relevant logs, ensuring unnecessary data is not sent, which reduces the risk of data exposure. Pub/Sub for Delivery: Exporting logs to Pub/Sub enables real-time streaming of filtered logs to external systems. This ensures the SIEM receives logs promptly and securely. Dataflow for Transformation and Transfer: Use Dataflow to process and transform logs as needed before pushing them to the on-premises SIEM.
-
Popa 👍 1 Answered BOption C, does involve setting up multiple components (Pub/Sub, Dataflow, log sinks) and ensuring they are properly configured. This might add to the complexity of the setup. That being said, option B is still a strong choice because it provides a more straightforward approach to controlling and accessing the logs using log views and identity federation
-
irene062 👍 1 Answered BLog views let you grant a user access to only a subset of the logs stored in a log bucket. https://cloud.google.com/logging/docs/logs-views
-
KLei 👍 1 Answered CB: Defining a log view provides access control but does not facilitate exporting logs to an external SIEM effectively.
-
kalbd2212 👍 2going with C..
Show 2 more comments
-
MoAk 👍 1 Answered CAnswer C.
-
abdelrahman89 👍 1 Answered BAnswer B
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.