Cloud Logging overview in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of Cloud Logging in GCP?

Cloud Logging collects and stores logs from various sources in Google Cloud Platform. What is its main purpose?

A To collect, store, and analyze logs from applications and services for monitoring and troubleshooting.

B To provide a database service for storing structured data.

C To deploy and manage virtual machines automatically.

D To manage user identities and access permissions.

💡 Hint

Think about what logs are used for in software systems.

Cloud Logging is designed to collect and manage logs to help monitor and troubleshoot applications and services.

💻 Command Output

intermediate

What is the output of this gcloud logging command?

Run the following command to list log entries for a project:

gcloud logging read "resource.type=gae_app" --limit 1 --format json

What type of output will this command produce?

A A YAML formatted list of all resources.

B A plain text list of all log names in the project.

C An error message about missing permissions.

D A JSON array with one log entry object related to App Engine.

💡 Hint

The command uses --format json and --limit 1 with a filter on resource type.

The command reads one log entry matching the filter and outputs it as a JSON array.

❓ Configuration

advanced

Which configuration snippet correctly creates a sink to export logs to a Cloud Storage bucket?

You want to export logs from Cloud Logging to a Cloud Storage bucket named my-logs-bucket. Which YAML snippet correctly defines this sink?

A

name: my-logs-sink
destination: bigquery.googleapis.com/projects/my-project/datasets/logs
filter: "severity>=ERROR"

B

name: my-logs-sink
destination: gs://my-logs-bucket
filter: "severity>=ERROR"

C

name: my-logs-sink
destination: pubsub.googleapis.com/projects/my-project/topics/logs-topic
filter: "severity>=ERROR"

D

name: my-logs-sink
destination: storage.googleapis.com/my-logs-bucket
filter: "severity>=ERROR"

💡 Hint

Cloud Storage destinations use the gs:// prefix.

To export logs to Cloud Storage, the destination must start with gs:// followed by the bucket name.

❓ Troubleshoot

advanced

Why does a Cloud Logging sink fail to export logs to BigQuery?

You created a sink to export logs to a BigQuery dataset, but no logs appear in the dataset. What is the most likely cause?

A The sink filter is too broad and includes all logs.

B The logs are not generated by any resource.

C The sink's service account lacks BigQuery dataset write permissions.

D The Cloud Storage bucket is not in the same region as BigQuery.

💡 Hint

Check permissions for the sink's service account on the destination.

If the sink's service account does not have write permissions on the BigQuery dataset, logs cannot be exported.

🔀 Workflow

expert

Order the steps to create and verify a Cloud Logging sink exporting logs to Pub/Sub

Arrange the steps in the correct order to create a sink that exports logs to a Pub/Sub topic and verify it works.

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about resource creation, permission granting, and verification order.

You must first create the Pub/Sub topic, then create the sink pointing to it, grant permissions, and finally verify logs arrive.