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.
A healthcare analytics platform ingests tabular patient data through a streaming ingestion pipeline into BigQuery for visualization in Looker dashboards. To comply with privacy regulations, you must configure Cloud Data Loss Prevention (Cloud DLP / Sensitive Data Protection) to conditionally sanitize incoming records.
Specifically, you need to configure a de-identification pipeline where:
PATIENT and FACTOID fields are inspected for PERSON_NAME infoTypes.[PERSON_NAME].AGE field is greater than 89.How should you structure the DeidentifyConfig for this ingestion pipeline?
InfoTypeTransformations using CryptoDeterministicConfig on PERSON_NAME and filter incoming messages in Pub/Sub using SQL filter expressions on the AGE attribute.CryptoDeterministicConfig performs deterministic tokenization/pseudonymization using cryptographic keys, allowing the same plaintext value to always yield the same ciphertext, and Pub/Sub message filtering routes messages based on subscription filter rules.
[PERSON_NAME]), not encrypting/tokenizing with a cryptographic key.CryptoDeterministicConfig requires managing key rings and crypto keys in Cloud KMS.The requirement was to generate consistent pseudonymized tokens for PERSON_NAME using encryption keys so analysts could perform joins across datasets without revealing identities.
Cloud DLP provides native row-level predicates (RecordCondition) specifically so developers do not need to build complex stream-splitting architectures just to apply conditional sanitization.
RecordTransformations with a FieldTransformation targeting the PATIENT and FACTOID fields, attach an infoTypeTransformations using ReplaceWithInfoTypeConfig, and attach a RecordCondition evaluating AGE greater than 89.This solution uses Cloud DLP's structured tabular de-identification capabilities within DeidentifyConfig, specifically using RecordTransformations and FieldTransformations with a RecordCondition.
FieldId entries for PATIENT and FACTOID within FieldTransformation ensures that de-identification inspection is scoped precisely to the relevant columns.infoTypeTransformations with PERSON_NAME and applying a primitive transformation of ReplaceWithInfoTypeConfig replaces matching personal names with the infoType label [PERSON_NAME].RecordCondition with a relational operator of GREATER_THAN on the AGE field (value 89) ensures the transformation executes only on rows meeting the compliance threshold while leaving others unaltered.Table objects without requiring unnesting or flat string concatenation.This approach directly leverages Cloud DLP's native conditional record evaluation without requiring custom conditional routing code in the ingestion pipeline, ensuring consistent policy enforcement directly at the data protection layer.
RecordTransformations with a FieldTransformation containing a CharacterMaskConfig on AGE, and define a RowCondition to drop rows matching PERSON_NAME.CharacterMaskConfig replaces individual characters in a string with a masking character (such as *), while dropping rows removes records entirely from the dataset.
CharacterMaskConfig to AGE obscures the age value rather than using age as a condition to sanitize PATIENT and FACTOID.PERSON_NAME is found deletes patient records instead of de-identifying them in-place with the infoType token.RecordCondition (with Condition and Expressions), not a configuration element called RowCondition for row dropping.[PERSON_NAME].The goal was to redact credit card digits or social security numbers with asterisks (****-****-****-1234) on specific columns and purge invalid records entirely.
When preparing datasets for visualization, preserving row structure and non-sensitive attributes while replacing sensitive findings with standardized infoType tags maintains dashboard usability while adhering to de-identification standards.
TransformationDetailsStorageConfig with a BucketingConfig on AGE and apply ReplaceWithInfoTypeConfig across all table columns globally inside an InspectConfig.TransformationDetailsStorageConfig is used to configure where transformation logs and metadata are stored (such as a BigQuery table), while BucketingConfig is used to categorize numerical or categorical data into predefined ranges (buckets).
ReplaceWithInfoTypeConfig belongs in DeidentifyConfig under primitive transformations, not inside InspectConfig.AGE > 89.InspectConfig specifies what infoTypes to find, not how to transform them.TransformationDetailsStorageConfig cannot execute de-identification rules.The scenario required logging de-identification metrics to a BigQuery audit table while generalizing continuous age values into discrete age brackets.
Confusing inspection rules with de-identification rules is a common mistake; InspectConfig finds sensitive findings, whereas DeidentifyConfig specifies how those findings are mutated or obfuscated.
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