Prepare and test your skills

Prepare and test your skills

Manual administration via the Google Admin Console and Google Cloud console is the hands-on way to create and control users and groups for Google Cloud access. Cloud Identity (opens in a new tab) is an Identity as a Service (IDaaS) solution that centrally manages users and groups in a domain. When you adopt Cloud Identity, you create a Cloud Identity account for each user and group, and then you use Identity and Access Management (IAM) to manage access to Google Cloud resources for each account.
The organization resource is the top-level container that links manual identity work to Google Cloud resources. Each Google Workspace or Cloud Identity account is associated with exactly one organization resource, and each organization resource is associated with exactly one domain. All projects and billing accounts created under that domain become child resources of the organization resource (opens in a new tab). This parent-child structure means policies and IAM roles granted at the organization flow down to everything inside it, while projects created before the organization appear under No organization until they are moved in.
Group management permissions come from two separate systems that must work together. Group permissions to create, view, edit, and delete groups are managed by Google Workspace, not by IAM, so an administrator must grant them through Workspace admin privileges. IAM permissions to use the Google Cloud console for groups come from IAM roles granted on the organization, including Organization Viewer (roles/resourcemanager.organizationViewer) for viewing groups and Logs Viewer (roles/logging.viewer) for viewing group membership change logs. This split means a person needs both the Workspace-side group privilege and the IAM-side viewer role to fully administer groups from the console.
A Google group (opens in a new tab) is a collection of users where each member inherits the IAM roles granted to that group. This inheritance lets you manage access by changing group membership instead of granting IAM roles to individual users. To view groups, go to the Groups page in the Google Cloud console and select the organization, and the console displays all groups you can access.
To create a group in the Google Cloud console:
When a member is added to a Google group, the member inherits all IAM roles granted to that group, regardless of their Google Groups role.
Viewing and editing group details keeps group names, descriptions, and membership accurate over time. To edit a group, find it on the Groups page, open the More menu, and choose View group details. Type a new name or description in the Group name or Group description field and click Save to apply the change.
Membership changes flow directly to access because the group depends on its member list for IAM inheritance. To add members, click Add members, enter names, choose their Google Groups roles, and click Add. To remove members, select the checkboxes next to their names and click Remove members. Some settings such as moderation, joining rules, and post creation and viewing permissions cannot be managed from the Google Cloud console, so use View in Google Groups to open the group in Google Groups for those features.
Deleting a group is an irreversible lifecycle change that removes a reusable access path. Before deletion, revoke all IAM roles from the group and wait at least 7 days to avoid unexpected access changes from cached or dependent bindings. Only after that waiting period, find the group on the Groups page, choose Delete group from the More menu, and click Confirm.
Exam tip: Revoke all IAM roles from a group and wait at least 7 days before deleting it, because deletion is irreversible.
If data sharing is enabled for the organization, Google Cloud automatically generates audit logs for Workspace actions such as adding a user to the organization or removing a user from a group. Those Google Workspace audit logs can be viewed and managed in Cloud Logging (opens in a new tab), which connects a manual Admin Console action to its traceable log entry.
Security groups streamline access control because IAM policy applies to the group and every member inherits it. Instead of binding roles user by user, you bind roles once to groups such as billing, network, or organization admins, and membership controls who receives them. Service agents cannot be added to Google groups unless the external members option is turned on.
Foundational group recommendations show how this grouping enforces separation of duties:
| Group | Purpose | Key IAM roles |
|---|---|---|
| grp-gcp-org-admin | Administers resources that belong to the organization | Organization Administrator, Folder Admin, Project Creator, Billing Account User |
| grp-gcp-network-admins | Creates networks, subnets, firewall rules, Cloud Router, Cloud VPN, and load balancers | Compute Network Admin, Compute Shared VPC Admin, Compute Security Admin, Folder Viewer |
| grp-gcp-billing-admin | Sets up billing accounts and monitors usage | Billing Account Administrator, Billing Account Creator, Organization Viewer |
Assign these highly privileged roles sparingly, and consider using individual accounts instead of a group for organization administration (opens in a new tab) when risk requires tighter control.
Programmatic and bulk management techniques are ways to create, update, and review many users and groups at once instead of handling accounts one by one. Cloud Identity (opens in a new tab) provides the central store for user and group accounts, while tools such as Google Cloud Directory Sync (GCDS), the gcloud CLI, and Google Cloud APIs carry out large-scale changes and lifecycle reviews. Together they let an organization automate the full lifecycle from account creation to permission cleanup.
Central identity management in Cloud Identity means every user and group gets an organization-controlled account that Identity and Access Management (IAM) can use for access to Google Cloud resources. Cloud Identity is an Identity as a Service (IDaaS) solution that centrally manages users and groups and can federate identities with other providers such as Active Directory and Microsoft Entra ID, formerly Azure AD. This control matters because personal accounts such as Gmail accounts sit outside the organization, while Cloud Identity accounts bring access and compliance under central management. When Cloud Identity is adopted, an administrator creates a Cloud Identity account for each user and group and then uses IAM to grant access to resources.
Bulk synchronization from an external identity provider (IdP) keeps external user records and Cloud Identity accounts aligned without manual entry for each person. Google Cloud Directory Sync (GCDS) is the sync tool that keeps external identities synchronized with corresponding Cloud Identity or Google Workspace accounts so users can sign in to Google services with external credentials. This approach requires two accounts for each user, an external account and a Cloud Identity or Google Workspace account, with the tool keeping them synchronized. By contrast, Workforce Identity Federation lets users sign in with their external IdP and access Google Cloud resources with only their external account.
The two user federation strategies differ in account count and sign-in flow:
| Strategy | Accounts per user | How access works |
|---|---|---|
| Federation using Cloud Identity or Google Workspace | Two accounts: external account plus Cloud Identity or Google Workspace account | User signs in with external credentials, GCDS keeps the paired accounts synchronized |
| Workforce Identity Federation | One account: external account only | External IdP signs the user directly into Google Cloud, sometimes called a federated identity |
Exam tip: Federation with sync needs two accounts per user, while Workforce Identity Federation needs only the external account.
Command-line and API-driven operations let administrators apply the same identity and project changes repeatedly across the organization. The gcloud CLI authenticates with user credentials through gcloud auth login and then runs project and IAM commands, with later commands using the signed-in principal to make requests. The same session powers Cloud Shell in the Google Cloud console, so interactive console work and command-line automation share one identity. For workloads and applications, Application Default Credentials (ADC) lets client libraries find credentials in the current environment, so code can move from a local device to a Compute Engine virtual machine without changing the code itself.
Large-scale setup with the gcloud CLI follows an ordered workflow:
gcloud init, then create a project with gcloud projects create or select an existing project with gcloud config set project.serviceusage.services.enable permission.gcloud projects add-iam-policy-binding once per role, with --member="user:USER_IDENTIFIER" for users or --member="serviceAccount:..." for service accounts.This sequence shows the dependency between layers: the project must exist before APIs are enabled, and APIs and IAM bindings must exist before users and service accounts can act on resources.
Monitoring large-scale identity changes means using centralized recommendations and audit logs to find unused accounts, extra permissions, and membership edits. Policy Intelligence includes the IAM recommender, which uses machine learning to recommend least-privilege fixes such as REMOVE_ROLE and to surface insights about permission usage and unused service accounts. At enterprise scale, administrators configure an export of recommendations to a BigQuery dataset and then query for recommender = "google.iam.policy.Recommender" to review and rightsize access with visualization tools. Changes to Google group membership are tracked separately in Activity logs for group membership review.
Cloud Audit Logs (opens in a new tab) records who did what, where, and when for IAM lifecycle events such as policy changes, service account creation, and key downloads. The four audit log classifications are:
For identity work, Admin Activity and Policy Denied logs are the most useful, and logs can be viewed in Logs Explorer, queried through the Cloud Logging API and command-line interface, or exported to BigQuery through a log sink for longer retention and aggregate analysis.
Google Cloud Directory Sync (GCDS) (opens in a new tab) is a tool that automates identity management by copying users and groups from an existing Active Directory or LDAP environment into Cloud Identity or Google Workspace. Data flows from Active Directory to GCDS through LDAP, and then from GCDS to Cloud Identity through HTTPS using the Directory API and Domain Shared Contacts API. This automation keeps cloud accounts in sync with on-premises changes, so access control stays secure and scalable without manual creation of each user.
GCDS sits between Active Directory on one side and Cloud Identity on the other, with a different connection on each side. On the on-premises side, GCDS uses LDAP to query a global catalog (GC) server for user and group information, which requires a hostname and port in the configuration. On the cloud side, GCDS communicates with Cloud Identity over HTTPS, which requires little or no firewall change. Because Active Directory uses unencrypted LDAP by default, remote access from Google Cloud should use encrypted communication with LDAPS (LDAP over SSL) or Cloud VPN.
GCDS can run on Windows or Linux, but it is best to run GCDS on a separate machine rather than on the domain controller. The machine must have LDAP access to Active Directory and meet system requirements, but it does not have to be domain-joined. In a small environment with one GC server, GCDS can point directly to that server, while in a larger environment with redundant GC servers, a PowerShell script can use the DC Locator mechanism to find the closest available GC dynamically instead of using one static endpoint.
GCDS depends on two dedicated service accounts, one in Cloud Identity and one in Active Directory. The Cloud Identity account, for example cloud-directory-sync, allows GCDS to create, list, and delete users and groups through the APIs. This account is made a Super Admin so it has sufficient privileges, is exempted from single sign-on so GCDS can still re-authorize if single sign-on fails, and is protected with 2-step verification because Super Admin grants full access.
The Active Directory account, for example gcds, allows GCDS to read users and groups from the directory. This dedicated domain user is created in the same domain as the GCDS machine, with a strong password, User must change password at next logon cleared, and Password never expires selected. Using separate, purpose-built accounts on both sides limits risk and makes it clear that all sync changes come from GCDS.
GCDS installation and setup centers on the Configuration Manager, the graphical interface included with GCDS for building the sync configuration. If the server has a desktop experience, Configuration Manager can run on the server itself; otherwise, it is run locally and the resulting XML configuration file is copied to the server. GCDS stores its configuration in an XML file that includes an OAuth refresh token used to authenticate to Google.
Because that file contains a credential, the folder that holds it must be secured so only GCDS and administrators have access. A common practice is to create a folder such as $Env:ProgramData\gcds and apply an access control list that grants full control only to Creator Owner, Built-in Administrators, Domain Admins, and Local Service. GCDS itself does not need other local resources, so it can run as the limited LocalService account rather than as a full administrator.
The sync configuration defines which types of directory objects flow from Active Directory into Cloud Identity. In Configuration Manager under General Settings, the administrator selects the object types to include:
User mapping is then configured under User Accounts by choosing whether the Cloud Identity email comes from the Active Directory userPrincipalName (UPN) or mail attribute. Default mappings populate Given Name from givenName and Family Name from sn, and the Email Address Attribute can be set to userPrincipalName, with optional domain substitution and optional removal of proxyAddresses if aliases should not sync. Search rules control scope with Sub-tree scope and a blank Base DN to search all domains in the forest, using an LDAP filter that matches non-disabled person users while excluding computer accounts, managed service accounts, and the gcds service account itself.
A safe GCDS rollout follows an ordered sequence that moves from preview to permanent changes to automation. Logging and notifications are configured first so each run writes a timestamped log file and can send email alerts through a mail server.
Initial provisioning makes permanent changes, so large deployments should first test with an LDAP query limited to a subset of users, then expand to the full set after validation. Repeatedly modifying or deleting large numbers of users during testing should be avoided because it can be flagged as abusive behavior.
Exam tip: Simulate sync only previews proposed changes, while Sync & apply changes permanently creates, updates, or deletes users and groups in Cloud Identity.
Federation using Cloud Identity synchronization requires two accounts per user, an external account plus a Cloud Identity or Google Workspace account kept synchronized by Google Cloud Directory Sync (GCDS), while Workforce Identity Federation requires only the external account. With synchronization the user signs in with external credentials to use the paired cloud account, whereas with Workforce Identity Federation the external identity provider signs the user directly into Google Cloud.
Members of a Google group inherit all Identity and Access Management (IAM) roles granted to that group, regardless of their Google Groups role, so access is managed by changing group membership instead of granting roles to individual users. Binding roles once to groups such as billing, network, or organization admins lets membership control who receives them.
Simulate sync only previews proposed changes and makes no changes to Cloud Identity, while Sync and apply changes permanently creates, updates, or deletes users and groups in Cloud Identity. A safe rollout runs Simulate sync with Clear cache selected for review, then runs Sync and apply changes after verifying that no unwanted deletions or suspensions appear.
An organization is setting up its Google Cloud solution environment for a newly onboarded engineering team. The cloud administrator needs to manually provision corporate identities, enforce organizational security policies such as multi-factor authentication for specific departments, and manage access to Google Cloud project resources efficiently at scale.
Which administrative approach should the administrator implement to meet these requirements?
Last updated