data from the former accounts, and then delete them.
Explanation:
To mitigate the security risk of unauthorized sign-in attempts from countries without local employees, two effective and cost-efficient solutions are:
A . Deploy 2-Step Verification for all users who have security keys. This enhances account security by requiring an additional verification step, reducing the risk of unauthorized access.
D . Subscribe to Cloud Identity Premium for all accounts and define Context-Aware Access levels to allow access only from specific countries where the company has employees. This adds an additional layer of security by controlling access based on geographic location.
These solutions are effective in enhancing security while minimizing financial outlay compared to other options like upgrading to Enterprise Plus.
Reference:
Google Workspace Admin Help - Set up 2-Step Verification
Google Workspace Admin Help - Context-Aware Access

To implement industry-standard email authentication protocols as part of a layered security approach for Gmail, you should configure DKIM (DomainKeys Identified Mail) and SPF (Sender Policy Framework) records for your domain. These protocols are crucial for verifying the sender's identity and ensuring the integrity of email messages.
Here's a breakdown of why options C and E are correct and why the others are not primarily email authentication protocols or best practices in this context:
C . Configure DKIM to digitally sign outbound emails and verify their origin.
DKIM adds a digital signature to the headers of outbound emails. This signature is verified by receiving mail servers using a public key published in your domain's DNS records. DKIM helps to confirm that the email was indeed sent from your domain and that its content has not been altered in transit. It is a key email authentication protocol that enhances deliverability and protects against email spoofing.
Associate Google Workspace Administrator topics guides or documents reference: The official Google Workspace Admin Help documentation on "Help prevent email spoofing with DKIM" (or similar titles) explains how to set up DKIM for your domain. It details the process of generating a DKIM key, adding the public key as a TXT record in your DNS, and enabling DKIM signing in the Google Admin console. The documentation emphasizes DKIM's role in authenticating outbound mail and improving email security.
E . Set up SPF records to specify authorized mail servers for your domain.
SPF is a DNS-based email authentication protocol that allows you to specify which mail servers are authorized to send emails on behalf of your domain. Receiving mail servers check the SPF record in the sender's domain's DNS to verify if the sending server's IP address is listed as authorized. This helps to prevent spammers from forging the "From" address of your domain.
Associate Google Workspace Administrator topics guides or documents reference: The Google Workspace Admin Help documentation on "Help prevent spoofing with SPF" (or similar titles) guides administrators on creating and publishing SPF records in their domain's DNS. It explains the syntax of SPF records and how they help receiving servers validate the sender's origin, thus reducing spoofing and improving deliverability.
Now, let's look at why the other options are not the primary choices for implementing industry-standard email authentication protocols:
A . Enable a default email quarantine for all users to isolate suspicious emails and determine if the messages haven't been authenticated.
Email quarantine is a security feature that holds potentially harmful or suspicious emails for review. While it can help manage unauthenticated emails, it is a response to potential authentication failures or suspicious content, not an authentication protocol itself. Quarantine helps in handling emails that fail authentication checks (like SPF or DKIM) or are flagged by other security measures.
Associate Google Workspace Administrator topics guides or documents reference: Documentation on Gmail quarantine settings explains how to configure them to manage suspicious emails, including those that may not be properly authenticated. It's a post-authentication handling mechanism.
B . Configure a blocked senders rule to block all emails from unknown senders.
Blocking all emails from "unknown senders" is an overly aggressive and impractical approach for most organizations, as you will likely receive legitimate emails from new contacts or domains. While you can create blocklists, it's not a standard email authentication protocol and can lead to significant disruption of email flow.
Associate Google Workspace Administrator topics guides or documents reference: Gmail's blocking features allow users and administrators to block specific addresses or domains, but blocking all unknown senders is not a recommended security practice.
D . Disable IMAP for your organization to prevent external clients from accessing Gmail.
Disabling IMAP can enhance security by limiting how users access their email, potentially reducing the risk of compromised third-party applications. However, it is not an email authentication protocol that verifies the sender of an email. It controls access to the mailbox, not the authentication of emails received or sent.
Associate Google Workspace Administrator topics guides or documents reference: Documentation on managing IMAP and POP access explains how to enable or disable these protocols for users, focusing on access methods rather than email sender authentication.
Therefore, the two correct answers for implementing industry-standard email authentication protocols are configuring DKIM to sign outbound emails and setting up SPF records to specify authorized sending servers.

Creating separate organizational units (OUs) for marketing and sales allows you to apply the Gemini licenses to only those departments. By enabling Gemini for just that OU, you ensure that only the employees in marketing and sales have access to Gemini features, ensuring an efficient and scalable solution. This avoids the need for manual assignment or unnecessary instructions to users in other departments.

To preserve an employee's Google Workspace data while they are on long leave, allow teammates access to that data, and minimize costs with the intention of fully restoring the account upon their return, the best course of action is to purchase an Archived User license and assign it to the employee.
Here's why option B is the most suitable and cost-effective solution that meets all the requirements:
B . Purchase an Archived User license and assign the license to the employee.
Google Workspace offers Archived User licenses at a significantly lower cost than a full user license. When you assign an Archived User license to an account, the data (including Gmail, Drive, and other Workspace services) is retained and can be accessed by other authorized users (e.g., administrators or delegated teammates). The user themselves cannot log in or use the services, thus minimizing cost. Upon the employee's return, you can easily reassign a full Business Plus license to their account, restoring their full access without any data loss or complex restoration processes.
Associate Google Workspace Administrator topics guides or documents reference: The official Google Workspace Admin Help documentation on "About Archived User licenses" (or similar titles) explicitly describes this scenario as the intended use case for Archived User licenses. It outlines the reduced cost, the preservation of data, the ability for administrators to access the data (and delegate access), and the seamless transition back to a full license when the user returns.
A . Suspend their account in the Admin console.
Suspending an account prevents the user from accessing it, but it typically retains the full license cost. While an administrator might be able to access some data in a suspended account, it doesn't offer the cost savings of an Archived User license. Additionally, depending on the suspension duration and Google's policies, there might be implications for long-term data retention without an active or archived license.
Associate Google Workspace Administrator topics guides or documents reference: The Google Workspace Admin Help documentation on "Suspend or restore users" explains the functionality of account suspension. It primarily focuses on temporarily revoking access, not on long-term, cost-effective data preservation with potential for delegated access.
C . Export the account data by using Takeout, and remove the user license in the Admin console.
While Google Takeout allows you to export user data, this creates a separate archive that is not directly integrated with Google Workspace. Providing teammates access to this exported data would be cumbersome and not as seamless as accessing it within the original Workspace environment. Removing the user license would stop data retention in Google Workspace, and restoring the account fully upon the employee's return would involve re-importing the data, which can be complex, time-consuming, and potentially lead to data loss or inconsistencies. This option does minimize cost by removing the license but at the expense of easy access and seamless restoration.
Associate Google Workspace Administrator topics guides or documents reference: Documentation on Google Takeout describes its purpose for exporting data out of Google services, primarily for personal use or data migration, not for temporary data preservation and collaborative access within the Workspace environment. Removing a license typically leads to data deletion after a certain period unless an alternative (like an Archived User license) is in place.
D . Copy the employee's emails, and transfer their file ownership to a teammate. Delete the user account.
This approach involves significant data manipulation and potential loss of context. Copying emails might not preserve the entire mailbox structure and could miss important information. Transferring file ownership can be complex and might not cover all types of data or shared items. Deleting the user account would permanently remove the data, making full restoration upon the employee's return impossible. This option is not suitable for preserving the employee's Workspace data and restoring their account later.
Associate Google Workspace Administrator topics guides or documents reference: Google Workspace's account management best practices emphasize preserving user accounts and data for returning employees. Deleting accounts with the intention of temporary leave is strongly discouraged due to the difficulty and risks associated with data recovery and account recreation.
Therefore, the most appropriate action that meets all the requirements of preserving data, providing access to teammates, minimizing cost during the leave, and allowing for full restoration upon return is to purchase an Archived User license and assign it to the employee.

Identify Unmanaged Accounts: First, you need to identify the unmanaged accounts in your domain. These are accounts created by users with their company email address but are not managed by your Google Workspace.
Use the Transfer Tool for Unmanaged Accounts: Google provides a specific tool called the "Transfer tool for unmanaged users". This tool allows administrators to invite users with unmanaged accounts to join the organization's managed Google Workspace account.
Send Invitations: Using this tool, you can send invitations to these users to join your Google Workspace domain.
Accept Invitations: The users need to accept the invitation to migrate their unmanaged account into your managed domain.
Monitor and Verify: After the invitation is accepted, monitor the process to ensure that all accounts are successfully migrated and are now managed under your Google Workspace domain.
Reference
Google Support: Transfer tool for unmanaged users