PROFESSIONAL-CLOUD-DEVELOPER · Question #325
Your organization has users and groups configured in an external identity provider (IdP). You want to leverage the same external IdP to allow Google Cloud console access to all employees. You also wan
The correct answer is A. Configure workforce identity federation with the external IdP, and set up attribute mapping.. Workforce Identity Federation is specifically designed for human users (as opposed to Workload Identity Federation, which is for applications/workloads) to access Google Cloud using external IdP identities - no Google accounts required. Attribute mapping lets you map IdP claims (
Question
Your organization has users and groups configured in an external identity provider (IdP). You want to leverage the same external IdP to allow Google Cloud console access to all employees. You also want to personalize the sign-in experience by displaying the user's name and photo when users access the Google Cloud console. What should you do?
Options
- AConfigure workforce identity federation with the external IdP, and set up attribute mapping.
- BConfigure a service account for each individual by using the user name and photo, and grant
- CConfigure workload identity federation to get the external IdP tokens, and use these tokens to
- DCreate a Google group that includes organization email IDs for all users. Ask users to use the
How the community answered
(41 responses)- A78% (32)
- B5% (2)
- C2% (1)
- D15% (6)
Explanation
Workforce Identity Federation is specifically designed for human users (as opposed to Workload Identity Federation, which is for applications/workloads) to access Google Cloud using external IdP identities - no Google accounts required. Attribute mapping lets you map IdP claims (e.g., 'displayName', 'picture') to Google attributes so the Cloud console can personalize the sign-in experience. Option B (service accounts per user) is incorrect because service accounts are for applications, not humans. Option C (Workload Identity Federation) is for service-to-service auth, not console user access. Option D (Google Group with org emails) requires users to have Google accounts and does not leverage the external IdP.
Topics
Community Discussion
No community discussion yet for this question.