Google Professional Workspace Administrator

The Google Professional Workspace Administrator exam has been created for professionals who are in charge of translating corporate goals into actionable configurations, rules, and security procedures pertaining to users, content, and integrations. For workers to collaborate, communicate, and access data in a safe and efficient way, Google Workspace Administrators must also have a full understanding of the architecture of the company.

Target Audience

• IT Systems Administrator
• Cloud Solutions Engineer
• Enterprise Google Workspace Administrator
• Systems Engineer

Recommended experience

3+ years of expertise in the field, including 1+ years of Google Workspace (formerly G Suite) management.

Exam Overview

Exam Registration

a) Attend the online exam from a distant location. Review the prerequisites for the online test.

b) Take the exam at a testing facility with on-site proctoring. Find a testing location close to you.

For more information, click on Google Professional Workspace Administrator FAQ.

Recertification Policy

To keep their certification status, candidates must recertify. All Google Cloud certificates are valid for two years from the date of certification, unless otherwise specified in the thorough test descriptions. By retaking the exam and receiving a passing score during the eligibility period for recertification, you can become certified again. Starting 60 days before the expiration of your certification, you may try to recertify.

Course Outline for Google Professional Workspace Administrator

Section 1: Managing objects (20%)

1.1 Managing account lifecycles by using provisioning and deprovisioning processes. Considerations include:

• Transferring ownership data to another account (Google Documentation: How to transfer file ownership)
• Provisioning users based on a process determined by an organization’s policy (for example, where to list accounts) (Google Documentation: Organization policy constraints)
• Provisioning and deprovisioning accounts, including:
  • Creating, reviewing, updating, deleting accounts (CRUD [create, read, update, and delete] operations). (Google Documentation: Perform CRUD operations on a MySQL database)
  • Adding users (for example, individual, bulk, and automated) (Google Documentation: Add or update multiple users from a CSV file)
  • Offboarding accounts (for example, suspending, deleting, and recovering)
  • Editing user attributes (for example, renaming, passwords, and aliases) (Google Documentation: Admin settings – User attributes)
  • Creating administrative roles (for example, default roles, and custom roles) (Google Documentation: Create and manage custom roles)
• Revoking account access outside of a typical organizational policy (for example, security reasons and personnel issues) (Google Documentation: Revoke access to a Google Cloud project)
• Configuring, monitoring, troubleshooting, and updating lifecycle management by using Google Cloud Directory Sync (GCDS) (Google Documentation: About Google Cloud Directory Sync)
  • Auditing and reviewing GCDS (for example, interpreting log data)

1.2 Configuring Google Drive. Consideration include:

• Managing the lifecycle of shared drives based on user requests and organizational policies (for example, OU [organizational unit] placements)
• Configuring shared drive permissions, given specific requirements or scenarios (Google Documentation: Set up shared drives for your organization)
• Implementing shared drive membership permissions based on organizational policies (Google Documentation: Manage data policies for specific shared drives)
• Transferring user data from one user’s drive to another drive (Google Documentation: How to transfer Drive files from one user to another)
• Applying security best practices for shared drives based on the business need (Google Documentation: Best practices and tips for shared drives)

1.3 Managing calendar and calendar resources. Considerations include:

• Creating and managing calendar resources (Google Documentation: Create buildings, features & Calendar resources)
• Managing and delegating calendar access and resources
• Managing the lifecycle of both individual and shared calendars (for example, differentiating between an individual’s calendar and a calendar resource) (Google Documentation: What is a Calendar resource?, Share room and resource calendars)
• Configuring Google video conference room options (for example, Jamboard, Google Meet) (Google Documentation: Manage Meet settings (for admins))
• Scheduling Google Meet conferences and livestream meetings or events (Google Documentation: Hold large remote events)
• Monitoring usage reports and recommending changes (Google Documentation: Monitor usage & security with reports)
• Troubleshooting calendar issues (Google Documentation: Google Workspace Known Issues)

1.4 Configuring and managing Groups for business. Considerations include:

    ●  Configuring memberships and advanced settings, including:

        ○  Adding users to groups (Google Documentation: Add people to your group)

        ○  Implementing current Google Workspace APIs

        ○  Automating tasks by using Apps Script (Google Documentation:  Automation quickstart)

    ●  Using a Google group to apply membership permissions for a shared drive

    ●  Creating specific types of Google-native groups (for example, dynamic, security, identity-mapped, and POSIX) (Google Documentation: Groups API overview)

    ●  Implementing Google group security access controls to restrict members (Google Documentation: Control access to sensitive data with security groups)

    ●  Troubleshooting issues in a Google group (for example, calendar invites not expanding, invites unable to be sent to a group)

Section 2: Configuring services (18%)

2.1 Implementing and managing Google Workspace configurations based on corporate policies. Considerations include:

    ●  Assigning and configuring permissions to Google Workspace tools by using organizational units (OUs) and Google groups (Google Documentation: How the organizational structure works)

    ●  Modifying OU policies (Google Documentation: Creating and managing organization policies)

    ●  Implementing application and security settings according to OU inheritance and override settings in parent OUs

    ●  Delegating granular Identify and Access Management (IAM) administrator roles and permissions to users in a domain (Google Documentation: Identity and Access Management (IAM))

    ●  Implementing security configuration options for installing or using Google Cloud Marketplace applications or add-ons (Google Documentation: Configure Security Command Center services)

    ●  Configuring Drive labels for data organization (Google Documentation: Create Drive labels for your organization)

    ●  Configuring a Rapid Release or Scheduled Release for feature releases (Google Documentation: Choose when users get new features)

    ●  Configuring Google Meet to align with corporate policies and requirements (Google Documentation: Manage Meet settings (for admins))

    ●  Creating and configuring security and data region settings (Google Documentation: Data regions: Choose a geographic location for your data)

    ●  Implementing security integration protocols and addressing questions and objections from users

    ●  Managing content compliance rules (Google Documentation: Advanced filtering with Content Compliance rules)

    ●  Investigating and remediating an issue by using Security Health Analytics check results (Google Documentation: Remediating Security Health Analytics findings)

2.2 Configuring Gmail. Considerations include:

    ●  Configuring basic mail routing scenarios for split delivery (Google Documentation: Set up Split Delivery with Google Workspace first)

    ●  Configuring a mail host (Google Documentation: Add mail servers for Gmail email routing)

    ●  Configuring end-user access to Gmail by using Google Workspace Sync for Microsoft Outlook (GWSMO) or email client (for example, POP, IMAP, Thunderbird, Outlook) (Google Documentation: Set up Gmail with a third-party email client)

    ●  Configuring POP and IMAP access to align with corporate policies and requirements (Google Documentation: Turn POP & IMAP on or off for users)

    ●  Configuring administrator access for mail forwarding by using advanced Gmail settings (for example, compliance rules, default routing, APIs) (Google Documentation: Add Gmail Routing settings)

    ●  Managing and understanding all available spam controls (for example, allowlist, denylist, inbound gateway, and IP allowlist) (Google Documentation: Allowlists, denylists, and approved senders)

    ●  Enabling email delegation for an OU (Google Documentation: Delegate a user’s email address)

    ●  Managing Gmail archives (Google Documentation: Archive former employee accounts)

Section 3: Troubleshooting (24%)

3.1 Troubleshooting mail delivery problems reported by users. Considerations include:

    ●  Determining whether user behavior or a broader issue (for example, rules, or Cloud Data Loss Prevention [DLP]) is causing an error (Google Documentation: Use Workspace DLP to prevent data loss)

    ●  Determining whether an issue is an expected behavior (for example, a missing attachment, or an attachment filter issue) (Google Documentation: Set up rules for basic email content filtering)

    ●  Auditing and reviewing mail flow structure and end-user actions to determine the root cause of delivery issues (Google Documentation: About the audit and investigation tool)

    ●  Analyzing message headers or email audit logs by using Google Workspace tools or security investigation tools (Google Documentation: About the security investigation tool)

    ●  Recommending and/or implementing an appropriate course of action related to mail delivery issues (for example, implementing mail policy changes) (Google Documentation: Email sender guidelines)

3.2 Troubleshooting and collecting logs and reports needed to engage with the support team. Considerations include:

    ●  Documenting steps taken by end user to reproduce an issue (Google Documentation: Manage Approvals)

    ●  Collecting appropriate log file types (Google Documentation: Drive log events, Collect Google Workspace logs)

    ●  Searching for known issues and application status (Google Documentation: Google Workspace Known Issues)

    ●  Generating HAR files

3.3 Identifying, classifying, troubleshooting, and mitigating basic email attacks. Considerations Include:

    ●  Configuring:

        ○  Blocked senders (Google Documentation: How to block or mark suspicious email as spam)

        ○  Email allowlist (Google Documentation: How to add an IP address to allowlist)

        ○  Objectionable content (Google Documentation: Control message delivery based on message content)

        ○  Phishing settings (Google Documentation: Advanced phishing and malware protection)

        ○  Spam settings (Google Documentation: How to customize spam settings on Google Workspace)

        ○  Gmail safety settings

        ○  Administrator quarantine (Google Documentation: Set up email quarantine)

        ○  Attachment compliance

        ○  Secure transport compliance (Google Documentation: Send email over a secure TLS connection)

     ●  Implementing Sender Policy Framework (SPF); Domain-based Message Authentication, Reporting, and Conformance (DMARC); Mail Transfer Agent Strict Transport Security (MTA-STS); and DomainKeys Identified Mail (DKIM) to secure email transmission (Google Documentation: Help prevent spoofing and spam with DMARC, About MTA-STS and TLS reporting)

    ●  Investigating whether custom configurations are responsible for any issues or vulnerability (for example, email allowlist and IP addresses) (Google Documentation: Allowlists, denylists, and approved senders)

    ●  Investigating the scope of email attacks by using available Google Workspace email tools (Google Documentation: Investigate reports of malicious emails)

    ●  Analyzing message contents for common attack patterns (for example, name, domain, and brand spoofing) (Google Documentation: Spoofing report)

    ●  Mitigating successful attacks and preventing future attacks by using Google Workspace email tools (for example, identifying the issue and responding)

3.4 Troubleshooting Google Workspace access and performance issues. Considerations include:

    ●  Identifying why a user is having an issue when they access a single Google application (for example, Drive) (Google Documentation: Troubleshoot shared drives for your users)

    ●  Identifying the root cause of a performance issue when accessing a Google Workspace application (for example, a known issue, an outage, a network, or a device) (Google Documentation: Google Workspace Known Issues)

    ●  Analyzing, evaluating, and modifying settings to ensure delivery of critical emails (for example, specific IP ranges, X-headers)

    ●  Troubleshooting authentication issues that users reported (Google Documentation: Troubleshoot login challenges, 2-Step Verification, & sign-in issues)

    ●  Troubleshooting issues that users reported when they set up Google Workspace on a mobile device 

    ●  Troubleshooting Google Meet video call issues from the administrator console (Google Documentation: Unable to start Google Meet sessions)

    ●  Troubleshooting Google Meet device issues by using the administrator console (Google Documentation: Manage Meet settings (for admins))

    ●  Troubleshooting network configuration issues to ensure high-quality meetings by using Google Meet (Google Documentation: Prepare your network for Meet meetings & live streams)

    ●  Troubleshooting Jamboards (Google Documentation: Troubleshoot Jamboard device)

    ●  Troubleshooting access to Google Workspace services (for example, Gmail and Drive) (Google Documentation: Troubleshoot shared drives for your users)

    ●  Troubleshooting data visibility issues by enabling/disabling licenses or services

    ●  Investigating access issues in applications for OUs (Google Documentation: About the security investigation tool)

    ●  Interpreting and responding to alerts in the Alert Center API (Google Documentation: Google Workspace Alert Center API)

Section 4: Data access and authentication (24%)

4.1 Configuring policies for all devices (for example, mobile device, desktop, Chrome OS, Google Meet Hardware, Jamboard, Google Voice, and browser). Considerations include:

    ●  Configuring:

        ○  Chrome user and browser policy settings (Google Documentation: How to activate user-level policies for Chrome)

        ○  ChromeOS device policy settings (for example, Enterprise) (Google Documentation: How to set policies for ChromeOS devices)

        ○  Windows 10 login and device policies (for example, Google Credential Provider for Windows (GCPW)

        ○  Managed Chrome browsers (for example, Chrome Browser Cloud Management) (Google Documentation: Chrome Browser Cloud Management)

        ○  Basic device management (Google Documentation: Set up basic mobile device management)

        ○  Basic and advanced device management for Android and iOS (Google Documentation: Set up advanced mobile management)

        ○  Company-owned device management for Android and iOS (Google Documentation: Set up company-owned iOS device management)

        ○  Context-aware access policies (Google Documentation: About Context-Aware Access)

        ○  Personal device settings for Android and iOS (for example, password, advanced, device approvals, application management, and insights) (Google Documentation: Apply settings for Android mobile devices)

    ●  Enabling Endpoint Verification security by using BeyondCorp (Google Documentation: Endpoint Verification overview)

4.2 Configuring and implementing Gmail DLP and sharing access control lists (ACLs) based on governance policies. Considerations include:

    ●  Identifying areas of improvement for secure collaboration based on data exfiltration reports (Google Documentation: Security checklist for medium and large businesses (100+ users))

    ●  Scanning emails by using Gmail DLP (Google Documentation: Scan your email traffic using DLP rules)

    ●  Implementing Gmail DLP policies to prevent the over-sharing of sensitive data

    ●  Configuring and implementing Gmail DLP options for data classification (Google Documentation: Use Workspace DLP to prevent data loss)

    ●  Configuring and implementing data classification settings on Drive (Google Documentation: Label Google Drive files automatically using AI classification)

    ●  Implementing context-aware access policies based on data governance policies (Google Documentation: Protect your business with Context-Aware Access)

    ●  Configuring settings to limit external sharing on Drive based on organizational policies (Google Documentation: Manage external sharing for your organization)

    ●  Configuring settings to limit email delivery based on organizational policies (Google Documentation: Restrict email messages to authorized addresses or domains only)

    ●  Configuring and implementing client-side encryption services for Drive (Google Documentation: Turn client-side encryption on or off)

4.3 Managing third-party applications. Considerations include: 

    ●  Implementing automatic releases of a browser extension to OUs within the domain (Google Documentation: Automatically install apps and extensions)

    ●  Implementing security configuration options for installing or using Google Cloud Marketplace applications or add-ons

    ●  Reviewing and authorizing user requests for a new Google Workspace Marketplace application, Google Play, or a Chrome extension (Google Documentation: App review process and requirements for the Google Workspace Marketplace)

    ●  Pushing an application to a user’s phone by using Google’s mobile device management (MDM)

    ●  Configuring Google as a Security Assertion Markup Language (SAML) provider for a third-party application (Google Documentation: Set up your own custom SAML app)

    ●  Deploying password-vaulted apps (Google Documentation: Add apps to the password vaulted apps service)

    ●  Deploying and restricting Google Workspace Marketplace and Google Play Store applications (Google Documentation: Set whether users can install Marketplace apps)

    ●  Granting API access to applications (Google Documentation: Granting and revoking access to the API)

    ●  Integrating third-party user provisions (Google Documentation: Set up third-party partner integrations)

    ●  Integrating third-party marketplace applications to specific OUs in Google Workspace (Google Documentation: Integrate 3rd-party apps with Google Workspace)

    ●  Managing access to additional Google services (for example, AdSense and YouTube) for a specific set of users

    ●  Revoking third-party author access

    ●  Removing connected applications and sites (Google Documentation: Authorization for Google Services)

4.4 Configuring user authentication. Considerations include:

    ●  Configuring:

        ○  2-step Verification for the administrator and high-risk accounts (for example, requiring a physical key or not allowing SMS) (Google Documentation: Deploy 2-Step Verification)

        ○  2-step Verification for low-risk and standard accounts (for example, Google Authenticator) (Google Documentation: Protect your business with 2-Step Verification)

        ○  Google-side connection to third-party single sign-on (SSO) providers

        ○  Google Multi-IdP options for SSO

        ○  Basic SAML SSO configuration for third-party application authentication when Google is the SSO provider (Google Documentation: Set up SSO for your organization)

        ○  Third-party SSO for Google Workspace

        ○  Access control based on the use of the security functionality within API Controls (Google Documentation: Control API access with domain-wide delegation)

        ○  Google session control based on a company’s legal policies (Google Documentation: Set session length for Google services)

    ●  Implementing basic user security controls (for example, password length enforcement) (Google Documentation: Enforce and monitor password requirements for users)

    ●  Implementing security aspects of identity management, perimeter security, and data protection

Section 5: Supporting business initiatives (14%)

5.1 Using Vault to support legal initiatives. Considerations Include:

    ●  Configuring retention rules based legal security policies (for example, setting retention rules, placing legal holds, exporting data for additional processing and review, auditing reports, and searching a domain’s data by user account, OU, date, or keyword) (Google Documentation: How retention works, Manage retention rules and holds)

    ●  Assisting with or creating:

        ○  Legal matters to hold data (Google Documentation: Place Drive, Meet, and Sites data on hold)

        ○  Export matter content (data) for analysis (Google Documentation: Get started with Vault search and export)

        ○  Delegation protocols for Vault access (Google Documentation: Set up Vault privileges)

        ○  Google Workspace content by using Vault (searching)

        ○  Legal holds for Google Workspace content by using Vault

        ○  Vault audit reports (running) (Google Documentation: Vault log events)

5.2 Creating and interpreting reports for the business. Considerations include:

    ●  Generating and interpreting user adoption reports (for example, Work Insights) (Google Documentation: Understand users’ Google Workspace adoption)

    ●  Investigating issues by using the Alert Center (Google Documentation: About the alert center)

    ●  Investigating and monitoring a service outage for a specific Google Workspace application (Google Documentation: Check the status of a Google Workspace service)

    ●  Investigating issues by using data objects and metrics available within activity reports (Google Documentation: Monitor usage & security with reports)

    ●  Configuring group alerts triggered by a specific event (Google Documentation: Configure alert center email notifications)

    ●  Creating and reviewing audit logs (Google Documentation: Audit Logging)

    ●  Using BigQuery to combine multiple Google Workspace logs and usage reports to provide actionable insights (Google Documentation: About reporting logs and BigQuery)

5.3 Supporting data import and export. Considerations include:

    ●  Assisting with off-boarding employees and transferring data (for example, Drive, Calendar, and Google Data Studio)

    ●  Migrating Gmail data between Google Workspace accounts (Google Documentation: Migrate email with the data migration service)

    ●  Exporting data from Google Workspace offline or to other platforms (Google Documentation: Export all your organization’s data)

Preparation Guide: Google Professional Workspace Administrator

It takes a lot of effort, focus, and knowledge of the many domains to pass the Google Professional Workspace Administrator Exam. With the help of this study guide, you will have access to all the necessary material and test details. This is a well-structured study manual to help you get ready for the test.

Review the Exam Objectives

The most important and initial step is to visit the official Google Adwords Advertising Fundamentals website before you start your preparation. The candidates should receive the necessary details and important exam instructions from this. Candidates can use this website to get all the accurate, up-to-date information they need about the exam.

The following crucial action is to thoroughly evaluate the course goals. The applicants should thoroughly research and learn each domain. This will help you comprehend the subject matter of each chapter and make appropriate plans. Candidates must work shrewdly in order to pass this exam, which necessitates a complete comprehension of the course content.

Join Study Groups

This phase is sometimes skipped or undervalued by candidates, yet it is typically one of the expert advice you will get from any previous successful candidate. A candidate must sign up for a specific group or online discussion forum that focuses on google AdWords. This is accessible online; all that is needed is exploration and participation in the most appropriate forum. It offers many advantages. To increase your knowledge and maintain attention, you can participate in group discussions, brainstorming sessions, and other interactive activities. This can help you boost your confidence and become used to the exam standards.

Practice Test Papers

Here is the essential tool for a candidate’s preparation process. This will give you more self-assurance and make it easier for you to become accustomed to the exam’s real questions. Furthermore, it will aid in your self-evaluation and produce superior outcomes. The applicants can concentrate on their areas of weakness while also being aware of their areas of strength. There is no such thing as taking an adequate number of practise exams. You get better the more you practise. Take a free practice exam right away to see for yourself, and don’t pass up this fantastic chance to develop yourself.