Google Workspace Professional Administrator — Question 31

Your company’s Google Workspace primary domain is “mycompany.com,” and it has acquired a startup that is using another cloud provider with a domain named “mystartup.com.” You plan to add all employees from the startup to your Google Workspace domain while preserving their current mail addresses. The startup CEO's email address is[email protected], which also matches your company CEO's email address as[email protected], even though they are different people. Each must keep the usage of their email. In addition, your manager asked to have all existing security policies applied for the new employees without any duplication. What should you do to implement the migration?

Answer options

• A. Create a secondary domain, mystartup.com, within your current Google Workspace domain, set up necessary DNS records, and create all startup employees with the secondary domain as their primary email addresses.
• B. Create an alias domain, mystartup.com, in your existing Google Workspace domain, set up necessary DNS records, and create all startup employees with the alias domain as their primary email addresses.
• C. Create a new Google Workspace domain with “mystartup.com,” and create a trust between both domains for reusing the same security policies and sharing employee information within the companies.
• D. Create the startup employees in the “mycompany.com’ domain, and add a number at the end of the user name whenever there is a conflict. In Gmail > Routing, define a specific route for the OU that targets the startup employees, which will modify the email address domain to “mystartup.com,” and remove any numbers previously added. In addition, confirm that the SPF and DKIM records are properly set.

Correct answer: A

Explanation

The correct answer is A because creating a secondary domain allows both companies to maintain their unique email addresses while enabling management of security policies in one Google Workspace account. Option B would not allow the startup employees to have their own distinct primary addresses, while C would create unnecessary complexity by involving a separate domain. Option D complicates the email structure and could lead to confusion and management challenges.