Module 4: Investigating Application Performance Issues

Looking for ‘Observability in Google Cloud Module 4 Answers’?

In this post, I provide complete, accurate, and detailed explanations for the answers to Module 4: Investigating Application Performance Issues of Course 13: Observability in Google Cloud – Preparing for Google Cloud Certification: Cloud Security Engineer Professional Certificate.

Whether you’re preparing for quizzes or brushing up on your knowledge, these insights will help you master the concepts effectively. Let’s dive into the correct answers and detailed explanations for each question!

Quiz - Investigating Application Performance Issues

Graded Assignment

1. You have an SLO that states that 90% of your http requests need to respond in less than 100 ms. You want a report that compares latency for your last two versions. What tool would you use to most easily create this report?

  • Error Reporting
  • Logging
  • Trace ✅
  • Profiler

Explanation:
Cloud Trace helps you analyze request latency and compare performance between different versions of a service. It’s ideal for examining response times to ensure SLOs are met.

2. You deployed a new version of a service and all of a sudden significantly more instances are being created in your Kubernetes cluster. Your service scales when average CPU utilization is greater than 70%. What tool can help you investigate the problem?

  • Trace
  • Profiler
  • Logging ✅
  • Error Reporting

Explanation:
While Profiler helps identify inefficient code, Logs from Cloud Logging give you real-time insights into application behavior, CPU usage patterns, and Kubernetes scaling triggers. You can check the logs for sudden spikes, errors, or resource pressure that led to autoscaling.

So even though Profiler is useful, Cloud Logging is more direct for this scenario because it shows what triggered the scale-up.

3. Which profile signifies the amount of memory allocated in the heap of the program?

  • Heap ✅
  • Allocated heap
  • Wall time
  • CPU time

Explanation:
In the context of Cloud Profiler, the profile type that shows memory allocated and retained in the heap is simply called “Heap”.

  • “Allocated heap” is not the correct profile name in Profiler (even if it sounds technically valid).
  • “Heap” in Profiler shows current memory usage in the heap, which is what you need for analyzing memory behavior.

Related contents:

Module 2: Configuring Google Cloud Services for Observability
Module 3: Monitoring Google Cloud Network
Module 5: Optimizing the Costs for Google Cloud Observability

You might also like:

Course 1: Preparing for Your Professional Cloud Security Engineer Journey
Course 2: Google Cloud Fundamentals: Core Infrastructure
Course 3: Networking in Google Cloud: Fundamentals
Course 4: Networking in Google Cloud: Routing and Addressing
Course 5: Networking in Google Cloud: Network Architecture
Course 6: Networking in Google Cloud: Network Security
Course 7: Networking in Google Cloud: Load Balancing
Course 8: Networking in Google Cloud: Hybrid and Multicloud
Course 9: Managing Security in Google Cloud
Course 10: Security Best Practices in Google Cloud
Course 11: Mitigating Security Vulnerabilities on Google Cloud
Course 12: Logging and Monitoring in Google Cloud
Course 14: Hands-On Labs in Google Cloud for Security Engineers

Leave a Reply