An enterprise organization is updating its observability architecture for workloads running on Compute Engine instances. The team requires centralized collection of application and system telemetry for real-time operational monitoring, as well as long-term retention of critical security and error logs in BigQuery for security analytics. Operational costs must be optimized without accidentally discarding high-severity audit and application error logs. Which TWO actions should the Cloud Architect recommend to satisfy these requirements? (Select TWO)
- Install and configure the Google Cloud Ops Agent on all Compute Engine virtual machines to collect unified system logs and metrics for Cloud Logging and Cloud Monitoring.Answer
- BAssign the primitive Owner role to the Compute Engine default service account to ensure unrestricted access to write telemetry to Cloud Logging and Cloud Monitoring.
- Configure an aggregated Log Router sink with an inclusion filter targeting severity levels of ERROR or higher to stream critical log entries to BigQuery.Answer
- DApply a global Cloud Logging exclusion filter for log entries matching severity level WARNING or higher to reduce total log ingestion costs.
- ERely strictly on project-level IAM permission checks to prevent unauthorized log data exfiltration without configuring VPC Service Controls perimeters.
Answer
The Cloud Architect should install the Google Cloud Ops Agent on all Compute Engine VMs to collect telemetry and create an aggregated Log Router sink with an inclusion filter targeting severity levels of ERROR or higher to stream critical log entries to BigQuery.
Deploying the Google Cloud Ops Agent ensures comprehensive collection of system logs and performance metrics from Compute Engine instances into Cloud Logging and Monitoring. Creating a Log Router sink with explicit inclusion filters targeting ERROR or higher severity levels ensures that high-value logs are securely exported to BigQuery for security analytics without incurring storage costs for routine low-severity logs.
Step-by-Step Solution
Key Concept
Monitoring, Logging, and Observability Integration