Examkin

Question

Difficulty: MediumMonitoring and Logging

An organization requires a centralized observability strategy across multiple Google Cloud projects. The compliance team mandates aggregating all Cloud Audit Logs from every project into a single Cloud Storage bucket for long-term retention. Additionally, the operations team needs to collect guest operating system memory utilization telemetry from a fleet of Compute Engine instances and trigger alerts if memory usage exceeds threshold limits. Which TWO steps should the cloud engineer implement to satisfy these operational requirements? (Select TWO.)

  1. Create an aggregated Log Router sink at the organization level with an inclusion filter for audit logs, designating the centralized Cloud Storage bucket as the sink destination.Answer
  2. Install the Google Cloud Ops Agent on all Compute Engine instances and configure a Cloud Monitoring alerting policy based on the agent's memory utilization metric.Answer
  3. C
    Install the legacy Stackdriver Monitoring agent on the Compute Engine virtual machines to capture guest OS memory metrics.
  4. D
    Create individual Log Router sinks in each project and grant the Primitive Owner role to the sink writer service account on the destination Cloud Storage bucket.

Answer

To meet both compliance and telemetry requirements, the engineer must create an aggregated Log Router sink at the organization level targeting the centralized Cloud Storage bucket, and install the Google Cloud Ops Agent on Compute Engine instances to collect memory metrics for alerting policies.
The solution requires two distinct actions: organization-level log routing and guest OS metric collection. An aggregated Log Router sink configured at the organization node automatically captures audit logs from all underlying projects into a single Cloud Storage bucket. Meanwhile, guest OS memory usage is not visible to the hypervisor by default, so installing the Google Cloud Ops Agent on the virtual machines is required to send memory metrics to Cloud Monitoring for alerting.

Step-by-Step Solution

1
Configure centralized audit log aggregation
An aggregated Log Router sink at the organization scope captures audit logs from all current and future projects and routes them to Cloud Storage.
Organization-level aggregated sinks remove the maintenance overhead of configuring individual sinks per project.
2
Deploy telemetry agent for OS-level metrics
The Ops Agent collects system metrics such as RAM utilization from inside the virtual machine operating system.
Hypervisor-level telemetry cannot inspect guest memory usage without an in-guest agent.
3
Set up alerting policies in Cloud Monitoring
Alerting policies monitor the Ops Agent memory utilization metric and trigger notifications when the specified threshold is exceeded.
Cloud Monitoring alerting policies actively notify operations teams when telemetry metrics cross predefined operational boundaries.

Key Concept

Centralized Log Router Sinks and Ops Agent Telemetry Collection
Rate this question

Topics

Monitoring and Logging

More questions from this topic