Google Professional Cloud Security Engineer Question 12
Select 3Google Cloud PlatformYour organization wants to use Google Workspace accounts for authentication with a third-party SaaS application. The IT team has decided to configure single sign-on (SSO) using a third-party identity provider (IdP) and synchronize user identities between the organization's on-premises Active Directory and Google Cloud. Which of the following steps are necessary to achieve this setup?
- A
Install and configure Google Cloud Directory Sync (GCDS) to sync user accounts from Active Directory to Google Cloud.
- B
Enable the Identity-Aware Proxy (IAP) on the third-party SaaS application for SSO integration.
- C
Configure the third-party SaaS application to trust the third-party IdP as its SSO provider using SAML.
- D
Set up SAML-based federation between the third-party IdP and Google Workspace.
- E
Create a custom OAuth 2.0 client ID in Google Cloud Console for SSO integration.
Show answer and explanation
Correct answers: A, C, D
Explanation
To implement single sign-on (SSO) with a third-party identity provider (IdP) and synchronize user accounts, you must use Google Cloud Directory Sync (GCDS) to sync identities from your on-premises Active Directory to Google Cloud. Then, you need to configure SAML-based federation between Google Workspace and the third-party IdP to enable SSO. Finally, the third-party SaaS application must be configured to trust the third-party IdP as its SSO provider using SAML.
- A. Correct.
Correct. Google Cloud Directory Sync (GCDS) is required to synchronize user accounts from on-premises Active Directory to Google Cloud, ensuring the identities are available for SSO.
- B. Incorrect.
Incorrect. Identity-Aware Proxy (IAP) is not relevant to this scenario because it is used to protect web applications and resources hosted on Google Cloud, not for integrating third-party SaaS applications.
- C. Correct.
Correct. The third-party SaaS application must be configured to trust the third-party identity provider (IdP) as its SSO provider using SAML, which is a standard protocol for SSO integration.
- D. Correct.
Correct. SAML-based federation must be set up between the third-party IdP and Google Workspace to allow users to authenticate using their Google Workspace credentials.
- E. Incorrect.
Incorrect. Creating a custom OAuth 2.0 client ID is not required for SAML-based SSO. OAuth 2.0 is a different protocol and is not applicable to this specific setup.