Answer-first summary for fast verification
Answer: The service account associated with the Logging sink lacks the necessary permissions to access the Pub/Sub topic.
Option B is correct because the Logging sink's service account must have the appropriate permissions to write to the Pub/Sub topic. Without these permissions, logs cannot be routed to the topic. Option A is incorrect because Cloud Logging and Pub/Sub are global services, making regional differences irrelevant. Option C is incorrect as firewall rules do not affect traffic between Logging and Pub/Sub. Option D is incorrect because even if the logging filter was misconfigured, some logs would still appear in Pub/Sub. For more details, refer to [Google Cloud's documentation on exporting logs to Elasticsearch](https://cloud.google.com/architecture/exporting-stackdriver-logging-elasticsearch#create_a_sink_service) and [configuring log exports](https://cloud.google.com/logging/docs/export/configure_export_v2#errors_exporting_logs_to_cloud_pubsub).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A company utilizes a GCP organization with applications running across various GCP projects. These applications send logs to Cloud Logging. The company aims to analyze these logs using third-party software like Elasticsearch. Despite setting up a Logs sink to direct logs to a Pub/Sub topic, no logs are appearing in Elasticsearch. What could be the possible reason?
A
The Pub/Sub topic is located in a different region than the Logging Sink configuration.
B
The service account associated with the Logging sink lacks the necessary permissions to access the Pub/Sub topic.
C
A firewall rule is blocking egress traffic to the third-party software.
D
The logging filter was incorrectly configured.
No comments yet.