Question 1070
A reviewer challenges the choice of Disable service account key creation when a fleet migration has eliminated json keys and needs a preventative guardrail against their reintroduction. Which underlying operation justifies the choice?
Explanation
Correct Answer
The operative mechanism for Disable service account key creation: Use the appropriate organization policy constraint restricting service account key creation across the intended hierarchy. For this scenario (a fleet migration has eliminated json keys and needs a preventative guardrail against their reintroduction), verify that a new project inherits the key-creation restriction even when a project editor requests a key.
Incorrect Answers
This describes how Workload federation attribute restriction works instead: Map repository and tenant claims into workload identity attributes and restrict acceptable principals with conditions. It is useful when a third-party ci tenant is trusted for staging but must not impersonate the production service account, but it does not explain the selected Disable service account key creation for the current requirement (a fleet migration has eliminated json keys and needs a preventative guardrail against their reintroduction).
This describes how Workload Identity Federation for external CI works instead: Configure workload identity pools and a trusted OIDC provider with scoped attribute mappings and IAM bindings. It is useful when a multi-cloud workload in another provider needs short-lived access to a google cloud bucket, but it does not explain the selected Disable service account key creation for the current requirement (a fleet migration has eliminated json keys and needs a preventative guardrail against their reintroduction).
This describes how Service account impersonation role separation works instead: Separate service account Token Creator or Workload Identity User permissions from administration and read-only audit grants. It is useful when a monitoring analyst needs to inspect service account usage without minting credentials on its behalf, but it does not explain the selected Disable service account key creation for the current requirement (a fleet migration has eliminated json keys and needs a preventative guardrail against their reintroduction).






Professional Cloud Security Engineer Practice Tests