Cloud Digital Leader Why Cloud Technology Can Transform Business Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Cloud Audit Logs

  Why it's wrong here

  Cloud Audit Logs are narrow in scope: they capture administrative activity and access events within Google Cloud resources, such as changes to IAM permissions, bucket creations, or service account usage. They are generated by Google Cloud's own services and cannot ingest AWS or Azure audit trails, making them unsuitable as a centralized multi-cloud logging repository. While they are a useful component of security monitoring, they lack the vendor-neutral ingestion capability required for aggregating logs from multiple public clouds.

• ✗

  Cloud Console

  Why it's wrong here

  Cloud Console is the web-based management interface for Google Cloud, providing a GUI to view resources, deploy GCP services, and inspect logs through the built-in Logs Explorer. However, it is purely a user-interface layer and not an autonomous log aggregation service; it does not collect, index, or store logs by itself. Moreover, it offers no API or agent framework to pull logs from AWS or Azure, so it cannot serve as a cross-cloud log sink. At best, it provides a convenient way to interact with Cloud Logging's data, but it is not the underlying service that aggregates logs.

• ✗

  Cloud Monitoring

  Why it's wrong here

  Cloud Monitoring is an observability tool designed for time-series metrics, uptime checks, and alerting policies, not for ingesting raw log messages. It can pull metric data from AWS and Azure via API integrations, but that data is numerical telemetry (e.g., CPU utilization, request latency), not unstructured application logs. While Cloud Monitoring can derive metric data from logs through log-based metrics, that is a downstream processing feature—it does not aggregate, store, or provide a searchable interface for multi-cloud raw logs. Therefore, it is the wrong choice for a centralized log aggregation platform.

• ✓

  Cloud Logging

  Why this is correct

  Cloud Logging is the correct answer because it is a fully managed, real-time log aggregation service capable of ingesting logs from any source, including AWS and Azure, via the Logging API, Fluent Bit agents, or SDK integrations. It accepts structured and unstructured logs, applies indexes for queryability, and supports exports to BigQuery, Pub/Sub, or cloud storage for long-term archiving. In a multi-cloud environment, you can install an agent on AWS EC2 or Azure VMs to forward logs to a centralized sink, giving you a single Logs Explorer to search across all clouds. This directly fulfills the requirement of aggregating logs from multiple public clouds.

Go deeper

Related to this question