GOOGLE-WORKSPACE-ADMINISTRATOR practice question 4 of 25

In the years prior to your organization moving to Google Workspace, it was relatively common practice for users to create consumer Google accounts…

Full set: 199 questions

Domain Business initiatives

In the years prior to your organization moving to Google Workspace, it was relatively common practice for users to create consumer Google accounts with their corporate email address (for example, to monitor Analytics, manage AdSense, and collaborate in Docs with other partners who were on Google Workspace.) You were able to address active employees’ use of consumer accounts during the rollout, and you are now concerned about blocking former employees who could potentially still have access to those services even though they don't have access to their corporate email account. What should you do?
Answer options
A: Contact Google Enterprise Support to provide a list of all accounts on your domain(s) that access non-Google Workspace Google services and have them blocked.
B: Use the Transfer Tool for Unmanaged Accounts to send requests to the former users to transfer their account to your domain as a managed account. Correct answer
C: Provide a list of all active employees to the managers of your company's Analytics, AdSense, etc. accounts, so they can clean up the respective access control lists.
D: Provision former user accounts with Cloud Identity licenses, generate a new Google password, and place them in an OU with all Google Workspace and Other Google Services disabled.
Correct Answer:
B. Use the Transfer Tool for Unmanaged Accounts to send requests to the former users to transfer their account to your domain as a managed account.
Explanation

The "Transfer tool for unmanaged users" is the specific Google Workspace feature designed to address this exact scenario. It allows an administrator to identify all consumer Google accounts that were created using a verified corporate domain email address. The administrator can then send a request to these users to convert their unmanaged account into a managed Google Workspace account. For former employees who cannot access their old mailbox to respond, the tool allows the administrator to force the transfer after a specified waiting period. Once the account is transferred and becomes managed, the administrator has full control to suspend, delete, or modify its access, effectively securing any associated company data.

Why Incorrect

A. Google Enterprise Support provides technical assistance and guidance but does not perform administrative tasks like blocking specific user accounts on behalf of a customer. Admins are expected to use the provided tools.
C. This manual process is inefficient, prone to human error, and incomplete. It only addresses known services (Analytics, AdSense) and fails to secure access to other potential assets like shared Google Docs.
D. While provisioning a Cloud Identity account creates a "conflicting account" situation, this process is more reactive. The Transfer Tool is the proactive, purpose-built solution for finding and migrating these accounts at scale.

References

1. Google Workspace Admin Help, "About the transfer tool for unmanaged users." This document explicitly states, "As an administrator, you can use the transfer tool to see which of your employees are using unmanaged Google Accounts... You can then ask these users to migrate their unmanaged accounts to a managed account in your organization." It also details the process for when a user does not respond, which is key for handling former employees.

2. Google Workspace Admin Help, "Transfer unmanaged user accounts." This guide provides the step-by-step process. Step 3, "Send transfer requests to users," notes: "If a user doesn't respond to your request, you can schedule their transfer in the transfer tool." This confirms the administrator's ability to take control of the account without user interaction.

3. Google Workspace Admin Help, "About conflicting accounts." This page describes the situation that arises from option D. It explains that when an administrator creates a managed account with an email address already in use by an unmanaged account, it creates a conflict that the user must resolve upon their next sign-in. This is less direct than the admin-initiated process in option B for securing former employee accounts.

Scroll to Top