Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is designing a hybrid cloud architecture where external on-premises applications must access Google Cloud resources securely without using downloadable service account keys. The compliance and security teams establish the following technical requirements:
Which combination of architectural and IAM practices should the cloud architect recommend?
Workload Identity Federation allows external workloads (such as on-premises applications or systems hosted in other clouds) to impersonate Google Cloud service accounts using short-lived credentials derived from Security Token Service (STS) tokens, eliminating the risks associated with downloadable service account keys.
serviceAccountDelegationInfo metadata, providing complete end-to-end traceability for forensic analysis.roles/iam.workloadIdentityPoolAdmin) role ensures that only authorized administrators can modify attribute mappings, preventing malicious actors from altering translation rules to gain unauthorized access.
This architecture establishes zero-trust identity federation while strictly fulfilling organizational compliance, least privilege governance, and end-to-end non-repudiation requirements.
This option configures Workload Identity Federation using user email addresses as identity identifiers, depends solely on default Admin Activity audit logs, and grants full project-level Owner permissions (roles/owner) to application developers.
The identity provider guaranteed that email addresses were permanent and immutable, and the developers were designated as full cloud project administrators in a sandbox environment.
This design generates static service account private keys, centralizes their storage within Secret Manager, and grants developers the Service Account Key Admin (roles/iam.serviceAccountKeyAdmin) role to manage key lifecycles.
The on-premises environment lacked an OIDC or SAML 2.0 compliant identity provider and could not support Workload Identity Federation token exchanges.
This option maps SAML group claims directly to primitive Editor roles (roles/editor), disables Data Access audit logs to avoid logging costs, and assigns the IAM Workload Identity Pool Admin role widely across engineering teams.
The workload only operated in a non-sensitive testing environment with no compliance or auditing requirements.
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