Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise organization is deploying Workload Identity Federation across multiple external continuous integration (CI/CD) platforms to access Google Cloud resources securely. The security team needs to establish a comprehensive security and auditing baseline for the federation lifecycle.
The implementation must satisfy two primary requirements:
Which configuration strategy should the security engineer implement?
This strategy establishes an end-to-end security architecture for Workload Identity Federation (WIF) by combining deep audit logging with strict administrative boundaries and immutable claim mappings.
sts.googleapis.com). Enabling Data Access audit logs ensures that every token exchange event—along with its mapped external attributes—is permanently captured.GenerateAccessToken are recorded in Identity and Access Management (IAM) API Data Access logs, providing an unbroken audit trail back to the originating external identity even when downstream resource APIs do not natively populate serviceAccountDelegationInfo.roles/iam.workloadIdentityPoolAdmin role, preventing unauthorized actors from inheriting iam.googleapis.com/workloadIdentityPoolProviders.update permissions from parent folders.This option bypasses Workload Identity Federation completely by issuing long-lived service account JSON keys, managing them in an external secrets manager (HashiCorp Vault), and rotating them with automated Cloud Functions.
The workloads operated in an isolated legacy environment that lacked support for OIDC/SAML token issuance and could not integrate with modern identity federation standards.
This option attempts to secure federation by relying on default Admin Activity audit logs, applying workforce identity pool session duration settings, and using email addresses as the primary subject attribute mapping.
The scenario focused exclusively on human employee single sign-on through Google Cloud console sessions using SAML/OIDC workforce identity pools.
This option grants developers the Owner (roles/owner) role over workload identity pool providers, sets the external subject attribute to the identity provider's issuer URL (iss), and enforces immutability on log export buckets using Bucket Lock.
iam.googleapis.com/workloadIdentityPoolProviders.update permission. Allowing developers or untrusted users to modify attribute mappings enables malicious actors to spoof identities or grant arbitrary workloads access to privileged service accounts.google.subject) to the general issuer URL treats all workloads from that external provider as the exact same identity, destroying granular non-repudiation and principal-level auditing.The goal was only to guarantee WORM (Write Once, Read Many) compliance for archived log objects in Cloud Storage without addressing identity federation security controls.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated