Question 350
The security team implements Default service account privilege hardening for this requirement: Newly created workloads must not automatically inherit broad project roles from legacy default service account settings. Which result best demonstrates successful enforcement?
Explanation
Correct Answer
This directly validates Default service account privilege hardening: New workload identities have no inherited editor role and require deliberate least-privilege grants. The observed result is consistent with the implemented mechanism, explicitly disable automatic privileged defaults where applicable and minimize or remove legacy bindings on default accounts, for the requirement (newly created workloads must not automatically inherit broad project roles from legacy default service account settings).
Incorrect Answers
This observation verifies Dedicated workload service account: The export operates with the new principal and fails when it touches unrelated resources. That validates a different security control used when a scheduled data export currently runs under an overly privileged default compute engine service account. It does not establish Default service account privilege hardening for this scenario (newly created workloads must not automatically inherit broad project roles from legacy default service account settings).
This observation verifies Disable service account key creation: A test attempt to create a service account key is rejected while federated authentication remains possible. 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 Default service account privilege hardening for this scenario (newly created workloads must not automatically inherit broad project roles from legacy default service account settings).
This observation verifies Workload Identity Federation for external CI: A release run exchanges its trusted OIDC identity for temporary access without a JSON key. That validates a different security control used when a github actions pipeline needs access to a deployment project without storing a downloaded service account key. It does not establish Default service account privilege hardening for this scenario (newly created workloads must not automatically inherit broad project roles from legacy default service account settings).






Professional Cloud Security Engineer Practice Tests