Cloud Trace for latency analysis in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Trace Span Latency Calculation

You have a trace with three spans: Span A starts at 0ms and ends at 50ms, Span B starts at 10ms and ends at 30ms, and Span C starts at 35ms and ends at 45ms. What is the total latency reported by Cloud Trace for this trace?

A 30 milliseconds

B 40 milliseconds

C 60 milliseconds

D 50 milliseconds

💡 Hint

Think about the overall start and end time of the entire trace, not just individual spans.

Cloud Trace calculates total latency as the difference between the earliest start time and the latest end time of all spans in the trace. Here, the earliest start is 0ms (Span A) and the latest end is 50ms (Span A), so total latency is 50 milliseconds.

❓ Architecture

intermediate

Choosing Trace Sampling Rate for Latency Analysis

You want to analyze latency spikes in a high-traffic web application using Cloud Trace. Which sampling strategy best balances cost and capturing latency spikes?

A Sample only requests that exceed a latency threshold

B Sample a fixed small percentage of requests randomly

C Sample 100% of all requests to capture every latency spike

D Do not sample any requests to save cost

💡 Hint

Consider how to capture important slow requests without overwhelming data volume.

Sampling only requests that exceed a latency threshold captures relevant latency spikes while reducing cost and data volume compared to sampling all requests.

❓ security

advanced

Securing Trace Data Access

Your team uses Cloud Trace to analyze latency but wants to restrict access to trace data containing sensitive user information. Which IAM role assignment best enforces least privilege for trace data access?

A Assign roles/cloudtrace.agent to all developers

B Assign roles/editor to all team members for full project access

C Assign roles/cloudtrace.viewer only to users who need to view trace data

D Assign roles/owner to the team lead for trace data access

💡 Hint

Least privilege means giving only the permissions needed to perform a task.

roles/cloudtrace.viewer allows read-only access to trace data, limiting exposure. roles/cloudtrace.agent allows writing traces but not necessarily viewing. roles/editor and roles/owner grant broad permissions beyond trace data.

❓ Configuration

advanced

Configuring Custom Trace Attributes for Latency Analysis

You want to add a custom attribute named 'user_region' to all your trace spans to analyze latency by region. Which configuration step is required to ensure this attribute appears in Cloud Trace?

A Add 'user_region' as a label in your application code when creating spans

B Enable 'user_region' in the Cloud Trace console settings

C Create a Cloud Logging sink to export 'user_region' attributes

D Set 'user_region' as an environment variable on your VM instances

💡 Hint

Custom attributes must be added where spans are created.

Custom trace attributes like 'user_region' must be added as labels in the application code when creating or updating spans. Console settings or environment variables do not automatically add attributes to spans.

✅ Best Practice

expert

Optimizing Trace Data Retention and Cost

Your organization wants to keep detailed latency traces for 30 days but minimize storage costs. Which approach best achieves this goal using Cloud Trace features?

A Keep all trace data in Cloud Trace indefinitely with no export

B Export trace data to Cloud Storage with lifecycle rules to delete after 30 days

C Disable trace data collection after 30 days

D Manually delete trace data daily from Cloud Trace

💡 Hint

Think about exporting data to cheaper storage with automatic deletion.

Exporting trace data to Cloud Storage allows applying lifecycle management policies to automatically delete data after 30 days, reducing costs. Keeping data indefinitely or manual deletion is inefficient. Disabling collection stops new data but does not manage existing data.