Associate Google Workspace Administrator — Free Practice Questions
10 free sample questions from a bank of 10, with the correct answers and explanations. No signup required — start practising right now.
1Your company is undergoing a regulatory compliance audit. As part of the audit, you are required to demonstrate that you can preserve all electronic communications related to a specific project for a potential legal discovery process. You need to configure Google Vault to accomplish this goal. What should you do?
Use the security investigation report to show Vault log events.
Use the search and export functionality to identify all relevant communications within the project timeframe.
Create a matter and a hold on all project-related data sources such as Email, Chat, and Drive within Google Workspace.
Create a custom retention policy for the project data. Ensure that the policy covers the required retention period.
Answer: C
The short version
C - Create a Vault matter and place holds on Gmail, Chat and Drive so the project's data cannot be deleted or altered.
Key concepts
Matter: A Vault container that groups holds, retention rules, saved searches and exports for one investigation or legal case.
Hold (custody): A rule that makes matching data undeletable - users cannot trash, edit or purge it and admins cannot remove it, overriding normal retention.
Data sources: The services a hold can cover, such as Gmail, Drive, Chat and Groups; one matter can hold all of them together.
Retention rules: Lifecycle settings that control how long data is kept, and which a user or admin can shorten; they are not a preservation guarantee.
Export: Producing copies of preserved data for custodians; it only works on data already under a hold.
Why C is correct
Legal discovery and regulatory preservation require that the data provably not disappear, and Google Vault implements that with a hold inside a matter. Once a hold is applied to a data source, the items in scope become immutable: users lose the ability to trash or modify them, and administrators cannot purge them ahead of the case, regardless of each user's own retention settings. Because the requirement covers all electronic communications for the project, a single matter with holds on Gmail, Chat and Drive captures every channel and produces the defensible record the auditor expects.
Why the others are wrong
A. The security investigation report surfaces login activity and security events such as suspicious logins or admin changes. It reports on events and preserves no message content, so it cannot demonstrate that communications were retained.
B. Search and export are operations performed on data that is already preserved. Searching a mailbox that nobody has held changes nothing - the next user deletion still destroys the evidence - so this cannot satisfy a preservation requirement.
D. A custom retention policy manages general data lifecycle for a scope of users or OU, and it can be edited or shortened by administrators. It produces no matter, no custodians and no hold record, so it does not create a defensible legal-discovery preservation.
AGWA exam tip
Remember the pairing: a matter is the container and the hold is what makes data undeletable. Retention rules keep data longer; only a hold preserves it for a case.
2Several employees from your finance department are collaborating on a long-term, multi-phase project. You need to create a confidential group for this project as quickly as possible. You also want to minimize management overhead. What should you do?
Create a Google Group by using Google Cloud Directory Sync (GCDS) to automatically sync the members.
Create a dynamic group and define the Department user attribute as a condition for membership with the value as the finance department.
Create a Google Group and update the settings to allow anyone in the organization to join the group.
Create a Google Group and appoint a group admin to manage the membership of this group.
Answer: D
The short version
D - Create a Google Group and appoint a group admin, which gives the project a shared identity while delegating membership management.
Key concepts
Google Group: A Workspace container providing a shared address, mailbox, Drive, calendar and shared contacts for collaborating users.
Group managers / owners: Members granted the right to add, remove and moderate the group's members, delegating that work away from the super admin.
Confidentiality: Restricting membership and external posting so the group's address, content and membership stay inside the organization.
Dynamic group: A mail alias whose membership is derived automatically from a user attribute such as department; it cannot host the full collaborative resources of a group.
GCDS (Google Cloud Directory Sync): A provisioning tool that syncs users from an external LDAP/AD directory into Google Workspace accounts, not group membership on demand.
Why D is correct
A Google Group is the Workspace object that bundles a shared mailbox, Drive, calendar and contacts, which is exactly what a multi-phase project needs, and keeping membership inside the domain is what makes it confidential. Appointing a member as group admin transfers day-to-day membership management to that person, so the super admin avoids the ongoing per-user overhead of adding and removing people - which is precisely the requirement to create it quickly and minimize management. The group is created and delegated in a couple of console actions, with no extra infrastructure.
Why the others are wrong
A. GCDS synchronizes Google Workspace user accounts from an external directory such as Active Directory or LDAP. It does not create or populate a Workspace-native Google Group, and standing up an external directory sync adds setup and maintenance overhead rather than removing it.
B. A dynamic group is a mail alias whose membership is computed from a user attribute; it cannot provide a group Drive, calendar or shared mailbox for project content, and it is not a way to create a Google Group with managed membership.
C. Setting the group to allow anyone in the organization to join removes the confidentiality requirement entirely, since any employee could read and post in a group meant only for the finance project team.
AGWA exam tip
For a confidential project group that must be quick and hands-off: create the group, keep it internal, and hand the owner role to a member instead of managing it centrally.
3Today 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.
Answer: B
The short version
B - Verify domain ownership in DNS; until Google's verification record is published and validated, privileged admin actions are blocked.
Key concepts
Domain verification: Publishing the DNS TXT record (or CNAME target) Google generates for your domain and confirming that your DNS authority serves it.
Admin console lockout: Until verification completes, the console treats the domain as unproven and blocks privileged operations such as creating users or changing user settings.
Super admin: The administrative role that owns the account; the role's powers over a domain are gated on that domain being verified.
Transfer tool: A sandboxed environment for bulk-migrating users and data from another Google account into this Workspace tenant.
Edition versus verification: The subscription edition controls features and limits; it has no bearing on whether the domain's DNS proves ownership.
Why B is correct
Signing up with an existing domain creates the account but does not prove that you control that domain. Verification requires adding the TXT record Google supplies to your DNS zone; Google then queries DNS and confirms it. Until that confirmation succeeds, the account treats the domain as unverified and withholds privileged administrative capabilities - which is exactly the reported symptom, being unable to create users or change user settings. So the first action is to inspect the DNS settings for the verification record and publish it if it is missing.
Why the others are wrong
A. The Transfer tool brings existing users and their data into the current Workspace account from another Google account. It concerns user migration, not administrative authority over your own domain, so it would not unblock user creation.
C. Waiting does not add a DNS record. Once the correct TXT record is in place and propagates, verification normally completes quickly; the longer propagation-related waits apply to features becoming active after verification, not to the domain being unverified in the first place.
D. Upgrading the edition adds features and user limits but does nothing to DNS. Domain verification is a property of your DNS zone and your account, entirely independent of which subscription tier you hold.
AGWA exam tip
New Workspace account, no admin rights: check DNS for Google's TXT record first. Editions control features; only verification controls authority over your domain.
4A team of temporary employees left your organization after completing a shared project. Per company policy, you need to disable their Google Workspace accounts while preserving all project data and related communications in Google Vault for a minimum of two years. You want to comply with this policy while minimizing cost. What should you do?
Purchase and assign Archived User licenses to the former employees.
Transfer the former employees’ files and data to active user accounts. Delete the former employees’ Workspace accounts.
Purchase additional user licenses and suspend the former employees’ accounts.
Move the former employees to their own organizational unit (OU) and disable access to Google services for that OU.
Answer: A
The short version
A - Assign Archived User licenses: the former employee's sign-in is disabled while their data stays preserved and searchable.
Key concepts
Archived User: A reduced-cost license for a former employee whose account must be disabled but whose data must be retained, typically for legal or regulatory reasons.
Suspended user: A full-license account whose sign-in and services are blocked while data remains; it still costs a full user license.
Data preservation: Requirement that the former employee's mailbox, Drive files and chats remain intact and, where a hold applies, undeletable.
License cost: The recurring per-user charge; an Archived User costs far less than a standard Business Plus or Enterprise seat.
Organizational unit (OU): A container grouping users so apps and services can be enabled or disabled for a set of accounts at once.
Why A is correct
The policy needs two things at once: accounts that cannot be used, and data that survives for at least two years, at minimum cost. An Archived User is purpose-built for exactly that combination - the license is cheap, the account is disabled for sign-in so the person cannot access anything, and the mailbox and files remain in the account so Vault retention, holds and Drive content continue to be preserved and searchable. It is the only option that satisfies all three constraints simultaneously.
Why the others are wrong
B. Transferring files and deleting the account destroys the very data the policy says to preserve - deletion removes the mailbox, Drive content and chat history outright, and Vault holds cannot be honoured on a deleted account. Per-item Drive transfers also create exactly the management overhead you want to avoid.
C. Suspending the accounts preserves their data, but each suspended user still consumes a full paid license for two years, so it is strictly more expensive than the archived license with the same effect. It also leaves the accounts in a temporary rather than final leaver state.
D. Moving users to an organizational unit and turning off services for that OU is a blunt, broad control that only limits access to services - the accounts themselves remain active, sign-in is unaffected, and each still costs a full license. It does not implement a compliant leaver process.
AGWA exam tip
Leaving but keeping data equals Archived User. Suspended costs the same as active, deleting kills the data, and an OU only gates services.
5The 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.
Answer: D
The short version
D - Use a Vault matter, search the employee's mailbox within it and export the M&A emails, giving legal an audited chain of custody.
Key concepts
Vault matter and export: A matter scoped to the M&A matter, with an export action producing copies for authorized custodians.
Custodian roles and permissions: Roles granted in the matter control who can search, review, export and download; the Vault audit report records every export.
Chain of custody: The documented, auditable record of who accessed and exported data, required for evidence to be defensible in legal proceedings.
Mail delegation: Granting another mailbox full or restricted delegate access, which grants live access to the mailbox rather than producing a preserved export.
Indefinite retention: Data kept until explicitly removed, so the emails still exist and only need to be surfaced to the right party.
Why D is correct
Google built Vault as the sanctioned discovery tool, and the export path is the one that protects privacy while producing defensible evidence. A matter scoped to the M&A deal covers the employee's Gmail source, the search narrows to the relevant messages, and the export is performed by a role authorized for it - with every action written to the Vault audit report. That gives legal a documented chain of custody, leaves the employee on leave with the same mailbox protection as everyone else, and works regardless of the person's availability or the retention setting.
Why the others are wrong
A. Having IT log into the mailbox and forward messages produces no custody record, no matter scope and no audit trail, and unnecessarily exposes an employee's private mail to IT staff. Forwarded copies are not evidence of what was actually in the mailbox.
B. Gmail delegation is a live grant of access to a mailbox, and it cannot be scoped to 'only the M&A-related emails' - the grant is all-or-nothing at the mailbox level. It also yields no export record, and the indefinite retention setting is irrelevant to someone browsing the mailbox directly.
C. A colleague with delegate access forwarding messages has the same defects as the direct IT approach: manual forwarding outside Vault, no auditable custody chain, and possible contamination or alteration of the evidence.
AGWA exam tip
Privacy-safe discovery always runs through Vault: matter, scoped search, authorized export, audit trail. Manual forwarding or mailbox delegation leaves no defensible custody.
6Your company distributes an internal newsletter that contains sensitive information to all employees by email. You’ve noticed unauthorized forwarding of this newsletter to external addresses, potentially leading to data leaks. To prevent this, you need to implement a solution that automatically detects and blocks such forwarding while allowing legitimate internal sharing. What should you do?
Add a banner to the newsletter that warns users that external sharing is prohibited.
Create a Gmail content compliance rule that targets the internal newsletter, identifying instances of external forwarding. Configure the rule to reject the message when such forwarding is detected
Develop an Apps Script project by using the Gmail API to scan sent emails for the newsletter content and external recipients. Automatically revoke access for violating users.
Create a content compliance rule to modify the newsletter subject line, adding a warning against external forwarding.
Answer: B
The short version
B - A Gmail content compliance rule that matches the newsletter going to a recipient outside the organization and rejects the message.
Key concepts
Content compliance rule: A domain-wide Gmail rule created in Admin console > Apps > Google Workspace > Gmail settings that inspects messages and applies an action.
Content conditions: Predicates such as 'has the words' or 'includes header' used to identify the specific newsletter content.
Recipient condition: 'Recipient is outside your organization', which separates legitimate internal distribution from an external leak.
Action - reject: Blocks the message before delivery and returns a delivery failure notice to the sender; 'quarantine' instead diverts it for admin review.
Pre-delivery enforcement: The rule is applied at SMTP time on the sender's own domain, so it acts before the message reaches the external recipient.
Why B is correct
The requirement is automatic detection and blocking while internal sharing keeps working, and that is precisely what a content compliance rule does. Its conditions combine 'has the words' with the newsletter's distinctive text and 'recipient is outside your organization'; because the rule runs on the sending side as the message is submitted, the reject action stops delivery and returns a failure to the sender, while messages to internal addresses match no rule and flow normally. The action is also written to the audit log and usable by DLP/archiving schemas, giving the security team a record of every attempt.
Why the others are wrong
A. A banner is a passive reminder with no enforcement. Users who disregard the warning still forward the newsletter, and nothing prevents the disclosure, so it fails the 'automatically detects and blocks' requirement.
C. An Apps Script using the Gmail API runs after the fact and can only inspect messages that have already left the tenant - it cannot recall them. Automatically revoking a user's access is also a different goal from blocking a message and would be disruptive.
D. Modifying the subject line still delivers the newsletter to external recipients, so the leak is not prevented; it also breaks any subject-based label or DLP matching and confuses recipients receiving the altered mail.
AGWA exam tip
To stop a leak you must act before delivery, from inside the tenant: content compliance rule with an outside-recipient condition and the reject action.
7Your organization has hired temporary employees to work on a sensitive internal project. You need to ensure that the sensitive project data in Google Drive is limited to only internal domain sharing. You do not want to be overly restrictive. What should you do?
Configure the Drive sharing options for the domain to internal only.
Restrict the Drive sharing options for the domain to allowlisted domains.
Create a Drive DLP rule, and use the sensitive internal Project name as the detector.
Turn off the Drive sharing setting from the Team dashboard.
Answer: C
The short version
C - Create a Drive DLP rule keyed on the sensitive project name, with an action that blocks sharing outside the domain.
Key concepts
Drive DLP rule: A rule in Admin console > Drive > Data loss prevention that matches Drive content and applies an action to it.
Detector: What identifies the sensitive content - a predefined Drive detector, a sensitive content label, or a custom regex detector such as the project name.
Action: Block sharing outside the domain, warn the user, apply a label, require review, or audit only.
Domain-wide sharing settings: The global Drive settings controlling who in the domain can share at all, which apply to every user's content.
Organizational unit scoping: Applying rules or app access to a subset of users rather than the entire domain.
Why C is correct
The requirement is precise: this project's data must stay inside the domain, but the rest of the organization must not be restricted. A Drive DLP rule matches on content - here a custom detector built from the sensitive project name, or a sensitive label applied to the project's files - and then applies a targeted action such as blocking sharing outside the domain. Because the rule keys on content rather than on users, exactly the project's Drive data is constrained and everything else behaves normally, which is what 'not overly restrictive' requires.
Why the others are wrong
A. Setting domain-wide sharing to internal only applies to every Drive item belonging to every user in the organization. That is precisely the over-restriction the scenario tells you to avoid, and it would break legitimate external collaboration elsewhere.
B. Allowlisting domains does the opposite of what is required - it explicitly permits sharing out to the named external domains. The requirement is to limit sharing to the internal domain, not to open a list of outside destinations.
D. The Team dashboard has no Drive sharing control - it reports on adoption and activity. Drive sharing behavior is governed by Drive settings, DLP rules and OU-level app access, so the described control does not exist.
AGWA exam tip
Granular beats global in DLP: match the specific content with a detector and block external sharing, rather than locking sharing down for the whole domain.
8Several employees at your company received messages with links to malicious websites. The messages appear to have been sent by your company’s human resources department. You need to identify which users received the emails and prevent a recurrence of similar incidents in the future. What should you do?
Search the sender’s email address by using Email Log Search. Identify the users that received the messages. Instruct them to mark them as spam in Gmail, delete the messages, and empty the trash.
Search for the sender’s email address by using the security investigation tool. Mark the messages as phishing. Add the sender’s email address to the Blocked senders list in the Spam, Phishing and Malware setting in Gmail to automatically reject future messages.
Collect a list of users who received the messages. Search the recipients’ email addresses in Google Vault. Export and download the malicious emails in PST file format. Add the sender’s email address to a quarantine list setting in Gmail to quarantine any future emails from the sender.
Search for the sender’s email address by using the security investigation tool. Delete the messages. Turn on the safety options for spoofing and authentication protection in Gmail settings.
Answer: D
The short version
D - Investigate with the security investigation tool to remove the messages, then enable Gmail's spoofing and authentication protection.
Key concepts
Security investigation tool: The Alert center view showing a prioritized security event, who received the message and the recommended actions to remediate it.
Recommended actions: One-click remediation such as removing similar messages from all affected mailboxes or marking the messages as phishing across the domain.
Spoofing and authentication protection: A Gmail setting that checks SPF, DKIM and DMARC alignment and filters or rejects messages that fail those checks.
Blocked senders: A Gmail control that routes mail from specific addresses to spam; it cannot be used against your own domain.
Email Log Search: A tool for SMTP delivery metadata - status, recipients, response codes - which does not remove content from mailboxes.
Why D is correct
Two separate objectives are in play: remediate what already landed, and stop it recurring. The security investigation tool supplies both halves of the first - it shows that the bulk message was delivered and to which users, and its recommended actions purge similar copies from every affected mailbox instantly. For the second, the giveaway is that the messages appear to come from your own HR department, which means the sender address is being forged or a lookalike domain is in use; turning on spoofing and authentication protection makes Gmail evaluate SPF/DKIM/DMARC alignment and filter messages that fail it, addressing the actual mechanism rather than the visible symptom.
Why the others are wrong
A. Email Log Search returns SMTP delivery metadata such as status, recipient and response codes for a given message; it cannot delete anything from user mailboxes. Asking each user to mark spam, delete and empty trash is a reactive, incomplete cleanup that leaves other copies in place.
B. Gmail has no reject-style blocked-senders list inside the Spam, Phishing and Malware settings for a Workspace domain, and the spoofed sender uses your own domain address, which can never be blocked. Blocking an address does not address the underlying spoofing behavior.
C. There is no quarantine-list setting in Gmail; quarantine is a content compliance action, not a sender list. Using Vault to export malicious mail in PST format is an evidence-preservation workflow that prevents nothing and takes far longer than the incident warrants.
AGWA exam tip
A message appearing to come from inside your own domain is spoofing, not a stranger: investigate the alert, remove it once, then turn on authentication protection.
9Your organization’s users are reporting that a large volume of legitimate emails are being misidentified as spam in Gmail. You want to troubleshoot this problem while following Google-recommended practices. What should you do?
Adjust the organization’s mail content compliance settings in the Admin console.
Advise users to individually allowlist senders.
Disable spam filtering for all users.
Contact Google Workspace support and report a suspected system-wide spam filter malfunction.
Answer: A
The short version
A - Tune the organization's mail content compliance settings, which is where Gmail's spam filtering behavior is centrally controlled.
Key concepts
Mail content compliance settings: The Admin console control under Apps > Google Workspace > Gmail settings that governs how Gmail treats this domain's mail.
Sender allowlist / blocklist: Entries that exempt trusted senders from spam filtering or force mail from specified senders into spam.
Content matching settings: Rules defining which words, phrases or headers trigger the configured spam actions.
Spam filtering thresholds: Google's classification settings that decide what lands in users' spam folders.
Per-user settings: Individual allowlisting done by users in their own Gmail settings, which is non-scalable and outside administrative oversight.
Why A is correct
Legitimate mail landing in spam is overwhelmingly a configuration outcome: a partner or application sender has been classified as spam, or its content trips the filters. The supported fix is to change that configuration centrally in Gmail settings > Content compliance - allowlist the affected senders, adjust content-matching rules and spam thresholds - which takes effect for every user at once and is what Google's own guidance recommends as the first step. Because the setting is domain-wide, one change fixes the reports from every user who was seeing the same symptom.
Why the others are wrong
B. Telling users to allowlist senders in their personal Gmail settings works one user at a time, depends on each user noticing and knowing how to do it, and leaves no central record of the exception. It is a temporary mitigation, not a fix, and is not scalable across the organization.
C. Disabling spam filtering removes an important security control for the entire domain, and legitimate spam and phishing would flood inboxes as a result. Weakening a security control to compensate for a misconfiguration trades one risk for a much larger one.
D. Support cannot retune your filters or adjust your compliance settings; spam misclassification is almost always driven by local configuration. Contacting support is appropriate only after the domain-side settings have been reviewed and a genuine platform malfunction is suspected.
AGWA exam tip
Fix spam classification where it is configured, not where users complain: Admin console > Gmail settings > Content compliance, one change for the whole domain.
10Your organization’s security team has published a list of vetted third-party apps and extensions that can be used by employees. All other apps are prohibited unless a business case is presented and approved. The Chrome Web Store policy applied at the top-level organization allows all apps and extensions with an admin blocklist. You need to disable any unapproved apps that have already been installed and prevent employees from installing unapproved apps. What should you do?
Change the Chrome Web Store allow/block mode setting to allow all apps, admin manages blocklist, In the App access control card, block any existing web app that is not on the security team’s vetted list.
Change the Chrome Web Store allow/block mode setting to block all apps, admin manages allowlist. Add the apps on the security team’s vetted list to the allowlist.
Disable Extensions and Chrome packaged apps as Allowed types of apps and extensions for the top-level organizational unit. Selectively enable the appropriate extension types for each suborganization
Disable the Chrome Web Store service for the top-level organizational unit. Enable the Chrome Web Store service for organizations that require Chrome apps and extensions.
Answer: B
The short version
B - Switch the Chrome Web Store policy to block all apps with an admin-managed allowlist, then add the vetted apps to it.
Key concepts
Chrome Web Store allow/block mode: The top-level policy with options to block everything except an admin-maintained allowlist, or to allow everything except an admin-maintained blocklist.
Admin-managed allowlist: The list of apps and extensions users are permitted to install once everything else is blocked.
Admin-managed blocklist: The list of items forbidden while everything else remains installable by default.
App access control card: The OU-level panel where specific web apps and extensions can be allowed or blocked for that organizational unit.
Allowed types of apps and extensions: The OU setting choosing which classes of extension, such as packaged apps or Chrome extensions, may run at all.
Why B is correct
The requirement is default-deny with named exceptions: only vetted items are permitted, everything else is prohibited. Setting the Chrome Web Store policy to block all apps and extensions with an admin-managed allowlist enforces exactly that - any app not on the allowlist is blocked, so the already-installed unapproved items stop working immediately and no new unapproved install can succeed. Putting the security team's vetted apps on the allowlist keeps the approved tools available, satisfying both halves of the requirement with a single policy change.
Why the others are wrong
A. Allow all with an admin-managed blocklist is the mode already in place, and it cannot meet the requirement in either direction. Under default-allow, an unapproved app that is not yet on the blocklist installs and runs, so it does not prevent unapproved installs, and blocking existing ones only happens for items somebody remembered to list.
C. Disabling extensions and packaged apps as allowed types for the top-level OU removes whole classes of extension by category. It cannot distinguish the vetted app from the unvetted one - neither is allowed - so it is the wrong granularity and does not implement an allowlist of approved items.
D. Turning off the Chrome Web Store service for the top-level OU would also block the security team's vetted apps, which must remain installable and usable. It is a blunt on/off switch rather than a policy that permits named, approved items.
AGWA exam tip
Default-deny plus named exceptions equals 'block all, admin manages allowlist'. Allow-all-plus-blocklist can never stop an app nobody has listed yet.