Question 690
The audit reviewer will not accept a configuration screenshot of Workload federation attribute restriction. Which observable test result proves the intended control works for this case: A third-party CI tenant is trusted for staging but must not impersonate the production service account?
Explanation
Correct Answer
This directly validates Workload federation attribute restriction: Staging claims cannot acquire the production service account identity despite using the same identity provider. The observed result is consistent with the implemented mechanism, map repository and tenant claims into workload identity attributes and restrict acceptable principals with conditions, for the requirement (a third-party ci tenant is trusted for staging but must not impersonate the production service account).
Incorrect Answers
This observation verifies Disable service account key creation: A new project inherits the key-creation restriction even when a project editor requests a key. That validates a different security control used when the organization wants to prevent developers from producing new long-lived downloadable service account keys. It does not establish Workload federation attribute restriction for this scenario (a third-party ci tenant is trusted for staging but must not impersonate the production service account).
This observation verifies Service account least-privilege bindings: Publishing succeeds on the authorized topic while subscription administration is denied. That validates a different security control used when a cloud run processor only reads one cloud storage bucket but currently has broad project editor access. It does not establish Workload federation attribute restriction for this scenario (a third-party ci tenant is trusted for staging but must not impersonate the production service account).
This observation verifies Short-lived service account tokens: A previously issued batch token expires and cannot be extended without new authorization. That validates a different security control used when a troubleshooting script requires temporary google cloud api credentials and should not carry a permanent secret. It does not establish Workload federation attribute restriction for this scenario (a third-party ci tenant is trusted for staging but must not impersonate the production service account).






Professional Cloud Security Engineer Practice Tests