PCDOE Implementing service monitoring strategies Practice Question

A developer wants to view logs from all pods in a GKE namespace in real time. Which command-line tool should they use?

⚠ Common exam trap

Google Cloud often tests the distinction between historical log retrieval (`gcloud logging read`) and real-time streaming (`gcloud logging tail`), and the trap here is that candidates mistakenly choose `kubectl logs` because they are familiar with its `-f` flag, but they overlook that it cannot aggregate logs from all pods in a namespace without complex scripting.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

gcloud logging tail

The `gcloud logging tail` command streams logs in real time from all pods in a GKE namespace, as it directly queries the Cloud Logging API for live log entries. This is the correct tool for real-time log streaming across multiple pods, unlike `kubectl logs` which only shows logs from a single pod or a limited set. The command supports filtering by resource labels, such as `--filter="resource.labels.namespace_name=NAMESPACE"`, to scope the output to a specific namespace.

Answer analysis

Option-by-option breakdown

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

✗
gcloud logging read
Why it's wrong here
This reads historical logs, not real-time.
✗
Cloud Console Logs Viewer
Why it's wrong here
Logs Viewer is for querying historical logs, not real-time streaming.
✗
kubectl logs --tail=100
Why it's wrong here
This tails logs from a single pod, not all pods.
✓
gcloud logging tail
Why this is correct
This streams logs in real time across resources.

Go deeper

PCDOE Implementing service monitoring strategies Practice Question

Why each option matters

Option-by-option breakdown

Related to this question