Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
Your organization operates a distributed multi-tier microservices application deployed across multiple Google Cloud projects. The services communicate over HTTP and use Envoy sidecar proxies configured within a service mesh to generate telemetry.
During performance troubleshooting, the operations team notices that requests spanning across project boundaries appear as disconnected, isolated spans in Cloud Trace rather than a single contiguous end-to-end distributed trace.
What should you do to ensure trace continuity across the different projects?
roles/cloudtrace.admin role to the Compute Engine default service accounts across all projects to enable automatic cross-project span federation.The roles/cloudtrace.admin IAM role grants full administrative permissions over Cloud Trace resources, allowing principals to manage trace configurations, sampling rates, and read/write trace data within a given project.
X-Cloud-Trace-Context), not because of permission failures. If IAM permissions were missing, spans would be dropped entirely rather than appearing as disconnected traces.roles/cloudtrace.agent role (roles/cloudtrace.agent) to write trace spans, making the administrative role unnecessarily broad and excessive.The sidecar proxies were receiving HTTP 403 Forbidden permission errors when attempting to post trace buffers to the Google Cloud Trace API endpoint.
X-Cloud-Trace-Context HTTP header across service calls, and verify each proxy runs with credentials for its respective project.Cloud Trace relies on context propagation to stitch individual operations (spans) across distributed architectures into a single coherent trace tree. In HTTP-based distributed environments, telemetry frameworks and sidecar proxies like Envoy use standardized tracking headers—specifically the X-Cloud-Trace-Context header—to pass trace identifiers, span identifiers, and trace flags between upstream callers and downstream callee services.

When a request traverses multiple Google Cloud projects:
X-Cloud-Trace-Context HTTP header in all downstream outbound requests. If an intermediary service drops this header, the downstream proxy assumes the call is a new root request, generating a new trace ID and breaking trace correlation.Preserving context headers directly addresses the mechanism used by Cloud Trace and service proxies to establish parent-child span relationships across projects without requiring extra networking infrastructure.
Internal Application Load Balancers (ALBs) are proxy-based regional Layer 7 load balancers that distribute HTTP and HTTPS traffic across backend VM instances, Google Kubernetes Engine pods, or serverless endpoints inside a Virtual Private Cloud (VPC).
You needed private Layer 7 traffic routing, path-based URL mapping, and SSL offloading across different VPCs connected via Private Service Connect.
Exporting telemetry to Cloud Storage involves batching log entries or raw text files via Cloud Logging log sinks for long-term archiving, compliance retention, or offline analytical processing using BigQuery.
trace.googleapis.com) or OpenTelemetry collectors, not by scanning static raw files dumped into Cloud Storage buckets.Your objective was to meet long-term compliance regulations requiring archival storage of raw access logs for multi-year audit requirements.
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