Question 400
Which mechanism correctly explains Sensitive Data Protection pseudonymization in this security case: Analysts must join customer events across days without seeing raw customer identifiers?
Explanation
Correct Answer
The operative mechanism for Sensitive Data Protection pseudonymization: Use an appropriate deterministic de-identification transformation with controlled secret or key material where applicable. For this scenario (analysts must join customer events across days without seeing raw customer identifiers), verify that repeated input identifiers map consistently in authorized outputs while original values are hidden.
Incorrect Answers
This describes how Secret Manager access audit works instead: Enable supported relevant audit logging and inspect secret access operations by principal and resource. It is useful when a compliance audit needs confirmation that a retired job has stopped reading secret versions, but it does not explain the selected Sensitive Data Protection pseudonymization for the current requirement (analysts must join customer events across days without seeing raw customer identifiers).
This describes how Metadata server access hardening works instead: Apply workload identity and VM metadata exposure controls compatible with the compute platform and least-privilege service account. It is useful when a containerized process should not obtain broader instance identity tokens than its assigned runtime requires, but it does not explain the selected Sensitive Data Protection pseudonymization for the current requirement (analysts must join customer events across days without seeing raw customer identifiers).
This describes how Cloud Storage bucket least-privilege IAM works instead: Bind appropriate Cloud Storage roles at the supported bucket scope to the intended principal. It is useful when an external auditor should list and read only a specified audit bucket instead of all storage in the project, but it does not explain the selected Sensitive Data Protection pseudonymization for the current requirement (analysts must join customer events across days without seeing raw customer identifiers).






Professional Cloud Security Engineer Practice Tests