GCP-ACE - Ensuring the successful operation of a cloud solution - Section 3.4

Monitor and log a cloud solution using Google Cloud Observability, including creating Cloud Monitoring alerts and custom metrics, configuring audit logs and VPC Flow Logs, configuring log buckets, sinks, and routers, viewing and filtering Cloud Logging, and deploying the Ops Agent and Managed Service for Prometheus.

Use Google Cloud Observability to keep a solution healthy: create Cloud Monitoring alerting policies on resource metrics and ingest custom metrics, configure audit logs, VPC Flow Logs, and firewall logs, and route logs with log sinks and buckets to BigQuery or external systems. Deploy the Ops Agent to collect VM metrics and logs, use Managed Service for Prometheus, and view and filter logs in Cloud Logging to investigate an issue.

Cloud MonitoringCloud LoggingVPC Flow LogsLog sinksOps AgentManaged Service for Prometheus

Practice question for this objective

Free sampleEnsuring the successful operation of a cloud solutionmedium

A new engineer is unsure how Cloud Logging and Cloud Monitoring divide responsibilities within Google Cloud Observability. Which statement correctly distinguishes the two services?

  • ACloud Monitoring stores raw log text for querying, while Cloud Logging charts numeric metrics and manages notification channels.
  • BBoth services store metrics only, and log data must instead be exported to an external system for retention and search.
  • CCloud Logging stores and queries log entries, while Cloud Monitoring collects metrics and evaluates alerting policies on them. Correct
  • DCloud Logging generates metric time series directly, while Cloud Monitoring merely renders those series on dashboards without alerting.
Distinguish Cloud Logging as the log storage and query service from Cloud Monitoring as the metrics and alerting service. Within Google Cloud Observability the two products are complementary: Cloud Logging ingests, retains, and lets you query log entries, whereas Cloud Monitoring collects metric time series and evaluates alerting policies to trigger notifications.

Why A is wrong: This reverses the two roles; storing and querying logs belongs to Cloud Logging, and charting metrics with notification channels belongs to Cloud Monitoring.

Why B is wrong: It is tempting because sinks can export logs, but Cloud Logging retains and searches log data natively, so external export is optional rather than required.

Why C is correct: This correctly splits the suite: Cloud Logging handles ingestion, storage, and querying of log entries, while Cloud Monitoring gathers metric time series and runs alerting policies over them.

Why D is wrong: Cloud Logging can derive log-based metrics, but describing it as the primary metrics engine and stripping alerting from Cloud Monitoring misstates each service's core role.

See more GCP-ACE practice questions, answers explained.

More in this domain

Back to all Ensuring the successful operation of a cloud solution objectives, or the GCP-ACE cert hub.

Examworthy is not affiliated with or endorsed by Google Cloud. Original, blueprint-aligned practice material only.