How to Securely Store and Analyze Location Data in Google Cloud?
Your organization uses Google Cloud to process large amounts of location data for analysis and visualization. The location data is potentially sensitive. You must design a solution that allows storing and processing the location data securely, minimizing data exposure risks, and adhering to both regulatory guidelines and your organization's internal data residency policies. What should you do?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests matching workload requirements (analysis and visualization) with the appropriate managed service while enforcing data residency and encryption controls.
This question tests secure data residency and access control for large-scale analytics workloads using Google Cloud. It establishes that BigQuery with region-specific configuration, row-level security, and CMEK is the correct architecture for compliant location data analysis.
Candidates often select regional Cloud Storage because it emphasizes residency and encryption, but overlook that the primary workload is large-scale analysis and visualization.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
BigQuery is purpose-built for processing and visualizing massive datasets efficiently. Configuring the dataset in a specified region directly satisfies data residency mandates, while authorized views and row-level security provide fine-grained geographic access controls. Pairing this with CMEK ensures encryption keys remain within the approved jurisdiction, fully meeting security and compliance requirements.Why the Other Options Are Wrong
Option A relies on compute-level restrictions and metadata labels, which lack granular access enforcement and are ill-suited for analytical workloads. Option B proposes global storage buckets, which explicitly violate data residency policies, and misapplies DLP as an access control mechanism rather than a scanning tool. Option C provides solid storage security but fails to address the explicit requirement for data analysis and visualization, making it an incomplete architectural match.Community Comment Notes
Learners consistently identified the keywords "analysis and visualization" as the deciding factor, correctly steering them toward BigQuery. Several candidates initially considered regional storage or DLP but recognized that the analytical workload requirement overrides pure object storage solutions. As noted by multiple community members, the workload type dictates the service selection before security controls are layered on.Official Reference
Exam Strategy
Always map the core workload description to the optimal managed service first; "analysis and visualization" signals BigQuery over generic object storage. Then layer compliance controls like region scoping, IAM conditions, and CMEK to satisfy residency and security mandates.
Frequently Asked Questions
Why isn't regional Cloud Storage sufficient for this workload?
Cloud Storage excels at object retention, but the prompt explicitly requires large-scale analysis and visualization, which BigQuery handles natively with SQL and built-in BI tools.
How does BigQuery enforce geographic access restrictions?
Row-level security and authorized views filter query results based on user attributes or IP/location contexts, preventing unauthorized geographic data exposure.