Practice Test 1 | Google Cloud Certified Professional Cloud Architect | Dumps | Mock Test

Correct Answer B

Explanation

A – Set timeouts on your application so that you can fail requests faster – This won’t be able to tell you directly where the bottleneck is.

B (Correct Answer) – Instrument your application with Operations Suite (formerly Stackdriver) Trace to break down the request latencies at each microservice. This is exactly Operations Suite (formerly Stackdriver) Trace comes to play.

C – Send custom metrics for each of your requests to Operations Suite (formerly Stackdriver) Monitoring – without knowing where the bottleneck is beforehand, it’s not easy, if not impossible, to setup custom metrics to capture the latency causes. Besides, the question itself is about to find where the latency/bottleneck exists.

D – Use Operations Suite (formerly Stackdriver) Monitoring to look for insights that show when your API latencies are high – this could tell you when the API call latency reaching to certain threshold/criteria but can hardly tell where the root causes is without additional setup and analysis.

Reference Resources

Operations Suite (formerly Stackdriver) Trace can help you answer the following questions: https://cloud.google.com/trace/docs/overview

·         How long does it take my application to handle a given request?

·         Why is it taking my application so long to handle a request?

·         Why do some of my requests take longer than others?

·         What is the overall latency of requests to my application?

·         Has latency for my application increased or decreased over time?

·         What can I do to reduce application latency?

“As micro-services become more popular, the cross-application tracing provided by Operations Suite (formerly Stackdriver) Trace becomes essential in pinpointing the root cause of latency issues.”