GOOGLE-WORKSPACE-ADMINISTRATOR · Question #41
Your company uses Google Workspace and has acquired a subsidiary that, for business reasons, will remain indefinitely on its existing third-party collaboration platform and legacy LDAP system. This…
The correct answer is B. Create a script that uses the Directory API to sync the subsidiary's contact list as shared contacts. A is not correct because the autonomy requirement and the lack of federation between the Active Directory instances make it almost impossible for this to work properly. B is correct because domain shared contacts satisfy the requirements of this scenario. C is not correct…
Question
Your company uses Google Workspace and has acquired a subsidiary that, for business reasons, will remain indefinitely on its existing third-party collaboration platform and legacy LDAP system. This subsidiary operates autonomously with a separate, unfederated Active Directory forest. It is anticipated that interaction between the two companies will be infrequent and primarily conducted via email. Leadership's minimum requirement is adding employees of that subsidiary to your corporate global address book (GAL). What should you do?
Options
- AConfigure GCDS on the subsidiary LDAP to provision their users with Cloud Identity licenses on
- BCreate a script that uses the Directory API to sync the subsidiary's contact list as shared contacts.
- CPublish a CSV file containing the subsidiary's directory for your users to upload into Google
- DProvision the subsidiary users with G Suite accounts on the parent domain for the additional
How the community answered
(42 responses)- A10% (4)
- B81% (34)
- C5% (2)
- D5% (2)
Explanation
A is not correct because the autonomy requirement and the lack of federation between the Active Directory instances make it almost impossible for this to work properly. B is correct because domain shared contacts satisfy the requirements of this scenario. C is not correct because it would be a one-time action performed by end users, and the contacts would not be automatically available domain-wide. D is not correct because there is no requirement at this time to bring the subsidiary onto the parent's G Suite platform, and it would require licensing.
Topics
Community Discussion
No community discussion yet for this question.