How the Associate Google Workspace Administrator exam works

Owen Mitchell has spent the autumn learning to run Birchline Outfitters' new Google Workspace tenant. In the first course he built the directory, the organizational units and the licence plan. In the second he configured Gmail, Drive, Calendar, Meet, Chat and Gemini. In the third he wrote the security baseline, planned 2-step verification, set up data loss prevention and Vault, and rehearsed an incident. Now Sofia Marchetti, the collaboration and identity lead who has mentored him through all three, books a small meeting room at the head office in Toronto and puts one document on the screen: the exam guide for the Associate Google Workspace Administrator certification.

"Everything you need is in what we have already done," she says. "This course is about turning it into a pass. That means knowing exactly what the exam measures, how it asks, how to pace yourself, and how to find the gaps you don't know you have." Owen's plan, which they write together in this first session, is to sit the exam in late May 2027, after the head office wave in February and the stores and warehouses in April. By then he will have run the tenant for real through two large migration waves, which is the kind of experience the exam assumes.

This is GCP-193, the final course of the Associate Google Workspace Administrator program on this site. GCP-210 covered users, organizational units, groups, domains and licensing. GCP-211 covered configuring the core services. GCP-212 covered security, data protection and troubleshooting. This course reviews all of that against the current exam guide, and adds what an exam needs that a job does not: registration and delivery, reading questions, timing, practice and the day itself.

What the certification says about you

Google Cloud groups its certifications in three levels. Foundational certifications check broad knowledge of what the cloud can do. Associate certifications check that a person can set up and run a service day to day. Professional certifications check design and leadership across larger environments. The Associate Google Workspace Administrator sits in the middle level. It says that the holder can manage the everyday running of a Workspace organization: user accounts, organizational units and groups, the core services, sharing and security settings, devices and browsers, and the troubleshooting that keeps people working.

The exam guide opens with a short description of the role. In our own words, it describes someone who keeps the environment running so that people can communicate and collaborate safely, who manages accounts and configures services such as Gmail and Drive, who protects the organization's data and keeps it compliant, and who resolves the problems that users bring. That description is worth reading slowly, because every question on the exam is written from that person's point of view. When an option is something a careful day-to-day administrator would do, it is usually closer to right than an option that is clever but risky.

The facts about the exam

Google's certification page for this exam lists the facts that matter for planning. We read the page in November 2026; Google changes these details from time to time, so check the page before you book.

For a Canadian candidate, the fee is quoted in US dollars. The registration system may show the amount converted to Canadian dollars with tax added at checkout, so the total Owen pays will be somewhat more than 125, depending on the exchange rate and the sales tax that applies in Ontario. He notes the amount on his plan as an estimate and checks the exact figure when he books.

Two of these facts shape how he studies. First, the recommended experience mentions Business Plus and Enterprise features. Birchline uses Enterprise Standard and Frontline Standard, so Owen must also know what other editions include and lack, because questions often turn on whether a feature is available at all. Second, there is no published passing score. Google reports results as pass or fail, and its support pages say numerical scores are not shared. That means there is no point aiming for a number; the only goal is to know the material well enough to pass with room to spare.

The six sections of the exam guide

The exam guide divides the exam into six sections, each with an approximate weight: the share of questions that section is likely to have. The weights are approximate, add up to about 100 and can change when Google revises the guide, but they are the best guide to where marks come from.

Each section is broken into numbered objectives. Section 2, for example, has separate objectives for Gmail, Drive and Docs, Calendar, Meet, Chat, generative AI, and development tools. Every objective lists the considerations it includes, such as MX records, content compliance rules or booking permissions. The guide is not a textbook, but it is a precise list of what can be asked. Owen prints it, and over the next sessions he will mark every consideration with one of three symbols: confident, unsure, or never seen.

How the sections map to the earlier courses

One section gets less attention in the earlier courses than its weight deserves. Chrome browser management, half of section 5, came up only in passing, because Birchline's laptops were already managed in other ways. Lesson 6 of this course fills that gap with the browser policies, enrollment and extension controls the guide lists. Owen writes it on his plan as a known gap before he has even started marking the guide.

Turning weights into expected questions

Weights become more useful when they are turned into numbers of questions. If an exam has 60 questions and a section's weight is about 20 in 100, that section will have about 12 of them. The exact count varies from one form of the exam to another, and some questions touch two sections at once, but the estimate tells Owen how much each section can lift or sink his result. A short calculation does it for both ends of the range.

# Approximate section weights from the exam guide (out of 100).
weights = {
    "1 Users, domains, directory": 20,
    "2 Core services": 23,
    "3 Data governance": 15,
    "4 Security and access": 20,
    "5 Browsers and endpoints": 10,
    "6 Troubleshooting": 13,
}
total = sum(weights.values())
print("Weights add up to", total)
for n_questions in (50, 60):
    print(f"\nOn a {n_questions}-question exam:")
    for section, w in weights.items():
        expected = n_questions * w / total
        print(f"  {section:30s} about {expected:4.1f} questions")

Weights add up to 101

On a 50-question exam:
  1 Users, domains, directory    about  9.9 questions
  2 Core services                about 11.4 questions
  3 Data governance              about  7.4 questions
  4 Security and access          about  9.9 questions
  5 Browsers and endpoints       about  5.0 questions
  6 Troubleshooting              about  6.4 questions

On a 60-question exam:
  1 Users, domains, directory    about 11.9 questions
  2 Core services                about 13.7 questions
  3 Data governance              about  8.9 questions
  4 Security and access          about 11.9 questions
  5 Browsers and endpoints       about  5.9 questions
  6 Troubleshooting              about  7.7 questions

The weights add up to 101 because each was rounded, so the program divides by the real total rather than 100. On a 60-question exam, core services contribute about 14 questions, users and security about 12 each, data governance about 9, troubleshooting about 8 and browsers and endpoints about 6. The three largest sections together are worth roughly 37 or 38 questions out of 60. Owen draws the obvious conclusion: no section can be skipped, but a weak spot in sections 1, 2 or 4 costs about twice as much as one in section 5.

What kind of questions to expect

All questions are multiple choice or multiple select. Most are short scenarios: a few sentences about an organization, a goal or a problem, and a question about what the administrator should do. Some ask for the first step, some for the best option, and some for the option that meets a constraint such as least administrative effort or no effect on other users. Multiple select questions say how many answers to choose. Lesson 3 is devoted to reading these questions well, because many wrong answers come from misreading a single word rather than from not knowing the material.

Google also publishes a small set of sample questions linked from the certification page. They are not a practice exam, and they are not scored for the real thing, but they show the style. Sofia asks Owen not to open them yet. "Save them for a check later," she says. "If you see them now, you'll remember the answers, and they'll tell you nothing."

What a pass does and does not require

The exam does not require memorizing every menu path in the Admin console. It does require knowing where a setting lives in the structure of the console, which organizational unit or group it applies to, which edition includes it, and what it does to users. A question might describe sharing failures in a shared drive and ask why; the answer depends on knowing that a shared drive follows its own organizational unit's settings, not on the exact name of a menu. Another might ask how to give a few users access to a feature without giving it to everyone; the answer is a configuration group or a child organizational unit, a pattern that runs through the whole Admin console.

Owen finds that reassuring. Most of the material is patterns, and he has used the patterns every week since October. Sofia adds one caution: the exam is written about Workspace in general, not about Birchline. Birchline made particular choices, such as keeping Exchange as the primary mail system during the migration and using Google as the identity provider. Other organizations make other choices, and the exam expects him to know the options and when each fits.

Building the first study plan

Before ending the session, they write the first version of the plan. It will change, but writing it now makes the next six months concrete.

The exam date falls on the Tuesday after the Victoria Day long weekend. Sofia points out that a long weekend just before an exam is a gift if Owen rests, and a trap if he spends it cramming. He keeps the date.