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 data platform ingests streaming customer interaction records and log files continuously into Cloud Storage, while also running batch analytical transformations in BigQuery. The security and compliance team has established the following requirements for sensitive data governance:
ACC-[0-9]{8}).Which architecture and configuration should the data engineering team implement using Sensitive Data Protection (Cloud DLP)?
This architecture leverages Sensitive Data Protection (Cloud DLP) core building blocks—Custom InfoTypes, StoredInfoTypes, Inspection Templates (InspectTemplate), and Finding Actions—to deliver scalable, centralized, and automated sensitive data discovery across diverse storage systems and streaming ingestion pipelines.
EMAIL_ADDRESS and PHONE_NUMBER) are native to the inspection engine and require no custom regex maintenance.CustomInfoType with a regular expression (regex) rule cleanly captures standardized organizational patterns such as ACC-[0-9]{8}.StoredInfoType configured with a LargeCustomDictionaryConfig referencing a file set in Cloud Storage indexes large term dictionaries efficiently for high-throughput matching.InspectTemplate decouples scanning rules from pipeline code. Any update made to the inspection template instantly propagates across Cloud Storage ingestion triggers, Dataflow pipelines, and BigQuery scheduled scans.StoredInfoType pre-indexes massive term lists, reducing inspection latency.Using centralized inspection templates with stored custom infoTypes avoids hardcoded rules in pipeline code, accommodates large-scale dictionary sizes, and natively outputs detailed audit trails directly to BigQuery without custom integration overhead.
This option combines Dataplex Auto Data Quality scans for rule verification on structured tables with Cloud Intrusion Detection System (Cloud IDS) network threat log export into Google Security Operations (SecOps).
InspectTemplate resources that can be embedded across real-time continuous ingestion pipelines.Your primary objective was monitoring network perimeters for intrusion attempts and ensuring that tabular data adheres to relational integrity constraints (such as non-null constraints or range checks).
This approach attempts to use BigQuery's native access control mechanisms (IAM column-level access control and policy tags) alongside custom SQL User-Defined Functions (UDFs) executed across BigQuery external tables to identify sensitive data.
Your datasets were already fully classified and you needed to restrict role-based querying access or dynamically mask specific existing columns (like masking all but the last 4 digits of a Social Security Number) in BigQuery tables.
This approach embeds complete detector definitions—including regular expressions and term lists—directly within each individual pipeline's API call configuration (InspectConfig) and relies on per-record synchronous API calls.
InspectConfig are intended only for small lists of words and phrases; they cannot scale to hold 500,000 terms due to API request size limits.You were performing lightweight, ad-hoc string inspection on a single microservice with a small static keyword list (fewer than a few dozen words) and only needed high-level alerting metrics rather than compliance audit storage.
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