Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your microservices application running on Google Kubernetes Engine (GKE) is experiencing high p99 latency spikes during peak hours. The application communicates internally with a Cloud SQL database and externally with a third-party payment gateway via an Internal Application Load Balancer and Cloud NAT.
You need to distinguish whether the root cause of the latency bottleneck is caused by internal application processing, internal network round-trip time (RTT), or external service dependencies.
Which observability strategy should you implement?
VPC Flow Logs record network flow samples sent and received by VM instances and GKE nodes, capturing network 5-tuples, packet counts, byte counts, and connection durations.
The goal was strictly to audit network traffic volume, detect top-talker IP addresses, or analyze inter-subnet bandwidth consumption at the VPC level.
Cloud Profiler continuously samples CPU, heap, and thread usage in application code to identify intensive functions. Dataflow system lag metrics measure processing latency for streaming and batch pipelines managed by Cloud Dataflow.
You were optimizing a heavy streaming analytics pipeline in Cloud Dataflow and needed to identify CPU-intensive transformations or stuck pipeline steps.
Using tcpdump on Kubernetes nodes captures low-level raw network packets at the network interface level to troubleshoot ARP discovery, NAT translation issues, and packet drops.
You were diagnosing bare-metal ingress networking failures, such as MetalLB ARP advertisement issues or Dataplane V2 DNAT encapsulation errors.
Cloud Trace with OpenTelemetry instrumentation provides end-to-end distributed tracing across microservices, breaking down request execution paths into granular parent and child spans. Combining this with Cloud Monitoring load balancer metrics and Cloud Logging allows DevOps teams to observe the entire lifecycle of a request.
Cloud Trace combined with load balancer latency metrics directly isolates each segment of a distributed transaction. It clearly separates network transport delays from internal computation and third-party response waits, offering the quickest path to root-cause identification without introducing heavy infrastructure overhead.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated