Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Google Cloud Certified Professional Cloud Security Engineer · Google Cloud
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
option A, C,D all supports referential integrity, however, D is not reversible. Choosing between A and C, I would go for A, because Format-Preservation Encryption provides fewer security guarantees compared to deterministic encryption. Unless there is strict requirement on the length and character set preservation, FPE is not recommended. And this question does not mention this requirement, therefore, answer should be A.
C. Format-preserving encryption Justification Based on Documentation: https://cloud.google.com/dlp/docs/transformations-reference#transformation_methods According to the Google Cloud DLP guidelines, format-preserving encryption (FPE) transforms sensitive data while keeping its original format. This is essential for working with structured data where you need to maintain the integrity of data types (e.g., keeping a credit score as a numeric field) while ensuring security through encryption. The ability to join user information in the banking app with credit score data while preserving the structure and format of the data is critical, especially since the goal is to analyze the data without exposing sensitive information.
Why C. Format-preserving encryption is correct: Format-preserving encryption (FPE) encrypts data while preserving its format (e.g., encrypting a credit card number would still result in a string with the same length and structure). It ensures that data relationships and referential integrity across systems remain intact. FPE is supported by Google Cloud DLP for tokenization tasks. Why not the other options: A. Deterministic encryption: Deterministic encryption ensures that the same plaintext always encrypts to the same ciphertext, which can preserve referential integrity. However, it doesn't inherently maintain the format of the original data, which might be a requirement in this case.