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.
A global enterprise is integrating an external third-party Identity Provider (IdP) with Google Cloud to manage access for external security analysts. The security team has defined several key requirements:
Which identity and access architecture should the security engineer implement?
Cloud Identity accounts are managed directory entities representing corporate users. Access bindings attach context-aware access levels to groups to control resource access based on device state, IP address, and other environmental attributes.
OR logical evaluation, which can inadvertently weaken security perimeters.The organization wanted to manage full identity lifecycles natively inside Google Workspace or Cloud Identity Premium and enforce strict endpoint device policies.
Metadata-based SSH keys are public cryptographic keys stored in project or instance metadata (ssh-keys) that allow users to authenticate directly to Compute Engine Linux guest environments.
Compute Instance Admin at the project level gives overly broad standing access instead of scoped, task-based permissions.compute.requireOsLogin) to tie server access directly to IAM lifecycles.An isolated non-production environment without IAM directory connectivity required simple, unmanaged public-key SSH authentication for legacy servers.
google.subject and google.groups to IdP assertions, grant IAM roles directly to federated principal sets, and use Privileged Access Manager (PAM) for time-bound privilege elevation.Workforce Identity Federation allows third-party identity providers (such as Okta, Microsoft Entra ID, or SAML 2.0/OIDC-compliant IdPs) to authenticate users directly into Google Cloud without requiring synchronized or managed Cloud Identity accounts. Privileged Access Manager (PAM) is an access governance service that manages just-in-time, time-bound privilege elevation with automated workflows and audit logging.
google.groups attribute in the workforce pool provider configuration (e.g., google.groups=assertion.attributes.groups), administrators can grant IAM roles to entire principal groups using principalSet://iam.googleapis.com/locations/global/workforcePools/.../group/GROUP_NAME.iam.serviceAccounts.actAs or token generation), PAM enables temporary, scoped role grants that automatically expire and leave detailed audit logs.Direct principal binding combined with PAM provides granular, auditable least privilege while eliminating credential synchronization overhead and avoiding the security risks associated with shared service accounts.
Service account impersonation allows authenticated identities to generate short-lived credentials (such as OAuth 2.0 access tokens or OpenID Connect ID tokens) to act on behalf of a specific service account by leveraging the roles/iam.serviceAccountTokenCreator role.
External automation pipelines or legacy APIs lacking native support for federated STS tokens required access to Google Cloud resources.
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