Home / cloud-computing / Google Cloud Certified Associate Google Workspace Administrator / Cheat Sheet
Google Cloud Certified Associate Google Workspace Administrator

Workspace Admin Cheat Sheet

Workspace Admin Tests the Narrowest Admin Console Fix — Not Org-Wide Toggles

This Associate exam replaced the Professional Workspace Administrator exam, retired 31 December 2024. It suits hands-on admins; the shift is scoping every change to the right OU or group while protecting data first.

Check Your Readiness →
Among the harder certs
Avg: Not published by Google
Pass: 750 / 1000
Most candidates understand Google Cloud Certified Associate Google Workspace Administrator concepts — and still fail. This exam tests how you apply knowledge under pressure.

Associate Workspace Administrator Section Map

Questions read like help-desk tickets and change requests. Several options are real settings placed in the wrong service or at the wrong scope. Google's published weights round to about 101%. Favour the option that preserves data, uses least privilege and touches the smallest population.

  1. 01
    Core Workspace services (~23%) — Gmail routing and SPF/DKIM/DMARC, Drive sharing, Calendar, Meet, Chat history, Gemini, AppSheet
  2. 02
    Users, domains and Directory (~20%) — leaver handling, OU design, configuration groups, domain aliases, GCDS and Directory Sync
  3. 03
    Security policies and access (~20%) — 2SV rollout, scoped admin roles, investigation tool, alert center, API controls
  4. 04
    Data governance and compliance (~15%) — Vault holds vs. retention, DLP, Drive trust rules, exports, data regions, labels
  5. 05
    Monitoring and troubleshooting (~13%) — audit logs, Email Log Search, Messageheader, restore windows, support evidence
  6. 06
    Browsers and endpoints (~10%) — basic vs. advanced mobile management, account vs. device wipe, Chrome enrollment

Wrong instinct vs correct approach

Five people in different departments need one Drive setting changed while keeping their departmental settings
✕ Wrong instinct

Create a new OU and move all five users into it

✓ Correct approach

A user belongs to exactly one OU, so moving them drops their other inherited settings. A configuration group targets the exception across OUs, and group-based settings take precedence over OU settings for that service.

A financial firm must block external sharing of Drive files containing account numbers and tell users why
✕ Wrong instinct

Write a Gmail content compliance rule or a Drive trust rule

✓ Correct approach

This is content-based, so use a DLP rule with the relevant detector, scoped to external sharing, with a block action and user message. Run it in audit mode first; trust rules act on who shares with whom.

A phishing email reached 400 Enterprise Plus users an hour ago and some clicked the link
✕ Wrong instinct

Check the security health page and email users to delete it

✓ Correct approach

The security investigation tool queries Gmail log events, identifies recipients and clickers, and bulk-deletes the message from every inbox. Security health shows configuration posture only, not individual incidents.

A customer says a message sent yesterday never reached the manager, not even in spam
✕ Wrong instinct

Ask the manager to forward the message headers to IT

✓ Correct approach

No received message means no header to analyse. Email Log Search traces delivery for roughly the last 30 days by sender, recipient or message ID. Messageheader in Admin Toolbox only helps once a message is in hand.

Know these cold

  • ▸ GCDS syncs one way from LDAP or Active Directory into Google; never back
  • ▸ Domain alias gives every user an extra address with no new accounts; secondary domain creates separate identities
  • ▸ Collaborative Inbox is enabled on a group, not by delegating one person's mailbox
  • ▸ Room booking rights come from resource calendar sharing, not from OU settings
  • ▸ Inbound mail failing after migration means MX records; SPF only affects how others judge outbound
  • ▸ Configure an inbound gateway for upstream filters; never allowlist the gateway IP in spam settings
  • ▸ Hold beats retention rule; Vault covers only accounts that still exist
  • ▸ Takeout is per-user self-service, Data Export is whole-tenant, Vault export is per matter
  • ▸ Deleted user restore about 20 days; admin Drive and Gmail data restore about 25 days
  • ▸ Enforce 2SV with an enrollment period; passkeys or security keys for admins, never SMS

Can you answer these without checking your notes?

In this scenario: "Five people in different departments need one Drive setting changed while keeping their departmental settings" — what should you do first?
A user belongs to exactly one OU, so moving them drops their other inherited settings. A configuration group targets the exception across OUs, and group-based settings take precedence over OU settings for that service.
In this scenario: "A financial firm must block external sharing of Drive files containing account numbers and tell users why" — what should you do first?
This is content-based, so use a DLP rule with the relevant detector, scoped to external sharing, with a block action and user message. Run it in audit mode first; trust rules act on who shares with whom.
In this scenario: "A phishing email reached 400 Enterprise Plus users an hour ago and some clicked the link" — what should you do first?
The security investigation tool queries Gmail log events, identifies recipients and clickers, and bulk-deletes the message from every inbox. Security health shows configuration posture only, not individual incidents.

Common Exam Mistakes — What candidates get wrong

Deleting a leaver's account before transferring Drive files or archiving

Deletion ends Vault coverage and removes unowned Drive files after the roughly 20-day account restore window. Transfer ownership first, then move the account to an Archived User license so mail stays searchable in Vault at lower cost.

Using a retention rule to preserve evidence for a named lawsuit

Retention rules purge at the end of their period and can be edited. Create a Vault matter and place a hold on the named accounts or OUs; holds override retention, but they do not survive deletion of the account.

Publishing the DKIM record but never clicking Start authentication

DKIM is generated in the Admin console, published as DNS TXT, then switched on. Also list every third-party sender in SPF, and move DMARC from p=none to quarantine or reject only after reports confirm legitimate mail aligns.

Making a regional IT lead super admin for routine password resets

Super admin cannot be scoped to an OU. Prebuilt roles such as Help Desk Admin or User Management Admin, or a custom role, can be limited to one OU. Keep more than one protected super admin with secured recovery.

Running a full device wipe on an employee's personal phone

Account wipe removes only Workspace data, or the Android work profile, and leaves personal content. Device wipe is a factory reset for lost company-owned devices, and device approval or app control needs advanced, not basic, management.

Resources to help you pass Google Workspace Administrator on your first attempt

Test whether you pick the right Admin console tool and scope for each Workspace ticket.