Examkin

Soru

Zorluk: OrtaMonitoring, Logging, and Observability Integration

A financial services organization processes transactions using microservices on Google Cloud. To control operational expenses, the lead architect must reduce Cloud Logging storage ingestion costs. However, compliance mandates require retaining all security audit records and application error logs for seven years in BigQuery. Which architectural approach should you implement to satisfy both cost optimization and compliance log retention requirements?

  1. Create a Log Router sink that exports audit logs and logs with severity ERROR or higher to BigQuery, while setting an exclusion filter on the default log bucket for logs with severity below ERROR.Cevap
  2. B
    Configure an exclusion filter matching severity >= INFO across all log buckets to aggressively drop log volume across the entire organization.
  3. C
    Assign the primitive Owner role to the logging service account across all projects to allow it to dynamically delete log buckets when ingestion quotas are reached.
  4. D
    Rely strictly on project-level IAM permission boundaries to prevent developers from viewing verbose logs, avoiding the use of Log Router sinks or exclusion filters.

Cevap

Create a Log Router sink that exports audit logs and logs with severity ERROR or higher to BigQuery, while setting an exclusion filter on the default log bucket for logs with severity below ERROR.
The correct approach uses Cloud Logging Log Router sinks to selectively export required audit and error logs to BigQuery for long-term compliance storage, while configuring exclusion filters on the default bucket to prevent low-severity routine logs from accumulating ingestion costs.

Adım Adım Çözüm

1
Analyze compliance and retention requirements
Identified that audit logs and high-severity error logs must be preserved long-term in BigQuery.
Regulatory compliance mandates seven-year data retention for critical operational and audit events.
2
Analyze cost optimization requirements
Identified that lower-severity logs (such as DEBUG and INFO) generate high volume and should be excluded from storage ingestion.
Excluding routine low-severity logs prevents unnecessary Cloud Logging storage charges.
3
Configure Cloud Logging Log Router and exclusion filters
Established a targeted sink for BigQuery export and added selective exclusion filters on the log bucket.
Log Router sinks allow precise routing of filtered logs to external destinations like BigQuery, while bucket exclusion filters stop unwanted logs from incurring ingestion fees.

Anahtar Kavram

Monitoring, Logging, and Observability Integration
Bu soruyu puanla

Konular

Monitoring, Logging, and Observability Integration

Bu konudan daha fazla soru