Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
An enterprise is centralizing sensitive customer transaction data from multiple business units into a shared BigQuery data warehouse. The data engineering and security teams must implement a robust security architecture that satisfies the following requirements:
Which combination of Google Cloud security mechanisms should the team implement?
This architecture combines VPC Service Controls, BigQuery Row-Level Security (RLS), and BigQuery Column-Level Security using Policy Tags and Dynamic Data Masking to establish end-to-end context-aware security and fine-grained data access.
WHERE region = 'APAC') directly to the base table based on user group membership (GRANT TO), avoiding the operational maintenance and scaling limits of creating separate tables or hundreds of authorized views.roles/datacatalog.categoryFineGrainedReader) role can view unmasked cleartext values.This approach aligns with Google Cloud security best practices by enforcing the principle of least privilege, zero-trust network boundaries, and scalable fine-grained access controls without administrative overhead.
This approach attempts to use standard VPC firewall rules for network containment, physical materialized subset tables partitioned/clustered per region for row segmentation, and AEAD client-side encryption for column protection.
The scenario required hosting data in isolated tenant-specific regional storage environments where raw records must remain cryptographically unreadable even to host database administrators.
This configuration uses Private Google Access with Cloud Armor, tenant-specific Authorized Views, and dataset-level CMEK (Customer-Managed Encryption Keys) in Cloud KMS.
The primary requirements were meeting cryptographic key lifecycle compliance (such as key rotation in Cloud HSM) and protecting external web applications from Layer 7 attacks.
This option proposes using IAM Conditions on dataset bindings, exporting filtered data extracts to separate Cloud Storage buckets, and using Sensitive Data Protection (Cloud DLP) to permanently drop sensitive columns.
The compliance policy strictly mandated that sensitive PII must never reside in Google Cloud and that downstream analysts only needed static, irreversibly anonymized CSV exports.
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