MENU
Your application's performance in Google Cloud has degraded since the last release. You suspect that downstream dependencies might be causing some requests to take longer to complete. You need to investigate the issue with your application to determine the cause. What should you do?
Suggested Answer: A
Get Premium Professional Cloud DevOps Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Comprehensive and Detailed
Google Cloud Trace is specifically designed to analyze request latency and identify performance bottlenecks across services. Since the issue is related to slow performance after a new release, the best approach is to use Cloud Trace to:
Visualize request latency across services
Pinpoint slow dependencies affecting response time
Analyze performance trends over time
Why not other options?
B (Error Reporting) Focuses on uncaught exceptions and crashes, not latency issues.
C (Cloud Profiler) Helps with CPU and memory analysis, not request tracing.
D (Prometheus for Cloud Monitoring) Useful for metrics collection, but not ideal for debugging specific request latency issues.
Official Reference:
36 comments · newest first
GA
Galen
10 months ago
Wait, I didn't know Cloud Trace could help with this!
IR
Iraida
10 months ago
C sounds interesting, but does it really help with latency issues?
NE
Nelida
11 months ago
D? Really? That seems overkill for just performance issues.
KI
Kirk
11 months ago
I think B is more useful for catching errors, not performance.
PR
Precious
11 months ago
A is the way to go for tracing requests!
JE
Jesus
11 months ago
I vaguely recall something about Prometheus being useful for monitoring, but I don't think it's specifically for tracing request performance like Cloud Trace.
WY
Wynell
11 months ago
I practiced a similar question where Cloud Profiler was mentioned. It might help with understanding resource usage, but I'm not convinced it's the best choice here.
DE
Devora
12 months ago
I'm not entirely sure, but I think Error Reporting is more about catching exceptions rather than performance issues.
VI
Viola
12 months ago
I remember studying about Cloud Trace and how it helps in tracking request latency. It seems like a good option for identifying slow dependencies.
NI
Nilsa
1 year ago
I'm leaning towards option D, Google Cloud Managed Service for Prometheus. That could provide a comprehensive monitoring solution to help us understand the application's behavior and dependencies.
MA
Maurine
1 year ago
Configuring Cloud Profiler sounds like a good strategy to me. That should give us a detailed view of the application's performance and help pinpoint the problem areas.
LE
Leandro
1 year ago
Hmm, I'm a bit unsure about this one. I'm wondering if Error Reporting might be a better option to help identify the root cause of the performance issues.
AL
Alfred
1 year ago
I think the key here is to investigate the downstream dependencies, so I'd go with option A to configure Cloud Trace and get a better understanding of the application's performance.
AB
Abel
2 years ago
I heard option C is like having a personal trainer for your application. It'll whip your app into shape in no time!
JA
Javier
1 year ago
D) Configure Google Cloud Managed Service for Prometheus in your application.
HI
Hildred
1 year ago
C) Configure Cloud Profiler in your application.
JI
Jina
1 year ago
B) Configure Error Reporting in your application.
AN
Anjelica
1 year ago
A) Configure Cloud Trace in your application.
RY
Ryan
1 year ago
D) Configure Google Cloud Managed Service for Prometheus in your application.
LU
Luther
1 year ago
C) Configure Cloud Profiler in your application.
MA
Magda
1 year ago
B) Configure Error Reporting in your application.
EL
Eladia
1 year ago
A) Configure Cloud Trace in your application.
RO
Robt
2 years ago
Option B is the best choice here. Error Reporting will give you the juicy details on what's going wrong with your app. Plus, it's like having a personal therapist for your application.
LI
Ling
2 years ago
I believe Error Reporting could also be useful to track any errors that are impacting performance.
ET
Ettie
2 years ago
Dude, option D is where it's at! Managed Service for Prometheus is like having a personal genie for your monitoring needs.
EL
Elvis
2 years ago
Nah, I'd go with option A. Cloud Trace is like a crystal ball for your app's performance issues. You can see exactly where the slowdowns are happening.
TE
Telma
1 year ago
Let's go with Cloud Trace then. It seems like the most effective option for investigating the issue.
KA
Kasandra
1 year ago
Let's go with Cloud Trace then. It seems like the best option for investigating the issue.
ER
Erick
1 year ago
I agree, Cloud Trace is a powerful tool for diagnosing performance problems.
YV
Yvonne
2 years ago
I agree, Cloud Trace is a powerful tool for diagnosing performance problems.
KA
Kate
2 years ago
Option A sounds like a good choice. Cloud Trace can help pinpoint the performance issues.
DE
Derick
2 years ago
Option A sounds like the best choice. Cloud Trace can help pinpoint the performance issues.
BE
Becky
2 years ago
I think configuring Cloud Profiler might also be helpful to analyze the performance bottlenecks.
QU
Quentin
2 years ago
I think option C is the way to go. Cloud Profiler can really help you pinpoint the performance bottlenecks in your application.
MO
Mohammad
2 years ago
I agree with Naomi, Cloud Trace can help us pinpoint the slow requests.
NA
Naomi
2 years ago
I think we should configure Cloud Trace to trace the requests.