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.

Practice

1. What is the main purpose of Cloud Logging in Google Cloud Platform?

easy

A. To store large files in the cloud

B. To create virtual machines automatically

C. To manage user permissions and roles

D. To collect and display logs from cloud resources in one place

Solution

1. Step 1: Understand Cloud Logging's role

   Cloud Logging collects logs from various cloud resources and shows them centrally.

2. Step 2: Compare options with this role

   Only To collect and display logs from cloud resources in one place describes collecting and displaying logs; others describe unrelated services.

3. Final Answer:

   To collect and display logs from cloud resources in one place -> Option D

4. Quick Check:

   Cloud Logging = centralized log collection [OK]

Hint: Cloud Logging is about logs, not VMs or storage [OK]

Common Mistakes:

• Confusing logging with VM creation
• Thinking it manages user permissions
• Mixing it up with storage services

2. Which of the following is the correct gcloud command to read logs from Cloud Logging?

easy

A. gcloud logging read "resource.type=gae_app"

B. gcloud compute instances list

C. gcloud storage buckets create my-bucket

D. gcloud iam roles describe admin

Solution

1. Step 1: Identify the command for reading logs

   The command to read logs uses 'gcloud logging read' followed by a filter.

2. Step 2: Check each option

   gcloud logging read "resource.type=gae_app" uses 'gcloud logging read' correctly; others relate to compute, storage, or IAM.

3. Final Answer:

   gcloud logging read "resource.type=gae_app" -> Option A

4. Quick Check:

   Log reading command starts with 'gcloud logging read' [OK]

Hint: Look for 'logging read' in the command to find logs [OK]

Common Mistakes:

• Using compute or storage commands instead of logging
• Missing the 'read' keyword after 'logging'
• Confusing IAM commands with logging commands

3. What will be the output of this command?
gcloud logging read "severity=ERROR" --limit 2 --format json

medium

A. A JSON list of the 2 most recent ERROR severity log entries

B. A list of all logs regardless of severity

C. An error message about invalid command syntax

D. A list of 2 logs with severity INFO

Solution

1. Step 1: Understand the command parameters

   The command reads logs filtered by severity=ERROR, limits output to 2 entries, and formats output as JSON.

2. Step 2: Analyze expected output

   It returns a JSON list of the 2 most recent logs with ERROR severity, not all logs or INFO logs.

3. Final Answer:

   A JSON list of the 2 most recent ERROR severity log entries -> Option A

4. Quick Check:

   Filter + limit + JSON format = filtered JSON logs [OK]

Hint: Filter by severity and limit controls output count [OK]

Common Mistakes:

• Ignoring the severity filter
• Expecting all logs instead of limited ones
• Confusing severity levels

4. You run this command but get no output:
gcloud logging read "severity=CRITICAL" --limit 5
What is the most likely reason?

medium

A. The command syntax is incorrect

B. There are no logs with severity CRITICAL in the selected time range

C. The gcloud tool is not installed

D. The limit flag cannot be used with severity filters

Solution

1. Step 1: Check command syntax

   The command syntax is correct; 'gcloud logging read' supports severity filters and limit.

2. Step 2: Consider reasons for no output

   No output usually means no matching logs exist for severity CRITICAL in the default time range.

3. Final Answer:

   There are no logs with severity CRITICAL in the selected time range -> Option B

4. Quick Check:

   No output often means no matching logs [OK]

Hint: No output? Check if logs exist for that severity [OK]

Common Mistakes:

• Assuming syntax error without checking
• Thinking limit flag is invalid with filters
• Ignoring that no logs might exist

5. You want to monitor your app's logs for errors and send alerts only when ERROR or higher severity logs appear. Which Cloud Logging feature should you use?

hard

A. Create a VM instance to process logs locally

B. Use Cloud Storage to save logs and check manually

C. Create a log-based metric with a filter for severity >= ERROR and set up an alerting policy

D. Run gcloud logging read manually every hour

Solution

1. Step 1: Identify monitoring and alerting needs

   You want automatic alerts on ERROR or higher severity logs.

2. Step 2: Match features to needs

   Log-based metrics with filters and alerting policies automate monitoring and alerts.

3. Step 3: Evaluate other options

   Manual checks or storing logs without alerts do not meet the requirement.

4. Final Answer:

   Create a log-based metric with a filter for severity >= ERROR and set up an alerting policy -> Option C

5. Quick Check:

   Log-based metrics + alerts = automated error monitoring [OK]

Hint: Use log-based metrics and alerts for automatic error notifications [OK]

Common Mistakes:

• Relying on manual log checks
• Using storage without alerting
• Creating unrelated VM instances