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 preparing customer service datasets stored in Google Cloud to train a machine learning model for sentiment analysis. The datasets include structured customer identifier fields (such as customer email addresses) alongside unstructured freeform text fields (such as customer support notes and reviews).
The machine learning engineering team has specified the following requirements:
Which Sensitive Data Protection (SDP) architecture should you implement?
Sensitive data discovery is an automated profiling service within Sensitive Data Protection that continuously scans BigQuery tables, Cloud Storage buckets, and databases across an organization to generate statistical risk profiles, infoType classifications, and security posture metrics.
The primary goal was to obtain continuous visibility and high-level reporting of sensitive data assets across the enterprise without performing transformations.
Record suppression is a de-identification technique in Sensitive Data Protection where entire rows or records are omitted from the output dataset when specified conditions evaluate to true.
The objective was to discard corrupt, invalid, or extremely high-risk records entirely from a dataset where partial masking or anonymization is prohibited by strict compliance policies.
BigQuery column-level security uses taxonomy-based policy tags and Identity and Access Management (IAM) roles to restrict access to specific table columns based on user identity and group membership.
The organization wanted to restrict direct human querying of sensitive structured columns in BigQuery for production users while managing permissions via IAM.
Sensitive Data Protection (SDP) provides automated de-identification and transformation capabilities designed to sanitize structured and unstructured data before it is ingested by downstream workloads such as AI/ML model training pipelines. Using custom de-identification templates, SDP can apply field-level cryptographic pseudonymization (tokenization) as well as content-level inspection and masking on unstructured text.
email field replaces sensitive identifiers with consistent surrogate tokens. Because identical inputs generate identical surrogate tokens when using the same crypto key, the ML team can group, join, and aggregate records belonging to the same user without seeing the underlying email address.PHONE_NUMBER and US_SOCIAL_SECURITY_NUMBER) and applies masking transformations (e.g., replacing values with *** or surrogate tags) directly to detected sensitive text.
This solution strikes the optimal balance between data privacy and data utility. Pure redaction or record deletion would destroy the relational links required for customer-level sentiment modeling, whereas tokenization preserves structural analytical value while eliminating cleartext PII risk.
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