Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is designing an automated data ingestion pipeline to process transaction records before storing them in BigQuery for analytics. The incoming records include sensitive commercial and personally identifiable information (PII) with the following specific requirements:
Which combination of Sensitive Data Protection (Cloud DLP) de-identification transformations should the cloud architect specify in the de-identification template?
This option proposes using BigQuery Dynamic Data Masking via Data Catalog policy tags and direct Cloud KMS envelope encryption during ingestion instead of Sensitive Data Protection transformations.
All data was already safely stored in cleartext in BigQuery and the goal was to dynamically hide column values from specific IAM users without transforming source records prior to ingestion.
Sensitive Data Protection (formerly Cloud DLP) provides configurable de-identification transformations that allow organizations to obfuscate, tokenize, mask, or generalize sensitive data at scale across streaming and batch pipelines.
infoTypeTransformations configuration inspects the text using built-in detectors (such as EMAIL_ADDRESS and PHONE_NUMBER) and applies character masking to replace matching tokens with characters like # or *.This architecture accurately satisfies all operational and structural constraints. It avoids breaking downstream schema constraints on legacy applications while maintaining strong de-identification and risk-mitigation standards across structured and unstructured data formats.
This configuration applies one-way HMAC-SHA-256 hashing to the credit card numbers, character masking to the age column, and unconditional replacement to support notes.
**) either removes the value completely or invalidates numerical aggregation, whereas bucketing preserves statistical utility.Credit card numbers were never required to be recovered/decrypted and age values did not need to be retained as usable demographic reporting bins.
This option combines Deterministic Encryption (AES-SIV), date shifting, and cryptographic hashing (HMAC-SHA-256) within a Sensitive Data Protection transformation config.
infoTypeTransformations) attempts to hash the entire free-text comment block rather than detecting and masking embedded sensitive entities (emails and phone numbers).Downstream systems accepted variable-length base64 strings for credit card numbers, the age column was a birthdate timestamp requiring random offset shifts, and entire customer remarks required one-way cryptographic fingerprinting.
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