Question 490
The audit reviewer will not accept a configuration screenshot of Sensitive Data Protection format-preserving encryption. Which observable test result proves the intended control works for this case: A legacy validation pipeline requires fixed-length account numbers but must not store readable identifiers?
Explanation
Correct Answer
This directly validates Sensitive Data Protection format-preserving encryption: Encrypted values match the expected format and unauthorized consumers cannot reverse them. The observed result is consistent with the implemented mechanism, apply a supported format-preserving encryption transform with managed key controls and documented transformation settings, for the requirement (a legacy validation pipeline requires fixed-length account numbers but must not store readable identifiers).
Incorrect Answers
This observation verifies Secret Manager runtime secret retrieval: The service reads the approved secret version at runtime and image scans show no embedded token. That validates a different security control used when a cloud run api needs a partner token that must not appear in the container image. It does not establish Sensitive Data Protection format-preserving encryption for this scenario (a legacy validation pipeline requires fixed-length account numbers but must not store readable identifiers).
This observation verifies Cloud SQL IAM database authentication: The service obtains an authorized IAM database login and shared credentials are not embedded in code. That validates a different security control used when a cloud service should connect to a supported cloud sql database without keeping a reusable database password in source code. It does not establish Sensitive Data Protection format-preserving encryption for this scenario (a legacy validation pipeline requires fixed-length account numbers but must not store readable identifiers).
This observation verifies Cloud Storage uniform bucket-level access: Object ACL changes no longer create new access outside the governed IAM policy. That validates a different security control used when a storage bucket has conflicting object acls that complicate consistent organization-wide iam control. It does not establish Sensitive Data Protection format-preserving encryption for this scenario (a legacy validation pipeline requires fixed-length account numbers but must not store readable identifiers).






Professional Cloud Security Engineer Practice Tests