Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise is architecting an automated data protection pipeline using Sensitive Data Protection (SDP) and Cloud Dataflow to sanitize transactional records before storing them in BigQuery. The solution must satisfy the following distinct workload requirements:
JOIN and aggregation operations on customer identifiers across multiple independent batch jobs and streaming runs. The tokens must be mathematically irreversible (one-way) to prevent sensitive identity leakage under any circumstance.Which combination of Sensitive Data Protection cryptographic transformations and key configurations should the security engineer implement?
This option proposes using Format-Preserving Encryption (FPE-FFX) with a transient cryptographic key for analytics workloads, and cryptographic hashing (CryptoHashConfig) with a Cloud KMS-wrapped key for the regulatory compliance auditing workflow.
This option utilizes Character Masking (CharacterMaskConfig) with character-skip rules for the analytics pipeline, and Deterministic Encryption (AES-SIV) configured with a transient key for the regulatory compliance pipeline.
# or *). Masking causes different raw customer IDs to collapse into identical masked strings (e.g., ###-##-1234), eliminating identifier cardinality and corrupting SQL joins and aggregation metrics.This configuration applies Deterministic Encryption (AES-SIV) configured with a context tweak for data analytics, alongside Format-Preserving Encryption (FPE-FFX) using an unwrapped raw key for the auditing workload.
Sensitive Data Protection provides cryptographic de-identification primitives designed to balance data privacy, referential integrity, and analytical utility. This solution combines one-way cryptographic hashing (CryptoHashConfig) for irreversible tokenization with deterministic encryption (CryptoDeterministicConfig using AES-SIV) for reversible pseudonymization, both backed by Cloud KMS-wrapped cryptographic keys (KmsWrappedCryptoKey).
JOIN and GROUP BY operations without ever being able to decrypt or re-identify the raw identifier.This architecture strictly enforces least-privilege token reversibility by utilizing irreversible hashing for standard analytics and authenticated AES-SIV deterministic encryption only for workflows that explicitly require re-identification. Utilizing Cloud KMS wrapping meets enterprise key management standards without exposing plaintext secrets in de-identification templates.
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