GOOGLE-WORKSPACE-ADMINISTRATOR practice question 21 of 25

You act as the Google Workspace Administrator for a company that has just acquired another organization. The acquired company will be migrated into…

Full set: 199 questions

Domain Service configuration

You act as the Google Workspace Administrator for a company that has just acquired another organization. The acquired company will be migrated into your Workspace environment in 6 months. Management has asked you to ensure that the Google Workspace users you currently manage can efficiently access rich contact information in Workspace for all users. This needs to occur before the migration, and optimally without additional expenditure. What step do you take to populate contact information for all users?
Answer options
A: Bulk-upload the contact information for these users via CSV into the Google Directory.
B: Use the Domain Shared Contacts API to upload contact information for the acquired company's users. Correct answer
C: Provision and license Google Workspace accounts for the acquired company's users because they will need accounts in the future.
D: Prepare an uploadable file to be distributed to your end users that allows them to add the acquired company’s user contact information to their personal contacts.
Correct Answer:
B. Use the Domain Shared Contacts API to upload contact information for the acquired company's users.
Explanation

The most efficient and cost-effective solution is to use the Domain Shared Contacts API. This API is specifically designed to programmatically create and manage external contacts that are shared with all users in a Google Workspace domain. These contacts appear in services like Gmail contact auto-complete and the Contacts interface without requiring a Google Workspace license for each entry. This directly addresses the need to make contact information available to all current users before the full migration and aligns with the goal of avoiding additional expenditure.

Why Incorrect

A. Bulk-uploading via CSV into the Google Directory is a method for creating new user accounts, which would prematurely provision users and incur unnecessary licensing costs.
C. Provisioning and licensing accounts 6 months before the migration is financially inefficient and contradicts the requirement to find a solution with optimal, minimal expenditure.
D. Distributing a file for end-users to manage their personal contacts is not a centralized or efficient administrative solution. It is unreliable and difficult to maintain or update consistently across the organization. ---

References

1. Google Workspace Admin Help, "About the Directory": This document clarifies the contents of the Directory. It states, "The Directory includes the user profiles of people in your organization... It can also include external contacts... To add and manage external contacts programmatically, use the Domain Shared Contacts API." This directly supports using the API for external contacts rather than creating full user profiles.

2. Google Developers, "Domain Shared Contacts API Overview": The official API documentation states, "The Domain Shared Contacts API allows applications to get and update external contacts that are shared to all users in a Google Workspace domain." This confirms that the API's purpose is to manage shared contacts for the entire domain, which is precisely the requirement in the scenario.

3. Google Workspace Admin Help, "Add or update multiple users from a CSV file": This guide details the process of using a CSV file to "add multiple new users at once." The entire process is oriented around creating full user accounts, which require licenses, making this method unsuitable for the stated constraints.

Scroll to Top