Question 990
A reviewer challenges the choice of Sensitive Data Protection format-preserving encryption when a legacy validation pipeline requires fixed-length account numbers but must not store readable identifiers. Which underlying operation justifies the choice?
Explanation
Correct Answer
The operative mechanism for Sensitive Data Protection format-preserving encryption: Apply a supported format-preserving encryption transform with managed key controls and documented transformation settings. For this scenario (a legacy validation pipeline requires fixed-length account numbers but must not store readable identifiers), verify that encrypted values match the expected format and unauthorized consumers cannot reverse them.
Incorrect Answers
This describes how Secret Manager rotation version control works instead: Add a new secret version and update consumers to an approved version alias or version reference. It is useful when a compromised api token needs replacement while maintaining a controlled rollback window, but it does not explain the selected Sensitive Data Protection format-preserving encryption for the current requirement (a legacy validation pipeline requires fixed-length account numbers but must not store readable identifiers).
This describes how Secret Manager runtime secret retrieval works instead: Store the secret in Secret Manager and grant narrow secret-version access to the runtime principal. It is useful when a scheduled batch requires a database credential accessible only to its specific service account, but it does not explain the selected Sensitive Data Protection format-preserving encryption for the current requirement (a legacy validation pipeline requires fixed-length account numbers but must not store readable identifiers).
This describes how BigQuery row-level security works instead: Define supported row access policies for appropriate principals and row-filter predicates. It is useful when a multinational dataset must restrict employees to rows for their employing subsidiary, but it does not explain the selected Sensitive Data Protection format-preserving encryption for the current requirement (a legacy validation pipeline requires fixed-length account numbers but must not store readable identifiers).






Professional Cloud Security Engineer Practice Tests