Your customer is moving an existing corporate application to Google Cloud Platform from an on- premises data center. The business owners require minimal user disruption. There are strict security…

Question

Options

• AUse G Suite Password Sync to replicate passwords into Google.
• BFederate authentication via SAML 2.0 to the existing Identity Provider.
• CProvision users in Google using the Google Cloud Directory Sync tool.
• DAsk users to set their Google password to match their corporate password.

• A
  8% (3)
• B
  71% (27)
• C
  3% (1)
• D
  18% (7)

Explanation

By using Google Cloud Directory Sync, you've already automated the creation and maintenance of users and tied their lifecycle to the users in Active Directory. Although Google Cloud Directory Sync provisions user account details, it doesn't synchronize passwords. Whenever a user needs to authenticate in Google Cloud, the authentication must be delegated back to Active Directory, which is done by using AD FS and the Security Assertion Markup Language (SAML) protocol. This setup ensures that only Active Directory has access to user credentials and is enforcing any existing policies or multi-factor authentication (MFA) mechanisms. Moreover, it establishes a single sign-on experience between your on-premises environment and Google. https://cloud.google.com/architecture/identity/federating-gcp-with-active-directory-configuring-

No community discussion yet for this question.