Skip to Content

Google Professional Cloud Developer: How to Set Up Google Cloud Console Access with External Identity Provider?

Learn how to configure workforce identity federation with an external identity provider and set up attribute mapping to enable Google Cloud console access for all employees while personalizing the sign-in experience.

Table of Contents

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?

A. Configure workforce identity federation with the external IdP, and set up attribute mapping.
B. Configure a service account for each individual by using the user name and photo, and grant permissions for each user to impersonate their respective service accounts.
C. Configure workload identity federation to get the external IdP tokens, and use these tokens to sign in to the Google Cloud console.
D. Create a Google group that includes organization email IDs for all users. Ask users to use the same name, work email ID, and password to register and sign in.

Answer

A. Configure workforce identity federation with the external IdP, and set up attribute mapping.

Explanation

To allow all employees to access the Google Cloud console using the existing users and groups in your external identity provider (IdP), you should set up workforce identity federation. This involves configuring a connection between your external IdP and Google Cloud.

Once workforce identity federation is established, you can personalize the sign-in experience by setting up attribute mapping. Attribute mapping allows you to pass user attributes like name and photo from the external IdP to Google Cloud. This way, when users sign in to the Google Cloud console, they will see their name and photo displayed, providing a personalized experience.

The other options are incorrect:

B. Configuring a service account for each user is not the right approach for workforce identity federation. Service accounts are meant for server-to-server interactions, not user authentication.

C. Workload identity federation is used to grant external identities access to Google Cloud resources, but it does not provide Google Cloud console access for users.

D. Creating a Google group with organization email IDs does not leverage the existing users and groups in your external IdP. It would require users to register separately, which is not the desired solution.

Therefore, configuring workforce identity federation with your external IdP and setting up attribute mapping is the correct way to enable Google Cloud console access for all employees while providing a personalized sign-in experience.

Google Professional Cloud Developer certification exam assessment practice question and answer (Q&A) dump including multiple choice questions (MCQ) and objective type questions, with detail explanation and reference available free, helpful to pass the Google Professional Cloud Developer exam and earn Google Professional Cloud Developer certification.