Which THREE of the following are benefits of using a SIEM integrated with Cloud native logs?
Ingesting logs from AWS, Azure and GCP into one SIEM correlates events across providers, giving a single pane of glass instead of per-provider consoles. This satisfies the benefit of centralised visibility spanning multiple cloud providers.
Why this answer
Option A is correct because a SIEM integrated with cloud-native logs ingests log streams from AWS CloudTrail, Azure Activity Logs, and GCP Cloud Audit Logs into one platform, giving centralized visibility across multiple cloud providers. Option B is correct because the SIEM stores normalized events in a long-term index, enabling advanced threat hunting queries and analytics over historical data that native cloud consoles cannot retain or query at scale. Option D is correct because the SIEM's correlation engine joins events from different security layers (identity, network, workload, and control-plane logs) into a single detection timeline, surfacing multi-stage attacks that isolated tools would miss.
Option C is not a SIEM function; guest OS kernel patching is performed by configuration-management or patch-management tools such as AWS Systems Manager Patch Manager or Azure Update Manager. Option E is not a SIEM function either; creating cloud accounts is an identity/provisioning task handled by services like AWS Organizations or Azure Management Groups, not by log analytics.
Exam trap
The trap is that candidates may select options that sound like general cloud automation benefits (patching, account creation) because they conflate 'cloud integration' with 'cloud management' — but the exam expects you to recognize that SIEM benefits are strictly about visibility, analytics, and correlation, not infrastructure provisioning or OS maintenance.