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 establishing baseline authentication security controls across its Cloud Identity and Google Cloud environment. The security engineering team needs to enforce hardened authentication and recovery policies for privileged accounts (super administrators) while maintaining standard policies for general workforce users.
Specifically, the implementation must achieve the following requirements:
Which configuration strategy should the security engineer implement in the Google Admin console?
This option proposes using Workload Identity Federation with encrypted SAML tokens and assigning the roles/iam.serviceAccountTokenCreator IAM role to allow administrators to impersonate service accounts for access management.
The organization needed to allow software applications running in an external cloud provider to authenticate directly to Google Cloud APIs securely without managing long-lived service account keys.
This solution establishes a structured identity governance model in Cloud Identity by isolating privileged super administrator accounts into a dedicated Organizational Unit (OU). By applying targeted policies to this OU, administrators can mandate hardware security keys (such as Titan Security Keys) for 2-Step Verification (2SV) and restrict insecure self-service account recovery channels.
Isolating privileged identities into an administrative OU is the Google Cloud standard architecture for enforcing elevated controls. Applying FIDO2/Titan Security Key enforcement exclusively to this OU guarantees maximum identity assurance for privileged accounts while preventing account takeovers via legacy recovery mechanisms.
This configuration applies a uniform, global security posture across the entire organization by leaving all accounts in the root Organizational Unit (OU) and permitting telecommunication-based second factors like SMS and voice verification codes alongside automated email-based self-service recovery.
The objective was to implement a low-friction, baseline MFA requirement across low-risk standard accounts where hardware security keys were not available and granular OU segmentation was explicitly avoided.
This option involves running Policy Analyzer queries to inspect IAM allow policies across the resource hierarchy and setting up automated 24-hour rotation for OAuth client ID secrets.
The primary goal was auditing which IAM principals hold administrative permissions across organization resources and mitigating application impersonation risks by cycling OAuth application credentials.
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