Question 300
Which mechanism correctly explains Workload federation attribute restriction in this security case: Several external repositories share an OIDC issuer but only one repository may deploy production infrastructure?
Explanation
Correct Answer
The operative mechanism for Workload federation attribute restriction: Map repository and tenant claims into workload identity attributes and restrict acceptable principals with conditions. For this scenario (several external repositories share an oidc issuer but only one repository may deploy production infrastructure), verify that a token from the approved repository deploys while a different repository token is rejected.
Incorrect Answers
This describes how Short-lived service account tokens works instead: Use the Service Account Credentials API or supported impersonation flow to obtain bounded-lifetime access tokens. It is useful when a batch worker must acquire an identity that expires automatically after a narrow maintenance window, but it does not explain the selected Workload federation attribute restriction for the current requirement (several external repositories share an oidc issuer but only one repository may deploy production infrastructure).
This describes how Service account least-privilege bindings works instead: Grant the required predefined or custom role to the service account at the narrowest supported resource scope. It is useful when a notification service must publish messages to a selected pub/sub topic without administering subscriptions, but it does not explain the selected Workload federation attribute restriction for the current requirement (several external repositories share an oidc issuer but only one repository may deploy production infrastructure).
This describes how Disable service account key creation works instead: Use the appropriate organization policy constraint restricting service account key creation across the intended hierarchy. It is useful when a fleet migration has eliminated json keys and needs a preventative guardrail against their reintroduction, but it does not explain the selected Workload federation attribute restriction for the current requirement (several external repositories share an oidc issuer but only one repository may deploy production infrastructure).






Professional Cloud Security Engineer Practice Tests