As a Professional Google Workspace Administrator, you will be required to translate business goals into tangible configurations, policies, and security practices for users, content, and integrations. Google Workspace Administrators also enable people to collaborate, communicate, and access data in a secure and efficient manner by understanding their organization’s infrastructure. They use tools, programming languages, and APIs to automate workflows while maintaining an engineering and solutions mindset.<\/p>\n\n\n\n
The Professional Google Workspace Administrator exam tests your knowledge of:<\/p>\n\n\n\n
Let us go through these objectives in detail – <\/p>\n\n\n\n
Below mentioned is the detailed course outline for the exam – <\/p>\n\n\n\n
1.1 Managing account lifecycles by using provisioning and deprovisioning processes. Considerations include:<\/p>\n\n\n\n
1.2 Configuring Google Drive. Consideration include:<\/p>\n\n\n\n
1.3 Managing calendar and calendar resources. Considerations include:<\/p>\n\n\n\n
1.4 Configuring and managing Groups for business. Considerations include:<\/p>\n\n\n\n
\u25cf Configuring memberships and advanced settings, including:<\/p>\n\n\n\n
\u25cb Adding users to groups (Google Documentation:<\/strong> Add people to your group<\/a>)<\/p>\n\n\n\n \u25cb Implementing current Google Workspace APIs<\/p>\n\n\n\n \u25cb Automating tasks by using Apps Script (Google Documentation:<\/strong> Automation quickstart<\/a>)<\/p>\n\n\n\n \u25cf Using a Google group to apply membership permissions for a shared drive<\/p>\n\n\n\n \u25cf Creating specific types of Google-native groups (for example, dynamic, security, identity-mapped, and POSIX) (Google Documentation:<\/strong> Groups API overview<\/a>)<\/p>\n\n\n\n \u25cf Implementing Google group security access controls to restrict members (Google Documentation:<\/strong> Control access to sensitive data with security groups<\/a>)<\/p>\n\n\n\n \u25cf Troubleshooting issues in a Google group (for example, calendar invites not expanding, invites unable to be sent to a group)<\/p>\n\n\n\n 2.1 Implementing and managing Google Workspace configurations based on corporate policies. Considerations include:<\/p>\n\n\n\n \u25cf Assigning and configuring permissions to Google Workspace tools by using organizational units (OUs) and Google groups (Google Documentation:<\/strong> How the organizational structure works<\/a>)<\/p>\n\n\n\n \u25cf Modifying OU policies (Google Documentation:<\/strong> Creating and managing organization policies<\/a>)<\/p>\n\n\n\n \u25cf Implementing application and security settings according to OU inheritance and override settings in parent OUs<\/p>\n\n\n\n \u25cf Delegating granular Identify and Access Management (IAM) administrator roles and permissions to users in a domain (Google Documentation:<\/strong> Identity and Access Management (IAM)<\/a>)<\/p>\n\n\n\n \u25cf Implementing security configuration options for installing or using Google Cloud Marketplace applications or add-ons (Google Documentation:<\/strong> Configure Security Command Center services<\/a>)<\/p>\n\n\n\n \u25cf Configuring Drive labels for data organization (Google Documentation:<\/strong> Create Drive labels for your organization<\/a>)<\/p>\n\n\n\n \u25cf Configuring a Rapid Release or Scheduled Release for feature releases (Google Documentation:<\/strong> Choose when users get new features<\/a>)<\/p>\n\n\n\n \u25cf Configuring Google Meet to align with corporate policies and requirements (Google Documentation:<\/strong> Manage Meet settings (for admins)<\/a>)<\/p>\n\n\n\n \u25cf Creating and configuring security and data region settings (Google Documentation:<\/strong> Data regions: Choose a geographic location for your data<\/a>)<\/p>\n\n\n\n \u25cf Implementing security integration protocols and addressing questions and objections from users<\/p>\n\n\n\n \u25cf Managing content compliance rules (Google Documentation:<\/strong> Advanced filtering with Content Compliance rules<\/a>)<\/p>\n\n\n\n \u25cf Investigating and remediating an issue by using Security Health Analytics check results (Google Documentation:<\/strong> Remediating Security Health Analytics findings<\/a>)<\/p>\n\n\n\n 2.2 Configuring Gmail. Considerations include:<\/p>\n\n\n\n \u25cf Configuring basic mail routing scenarios for split delivery (Google Documentation:<\/strong> Set up Split Delivery with Google Workspace first<\/a>)<\/p>\n\n\n\n \u25cf Configuring a mail host (Google Documentation:<\/strong> Add mail servers for Gmail email routing<\/a>)<\/p>\n\n\n\n \u25cf 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:<\/strong> Set up Gmail with a third-party email client<\/a>)<\/p>\n\n\n\n \u25cf Configuring POP and IMAP access to align with corporate policies and requirements (Google Documentation:<\/strong> Turn POP & IMAP on or off for users<\/a>)<\/p>\n\n\n\n \u25cf Configuring administrator access for mail forwarding by using advanced Gmail settings (for example, compliance rules, default routing, APIs) (Google Documentation:<\/strong> Add Gmail Routing settings<\/a>)<\/p>\n\n\n\n \u25cf Managing and understanding all available spam controls (for example, allowlist, denylist, inbound gateway, and IP allowlist) (Google Documentation:<\/strong> Allowlists, denylists, and approved senders<\/a>)<\/p>\n\n\n\n \u25cf Enabling email delegation for an OU (Google Documentation:<\/strong> Delegate a user\u2019s email address<\/a>)<\/p>\n\n\n\n \u25cf Managing Gmail archives (Google Documentation:<\/strong> Archive former employee accounts<\/a>)<\/p>\n\n\n\n 3.1 Troubleshooting mail delivery problems reported by users. Considerations include:<\/p>\n\n\n\n \u25cf Determining whether user behavior or a broader issue (for example, rules, or Cloud Data Loss Prevention [DLP]) is causing an error (Google Documentation:<\/strong> Use Workspace DLP to prevent data loss<\/a>)<\/p>\n\n\n\n \u25cf Determining whether an issue is an expected behavior (for example, a missing attachment, or an attachment filter issue) (Google Documentation:<\/strong> Set up rules for basic email content filtering<\/a>)<\/p>\n\n\n\n \u25cf Auditing and reviewing mail flow structure and end-user actions to determine the root cause of delivery issues (Google Documentation:<\/strong> About the audit and investigation tool<\/a>)<\/p>\n\n\n\n \u25cf Analyzing message headers or email audit logs by using Google Workspace tools or security investigation tools (Google Documentation:<\/strong> About the security investigation tool<\/a>)<\/p>\n\n\n\n \u25cf Recommending and\/or implementing an appropriate course of action related to mail delivery issues (for example, implementing mail policy changes) (Google Documentation:<\/strong> Email sender guidelines<\/a>)<\/p>\n\n\n\n 3.2 Troubleshooting and collecting logs and reports needed to engage with the support team. Considerations include:<\/p>\n\n\n\n \u25cf Documenting steps taken by end user to reproduce an issue (Google Documentation:<\/strong> Manage Approvals<\/a>)<\/p>\n\n\n\n \u25cf Collecting appropriate log file types (Google Documentation:<\/strong> Drive log events<\/a>, Collect Google Workspace logs<\/a>)<\/p>\n\n\n\n \u25cf Searching for known issues and application status (Google Documentation:<\/strong> Google Workspace Known Issues<\/a>)<\/p>\n\n\n\n \u25cf Generating HAR files<\/p>\n\n\n\n 3.3 Identifying, classifying, troubleshooting, and mitigating basic email attacks. Considerations Include:<\/p>\n\n\n\n \u25cf Configuring:<\/p>\n\n\n\n \u25cb Blocked senders (Google Documentation:<\/strong> How to block or mark suspicious email as spam<\/a>)<\/p>\n\n\n\n \u25cb Email allowlist (Google Documentation:<\/strong> How to add an IP address to allowlist<\/a>)<\/p>\n\n\n\n \u25cb Objectionable content (Google Documentation:<\/strong> Control message delivery based on message content<\/a>)<\/p>\n\n\n\n \u25cb Phishing settings (Google Documentation:<\/strong> Advanced phishing and malware protection<\/a>)<\/p>\n\n\n\n \u25cb Spam settings (Google Documentation:<\/strong> How to customize spam settings on Google Workspace<\/a>)<\/p>\n\n\n\n \u25cb Gmail safety settings<\/p>\n\n\n\n \u25cb Administrator quarantine (Google Documentation:<\/strong> Set up email quarantine<\/a>)<\/p>\n\n\n\n \u25cb Attachment compliance<\/p>\n\n\n\n \u25cb Secure transport compliance (Google Documentation:<\/strong> Send email over a secure TLS connection<\/a>)<\/p>\n\n\n\n \u25cf 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:<\/strong> Help prevent spoofing and spam with DMARC<\/a>, About MTA-STS and TLS reporting<\/a>)<\/p>\n\n\n\n \u25cf Investigating whether custom configurations are responsible for any issues or vulnerability (for example, email allowlist and IP addresses) (Google Documentation:<\/strong> Allowlists, denylists, and approved senders<\/a>)<\/p>\n\n\n\n \u25cf Investigating the scope of email attacks by using available Google Workspace email tools (Google Documentation:<\/strong> Investigate reports of malicious emails<\/a>)<\/p>\n\n\n\n \u25cf Analyzing message contents for common attack patterns (for example, name, domain, and brand spoofing) (Google Documentation:<\/strong> Spoofing report<\/a>)<\/p>\n\n\n\n \u25cf Mitigating successful attacks and preventing future attacks by using Google Workspace email tools (for example, identifying the issue and responding)<\/p>\n\n\n\n 3.4 Troubleshooting Google Workspace access and performance issues. Considerations include:<\/p>\n\n\n\n \u25cf Identifying why a user is having an issue when they access a single Google application (for example, Drive) (Google Documentation:<\/strong> Troubleshoot shared drives for your users<\/a>)<\/p>\n\n\n\n \u25cf 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:<\/strong> Google Workspace Known Issues<\/a>)<\/p>\n\n\n\n \u25cf Analyzing, evaluating, and modifying settings to ensure delivery of critical emails (for example, specific IP ranges, X-headers)<\/p>\n\n\n\n \u25cf Troubleshooting authentication issues that users reported (Google Documentation:<\/strong> Troubleshoot login challenges, 2-Step Verification, & sign-in issues<\/a>)<\/p>\n\n\n\n \u25cf Troubleshooting issues that users reported when they set up Google Workspace on a mobile device <\/p>\n\n\n\n \u25cf Troubleshooting Google Meet video call issues from the administrator console (Google Documentation:<\/strong> Unable to start Google Meet sessions<\/a>)<\/p>\n\n\n\n \u25cf Troubleshooting Google Meet device issues by using the administrator console (Google Documentation:<\/strong> Manage Meet settings (for admins)<\/a>)<\/p>\n\n\n\n \u25cf Troubleshooting network configuration issues to ensure high-quality meetings by using Google Meet (Google Documentation:<\/strong> Prepare your network for Meet meetings & live streams<\/a>)<\/p>\n\n\n\n \u25cf Troubleshooting Jamboards (Google Documentation:<\/strong> Troubleshoot Jamboard device<\/a>)<\/p>\n\n\n\n \u25cf Troubleshooting access to Google Workspace services (for example, Gmail and Drive) (Google Documentation:<\/strong> Troubleshoot shared drives for your users<\/a>)<\/p>\n\n\n\n \u25cf Troubleshooting data visibility issues by enabling\/disabling licenses or services<\/p>\n\n\n\n \u25cf Investigating access issues in applications for OUs (Google Documentation:<\/strong> About the security investigation tool<\/a>)<\/p>\n\n\n\n \u25cf Interpreting and responding to alerts in the Alert Center API (Google Documentation:<\/strong> Google Workspace Alert Center API<\/a>)<\/p>\n\n\n\n 4.1 Configuring policies for all devices (for example, mobile device, desktop, Chrome OS, Google Meet Hardware, Jamboard, Google Voice, and browser). Considerations include:<\/p>\n\n\n\n \u25cf Configuring:<\/p>\n\n\n\n \u25cb Chrome user and browser policy settings (Google Documentation:<\/strong> How to activate user-level policies for Chrome<\/a>)<\/p>\n\n\n\n \u25cb ChromeOS device policy settings (for example, Enterprise) (Google Documentation:<\/strong> Section 2: Configuring services (18%)<\/strong><\/h4>\n\n\n\n
Section 3: Troubleshooting (24%)<\/strong><\/h4>\n\n\n\n
Section 4: Data access and authentication (24%)<\/strong><\/h4>\n\n\n\n