Examkin

Soru

Zorluk: ZorMonitoring, Logging, and Observability Integration

An enterprise e-commerce platform processes high-volume transaction traffic across Google Kubernetes Engine (GKE) clusters and Compute Engine instance groups. The operations team must design a centralized observability and logging strategy that satisfies three core requirements: route high-volume HTTP 200 OK access logs to Cloud Storage for cost-effective long-term compliance storage, stream application exception logs and high-severity errors to BigQuery for real-time security and operational analytics, and guarantee that no critical system errors or security audit logs are accidentally omitted during ingestion filter tuning. Which architectural design best meets these requirements while preventing operational log loss?

  1. Configure Log Router sinks with fine-grained inclusion filters that direct audit logs and high-severity errors to BigQuery, while creating a separate Cloud Storage sink with explicit exclusion filters scoped strictly to HTTP 200 OK payload statuses.Cevap
  2. B
    Apply a broad log exclusion filter with severity thresholds set to drop all web service log entries at the project `_Default` log bucket level, relying on Cloud Monitoring custom metrics to detect application failures.
  3. C
    Grant the primitive Owner role to service accounts running custom log collection daemons on GKE nodes so they can dynamically bypass Log Router filters and write directly to destination storage buckets.
  4. D
    Configure Log Router sinks to export all logs to external Cloud Storage buckets across project boundaries relying solely on IAM destination permissions, without establishing VPC Service Controls security perimeters.

Cevap

The optimal architecture configures Cloud Logging Log Router sinks with fine-grained inclusion filters to route audit and error logs to BigQuery, alongside a dedicated sink to Cloud Storage using narrow exclusion filters specifically targeted at low-severity HTTP access logs.
Configuring Cloud Logging Log Router sinks with specific inclusion filters for audit and error logs combined with targeted exclusion filters for low-severity HTTP access logs fulfills all analytical and compliance requirements while protecting against accidental loss of operational visibility.

Adım Adım Çözüm

1
Analyze logging ingestion and destination requirements
Identified the need for dual export destinations: BigQuery for real-time analytics and Cloud Storage for long-term compliance storage.
Different log types require different retention, query latency, and cost profiles.
2
Evaluate Log Router exclusion and inclusion filter designs
Determined that exclusion filters must be strictly scoped to specific benign payload attributes (such as HTTP 200 status codes).
Overbroad exclusion filters risk dropping critical high-severity application errors or required audit logs.
3
Select the optimal GCP recommended pattern
Leveraged native GCP Log Router sinks with explicit inclusion and narrow exclusion rules.
Provides scalable, managed log routing without security risks or unvalidated log drops.

Anahtar Kavram

Cloud Logging Log Router Sinks and Exclusion Filters
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Monitoring, Logging, and Observability Integration

Bu konudan daha fazla soru