Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
A DevOps team is centralizing application and access audit logs into BigQuery to satisfy strict data protection regulations (such as GDPR and HIPAA). The log management design must satisfy the following access and compliance requirements:
Which strategy should the DevOps team implement in BigQuery to meet these requirements?
Assured Workloads enforces compliance controls and data residency boundaries by restricting resource creation and support personnel access to specific geographic regions (such as US-only or EU-only regions).
The primary goal was strictly enforcing hardware-level data residency and sovereign boundary controls across cloud infrastructure rather than controlling granular query visibility inside a table.
BigQuery Data Policies and Row Access Policies are fine-grained security controls built directly into BigQuery. Column-level data masking policies control how sensitive column data is displayed to different principals (such as masking via hash or null values), while row access policies act as an inline security filter determining which rows are returned to a user.
DATA_MASKING_POLICY with masking expressions like SHA256 or ALWAYS_NULL ensures DevOps engineers only see obfuscated sensitive log data.RAW_DATA_ACCESS_POLICY on the same column policy allows them to inspect unmasked raw logs without duplicating tables.CREATE ROW ACCESS POLICY with a FILTER USING (region = ...) statement ensures principals can only view rows corresponding to their assigned geographic boundary.Native BigQuery data policies and row-level access control enforce data masking and residency filtering simultaneously on a single centralized dataset, avoiding the cost, complexity, and synchronization drift of managing multiple filtered tables or custom export pipelines.
Authorized views allow users to query data from a view without having direct access to the underlying tables. The bigquery.filteredDataViewer role is an internal, system-managed role utilized by BigQuery when row access policies are created.
bigquery.filteredDataViewer manually through IAM; it must only be granted automatically through Row Access Policies.WHERE clauses for every combination of region and masking level requires maintaining numerous view definitions rather than applying centralized column and row policies.Row-level security and column-level data policies were unavailable and legacy SQL views were required to isolate access across different consumer groups.
Ingestion-time Sensitive Data Protection (DLP) de-identification permanently transforms or tokenizes incoming log streams using predefined templates before the data is written to long-term storage.
All users, including compliance officers, were strictly prohibited from retaining or accessing raw PII under any circumstance, and no row-level regional segmentation was required.
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 Validated