Give Push to your Success with Google Cloud Certified Associate-Google-Workspace-Administrator Exam Questions [Q67-Q83]

Rate this post

Give Push to your Success with Google Cloud Certified Associate-Google-Workspace-Administrator Exam Questions

Associate-Google-Workspace-Administrator 100% Guarantee Download Associate-Google-Workspace-Administrator Exam PDF Q&A

Q67. The innovation team at your organization has a dedicated room with prototype equipment. You need to make the room bookable, add the equipment, and ensure that there are no booking conflicts. Only the innovation team and the sales directors can access this room. What should you do?

Create a separate Google Calendar resource for the room. Manually manage booking requests from both teams.

Create a Google Group for the innovation team and another Google Group for sales directors. Share the room’s calendar with both groups.

Create a Google Calendar event for the room. Share the event with the innovation team and sales directors.

Edit the Google Calendar settings for the room resource. Adjust the permission settings so only the innovation team and sales director group can view and book time on this calendar.

Q68. You work for a healthcare provider that uses an external medical billing company to manage patient records and invoices. Your organization’s employees need to share patient documents with the billing company’s employees for processing. You need to configure access so the medical billing company’s employees can view and edit the documents, but they cannot delete the documents.
What should you do?

Create a shared drive that is managed by your organization’s employees. Grant Contributor access to the billing company’s staff.

Create a shared drive. Grant Content Manager access to your organization’s employees and the billing company.

Create a group, and add the employees from your organization and the billing company. Create a shared folder on Google Drive. Grant Editor access to the group

Restrict access for the medical billing company’s employees by using Data Loss Prevention (DLP) policies.

Q69. You are configuring Chrome browser security policies for your organization. These policies must restrict certain Chrome apps and extensions.
You need to ensure that these policies are applied on the devices regardless of which user logs into the device. What should you do?

Configure the allowed list of apps in the Devices page in the apps and extensions settings.

Configure the Chrome user setting to require users to sign in to use Chrome apps and extensions.

Configure the Policy Precedence to override the domain-wide policy applied for apps and extensions.

Require 2SV for user logins.

Q70. Your CEO travels frequently, and multiple executive assistants need email access. What should you do?

Log into the CEO’s account and set up shared aliases.

Create a group of assistants and enable delegated access to the CEO’s mailbox.

Provide assistants with the CEO’s password.

Enable users to customize sender information.

Q71. Your organization recently deployed Google Workspace. Over 3,000 external contacts were shared in public folders in Microsoft Exchange before the implementation. You need to ensure that these external contacts appear to domain users in Gmail. What should you do?

Export the external contacts to a CSV file, upload the file to Google Drive, and instruct users to import to their My Contacts.

Use Google Cloud Directory Sync to sync the external contacts from the public folders in Microsoft Exchange to the Directory.

Use the Domain Shared Contacts API to add the external contacts to the Directory.

Create a user account, add the external contacts, and delegate them to all users in the domain.

Q72. Your organization handles a significant amount of sensitive customer data and must follow strict industry regulations. To meet an upcoming compliance deadline, you need to quickly implement a solution that automatically classifies files stored in Google Drive based on the content of files.
What should you do?

Create data loss prevention (DLP) rules for Drive. Configure the rules to apply Drive labels based on content.

Apply Drive labels based on content. Use Google Vault to create retention rules based on Drive labels, ensuring that data is kept for the required duration.

Implement a third-party data governance tool that integrates with Drive and provides advanced classification capabilities.

Add users into organizational units (OUs). Configure default file classification in Drive for the desired OUs.

Q73. The legal department at your organization is working on a time-critical merger and acquisition (M&A) deal. They urgently require access to specific email communications from an employee who is currently on leave. The organization’s current retention policy is set to indefinite. You need to retrieve the required emails for the legal department in a manner that ensures data privacy.
What should you do?

Instruct the IT department to directly access and forward the relevant emails to the legal department.

Temporarily grant the legal department access to the employee’s email account with a restricted scope that is limited to the M&A-related emails.

Ask a colleague with delegate access to the employee’s mailbox to identify and forward the relevant emails to the legal department.

Use Google Vault to create a matter specific to the M&A deal. Search for relevant emails within the employee’s mailbox. Export and share relevant emails with your legal department.

Q74. An employee has leaked confidential salary information to an external party. You need to preserve their messages in Vault for investigation. What should you do?

Search and export all external messages.

Create a matter and place a hold on the employee’s email.

Create a custom retention policy and review audit logs.

Use the security investigation tool first, then create a hold.

Q75. Today your company signed up for Google Workspace Business Starter with an existing domain name. You want to add team members and manage their access to email and other services. However, you are unable to create new user accounts or change user settings. You need to fix this problem. What should you do?

Run the Transfer tool to bring unmanaged users to your Workspace account.

Check domain ownership in the DNS settings.

Wait 24 hours after signing up for the features to become active.

Upgrade to a Google Workspace Enterprise edition.

Q76. You notice an increase in support tickets related to Gmail. Multiple users are reporting that their emails are not loading, and they are receiving error messages. You need to troubleshoot the issue and identify potential causes. What should you do?

Analyze the users’ Gmail labels and filters to determine whether incoming emails are being inadvertently blocked.

Collect the users’ browser versions and extensions to identify potential compatibility issues.

Review the users’ email forwarding settings to ensure that emails are not being redirected to incorrect addresses.

Gather HAR files from affected users to capture network traffic and analyze request/response details.

Q77. Your organization is increasingly concerned about its environmental impact. You want to assess the environmental impact of using Google Workspace services. Which report should you use?

Carbon footprint report

Google Environmental Report

Apps Monthly Uptime report

Accounts report

To assess the environmental impact of using Google Workspace services, you should refer to the Google Environmental Report. Google publishes comprehensive reports detailing its environmental efforts, including the energy efficiency of its data centers, its use of renewable energy, and its overall carbon footprint, which includes the impact of services like Google Workspace.
Here’s why option B is the correct choice and why the others are not relevant to assessing the overall environmental impact of using Google Workspace:
B . Google Environmental Report
Google regularly publishes detailed environmental reports that cover various aspects of its sustainability initiatives, including its progress towards using renewable energy, its efforts to improve energy efficiency in its operations (which power Google Workspace), and its overall carbon footprint. These reports provide insights into the environmental impact associated with using Google services.
Associate Google Workspace Administrator topics guides or documents reference: While there might not be a specific “Google Workspace Environmental Impact Report” as a standalone document within the Admin console, Google’s overarching “Environmental Report” (often found on Google’s sustainability or environmental responsibility websites) encompasses the infrastructure and practices that support all Google services, including Google Workspace. Administrators looking for this information would be directed to these publicly available Google reports.
A . Carbon footprint report
While the concept of a “carbon footprint report” is relevant to environmental impact, Google typically includes this information within its broader “Environmental Report” rather than providing a separate report specifically for Google Workspace usage within an organization’s Admin console. You would likely find data related to the carbon efficiency of Google’s infrastructure in their main environmental disclosures.
Associate Google Workspace Administrator topics guides or documents reference: Google’s communication about its carbon footprint and environmental efforts is usually consolidated in their public sustainability reports.
C . Apps Monthly Uptime report
The Apps Monthly Uptime report provides information about the reliability and availability of Google Workspace services. It focuses on service performance and uptime metrics, not on environmental impact or sustainability.
Associate Google Workspace Administrator topics guides or documents reference: The Google Workspace Admin Help documentation on service-level agreements (SLAs) and service status provides information about uptime guarantees and how to monitor service availability, which is the focus of the Apps Monthly Uptime report.
D . Accounts report
The Accounts report in the Google Admin console provides details about user accounts within your organization, such as the number of active users, account status, and other user-related information. It does not contain any data or analysis related to the environmental impact of using Google Workspace services.
Associate Google Workspace Administrator topics guides or documents reference: The Google Workspace Admin Help documentation on reporting and user accounts describes the information available in the Accounts report, which is focused on user management and activity metrics.
Therefore, to assess the environmental impact of using Google Workspace services, your organization should refer to the publicly available Google Environmental Report, which details Google’s sustainability efforts and overall environmental performance.

Q78. Your company has recently migrated from an on-premises email solution to Google Workspace. You have successfully added and verified the new primary domain. However, you also want to continue receiving emails sent to your former on-premises email server for a transitional period. You need to ensure that emails sent to your former domain are still delivered to your on-premises server, even though your primary email system is now Google Workspace. What should you do?

Configure MX records for the former domain to point to your on-premises email servers.

Add the former domain as a secondary domain in your Google Workspace settings and verify the domain.

Adjust the TTL (Time-to-Live) for the former domain to ensure a smooth transition.

Add the former domain as a domain alias for the primary domain.

To ensure that emails sent to your former domain are still delivered to your on-premises server during a transitional period after migrating your primary email to Google Workspace, you need to configure the MX (Mail Exchanger) records for the former domain to point to your on-premises email servers.
Here’s why the other options are incorrect and why configuring MX records is the correct approach, based on the principles of email routing and domain management within Google Workspace:
A . Configure MX records for the former domain to point to your on-premises email servers.
MX records are DNS records that specify the mail servers responsible for accepting email messages on behalf of a domain. 1 By configuring the MX records for your former domain to point to the IP addresses or hostnames of your on-premises email servers, you are instructing the internet’s DNS system that any email addressed to users on your former domain should be routed to those specific servers. This ensures that mail for the former domain bypasses Google Workspace and continues to be delivered to your existing infrastructure.
Associate Google Workspace Administrator topics guides or documents reference: While the exact phrasing might vary across different Google Workspace support articles and documentation, the core concept of MX records and their role in email routing is fundamental to domain setup and management. The official Google Workspace Admin Help documentation on “Set up MX records for Google Workspace” (or similar titles) explicitly explains how MX records control where email for a domain is delivered. In this scenario, you are essentially managing the MX records for a domain that is not the primary Google Workspace domain to direct its mail flow.
B . Add the former domain as a secondary domain in your Google Workspace settings and verify the domain.
Adding a domain as a secondary domain within Google Workspace allows you to create separate user accounts with email addresses on that domain, all managed within your Google Workspace organization. This would mean that Google Workspace would handle the email for the former domain, which is the opposite of what you need in this scenario (you want the emails to go to your on-premises server).
Associate Google Workspace Administrator topics guides or documents reference: The Google Workspace Admin Help documentation on “Add a domain or domain alias” clearly distinguishes between secondary domains and domain aliases and their respective functionalities. Secondary domains are for managing separate sets of users, not for routing mail to external servers.
C . Adjust the TTL (Time-to-Live) for the former domain to ensure a smooth transition.
TTL is the amount of time a DNS record is cached by resolving name servers. While adjusting TTL can be important when making DNS changes (like switching MX records to Google Workspace), it doesn’t directly control where email is delivered. Lowering the TTL before making MX changes to point to Google Workspace helps with a faster transition, but in this case, you are not pointing the former domain’s mail to Google Workspace. Therefore, adjusting the TTL alone will not achieve the desired outcome.
Associate Google Workspace Administrator topics guides or documents reference: Information on TTL is typically found within the context of DNS management best practices in Google Workspace Admin Help, often related to domain verification or MX record changes to Google. It doesn’t serve as a mechanism for routing mail to external, non-Google Workspace servers for a domain that isn’t managed by Google Workspace for email.
D . Add the former domain as a domain alias for the primary domain.
Adding a domain as a domain alias means that emails sent to addresses on the alias domain will be delivered to the corresponding user accounts on your primary Google Workspace domain. This is useful when you want users to receive email at multiple domain names within your Google Workspace environment. It does not route email to an external, on-premises server.
Associate Google Workspace Administrator topics guides or documents reference: The Google Workspace Admin Help documentation on “Add a domain or domain alias” clearly explains the functionality of domain aliases. It emphasizes that email sent to a domain alias is received by the users on the primary domain, not an external system.
Therefore, the only way to ensure emails sent to your former domain are still delivered to your on-premises server is by configuring the MX records for that former domain to point to your on-premises mail server.

Q79. An employee with a Workspace Business Plus license at your company is going on a long leave soon. The employee will not need access to their Google Workspace data, but their teammates will need access to the employee’s dat a. When the employee returns from leave, you will need to restore access to their account, data, emails, and shared documents. You need to preserve the employee’s Workspace data while also minimizing cost while they are on leave. What should you do?

Suspend their account in the Admin console.

Purchase an Archived User license and assign the license to the employee.

Export the account data by using Takeout, and remove the user license in the Admin console.

Copy the employee’s emails, and transfer their file ownership to a teammate. Delete the user account.

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.

Q80. Your organization needs an approval application for purchases where a user can enter information on the purchase required and then submit it for management approval. You need to suggest a solution to create the application that must be available on both the web and mobile devices. Your organization does not have software developers or the budget to hire a third party. What should you do?

Suggest that the organization use AppScript to create forms linked to a Google Sheet to store the purchase data.

Suggest that the organization continue to approve requests manually until budget is available to use a third-party application provider.

Suggest the organization use AppSheet to create the application.

Suggest that the organization develop an application internally with a database, a backend service for data retrieval, and a frontend service for the application’s user interface.

Q81. An employee using a Workspace Enterprise Standard license was terminated from your organization. You need to ensure that the former employee no longer has access to their Workspace account and preserve access to the former employee’s documents for the manager and the team.
You want to minimize license cost. What should you do?

Delete the former employee’s Workspace account.

Suspend former employee’s Workspace account.

Reset the password of the former employee and keep their Workspace license active.

Switch the license type of the former employee’s Workspace account to an Archived User license.

Q82. Your organization has experienced a recent increase in unauthorized access attempts to your company’s Google Workspace instance. You need to enhance the security of user accounts while following Google-recommended practices. What should you do?

Disable password recovery options to prevent unauthorized individuals from accessing user accounts.

Implement a strong password policy and enable text messages as the 2-Step Verification (2SV) using text messages.

Enforce the use of physical security keys as the 2-Step Verification (2SV) method for all users.

Enforce a strong password policy that requires users to include special characters, numbers, and uppercase letters.

Q83. Per regulatory requirements, your company is required to keep the data of employees located in Germany within Europe and the data of employees located in the US within the US. The employees in Germany are in a separate organizational unit (OU) than employees in the US. You need to ensure that where employee data is stored is in compliance with the location regulations.
What should you do?

Instruct employees to use Drive for desktop to keep documents on their corporate computers.

Create two Groups. Assign employees into the Germany or US Group based on their location. Use Google Drive trust rules to prevent sharing between the Groups.

Navigate to the Data Regions function in the Admin console. Select the Europe region for employees in Germany, and select the US region for US employees.

Navigate to the Data Regions function in the Admin console. Select ‘No preference.’

Google Associate-Google-Workspace-Administrator Exam Syllabus Topics:

Topic	Details
Topic 1	Troubleshooting: This section of the exam measures the skills of Technical Support Specialists and focuses on identifying, diagnosing, and resolving issues within Google Workspace services. It tests the ability to troubleshoot mail delivery problems, interpret message headers, analyze audit logs, and determine root causes of communication failures. Candidates are expected to collect relevant logs and documentation for support escalation and identify known issues. The section also evaluates knowledge in detecting and mitigating basic email attacks such as phishing, spam, or spoofing, using Gmail security settings and compliance tools. Additionally, it assesses troubleshooting skills for Google Workspace access, performance, and authentication issues across different devices and applications, including Google Meet and Jamboard, while maintaining service continuity and network reliability.
Topic 2	Supporting Business Initiatives: This section of the exam measures the skills of Enterprise Data Managers and covers the use of Google Workspace tools to support legal, reporting, and data management initiatives. It assesses the ability to configure Google Vault for retention rules, legal holds, and audits, ensuring compliance with legal and organizational data policies. The section also involves generating and interpreting user adoption and usage reports, analyzing alerts, monitoring service outages, and using BigQuery to derive actionable insights from activity logs. Furthermore, candidates are evaluated on their proficiency in supporting data import and export tasks, including onboarding and offboarding processes, migrating Gmail data, and exporting Google Workspace content to other platforms.
Topic 3	Data Access and Authentication: This section of the exam evaluates the capabilities of Security Administrators and focuses on configuring policies that secure organizational data across devices and applications. It includes setting up Chrome and Windows device management, implementing context-aware access, and enabling endpoint verification. The section assesses the ability to configure Gmail Data Loss Prevention (DLP) and Access Control Lists (ACLs) to prevent data leaks and enforce governance policies. Candidates must demonstrate an understanding of configuring secure collaboration settings on Drive, managing client-side encryption, and restricting external sharing. It also covers managing third-party applications by controlling permissions, approving Marketplace add-ons, and deploying apps securely within organizational units. Lastly, this section measures the ability to configure user authentication methods, such as two-step verification, SSO integration, and session controls, ensuring alignment with corporate security standards and compliance requirements.
Topic 4	Configuring Services: This section of the exam evaluates the expertise of IT Systems Engineers and emphasizes configuring Google Workspace services according to corporate policies. It involves assigning permissions, setting up organizational units (OUs), managing application and security settings, and delegating Identity and Access Management (IAM) roles. The section also covers creating data compliance rules, applying Drive labels for data organization, and setting up feature releases such as Rapid or Scheduled Release. Candidates must demonstrate knowledge of security configurations for Google Cloud Marketplace applications and implement content compliance and security integration protocols. Furthermore, it includes configuring Gmail settings such as routing, spam control, email delegation, and archiving to ensure communication security and policy alignment across the organization.
Topic 5	Managing Objects: This section of the exam measures the skills of Google Workspace Administrators and covers the management of user accounts, shared drives, calendars, and groups within an organization. It assesses the ability to handle account lifecycles through provisioning and deprovisioning processes, transferring ownership, managing roles, and applying security measures when access needs to be revoked. Candidates must understand how to configure Google Cloud Directory Sync (GCDS) for synchronizing user data, perform audits, and interpret logs. Additionally, it tests knowledge of managing Google Drive permissions, lifecycle management of shared drives, and implementing security best practices. The section also focuses on configuring and troubleshooting Google Calendar and Groups for Business, ensuring proper access control, resource management, and the automation of group-related tasks using APIs and Apps Script.