An enterprise architecture team is establishing an observability framework for custom applications running on Google Cloud Compute Engine instances across multiple production projects. They need to collect both system metrics and application logs, and aggregate critical logs into a centralized log repository in a dedicated security project. Which TWO actions should you take to meet these requirements using Google Cloud recommended practices? (Select TWO)
- Install and configure the Ops Agent on the Compute Engine instances to collect and transmit system metrics and application logs to Cloud Logging and Cloud Monitoring.Cevap
- BAssign the primitive Owner role (roles/owner) to the instance service account to grant complete access for writing telemetry and logs across the organization.
- Configure an aggregated Log Router sink at the organization or folder level to route log entries from all production projects to a central Cloud Logging log bucket.Cevap
- DCreate an aggregate log exclusion filter that drops all ERROR and AUDIT severity logs to prevent log ingestion costs from exceeding budget limits.
- ERely exclusively on standard IAM permissions to control log access without configuring VPC Service Controls around log destination buckets.
Cevap
The two correct actions are to install the Ops Agent on the Compute Engine instances to collect metrics and logs, and to set up an aggregated Log Router sink at the organization level to direct logs to a central log bucket.
Installing the Ops Agent ensures complete telemetry ingestion (system metrics and application logs) from Compute Engine instances. Using an aggregated Log Router sink at the organization or folder level efficiently collects and centralizes logs across multiple projects into a designated security log bucket.
Adım Adım Çözüm
Anahtar Kavram
Centralized observability integration using the Google Cloud Ops Agent and Aggregated Log Router sinks.