A dynamic group automatically updates membership based on user attributes, such as department, ensuring that only relevant employees (e.g., those in the finance department) are added to the group. This minimizes management overhead because the membership is updated automatically, without the need for manual intervention. It also ensures that the group remains up to date as employees join or leave the department.

To ensure that Google Calendar suggests nearby office rooms when a user creates an event, you need to associate both the users and the room resources with their respective locations within the Google Workspace organizational structure. The most effective way to do this is by organizing users into organizational units (OUs) based on their location and then associating the room resources with the corresponding OUs.

Here's why option C is the correct approach and why the others are less suitable for this specific requirement:

C . Add your users to organizational units (OUs) by location. Add room resources to the corresponding OUs.

Google Calendar uses the organizational unit (OU) structure to determine the proximity of resources to users. By placing users within OUs that correspond to their office locations and then assigning the room resources of each office to the same or relevant child OUs, Google Calendar can suggest nearby rooms to users when they schedule meetings. This method directly links users and resources based on their organizational location.

Associate Google Workspace Administrator topics guides or documents reference: The official Google Workspace Admin Help documentation on 'Set up rooms and shared resources' (or similar titles) explains how to create and manage room resources. It also details how to associate these resources with specific buildings, floors, and, importantly, organizational units. While the documentation might not explicitly state that nearby suggestions solely rely on OUs, the OU structure is the primary way Google Workspace understands the organizational hierarchy and location of users and resources. By aligning user and resource OUs, you provide the context for 'nearby' suggestions.

A . Assign building ID, floor name, and floor section to define users' work locations based on defined buildings and rooms.

While assigning building IDs, floor names, and sections is crucial for defining the physical location of room resources, it doesn't directly define the user's work location in a way that Google Calendar inherently uses for proximity-based suggestions. These attributes are primarily for the room resources themselves. To establish the 'nearby' context, you need to link users to their locations within the organizational structure (i.e., through OUs).

Associate Google Workspace Administrator topics guides or documents reference: The documentation on setting up room resources will guide you through adding details like building, floor, and capacity to the resource. However, it's the OU assignment of both users and resources that provides the relational context for proximity.

B . Add your users to Google Groups by location. Add room resources to the corresponding groups.

Google Groups are primarily for communication and collaboration among users. While you can group users by location, Google Calendar's room suggestion logic is not primarily based on Google Group membership. Associating room resources with groups does not provide the necessary organizational context for suggesting nearby rooms to users when they create events.

Associate Google Workspace Administrator topics guides or documents reference: Google Groups functionality is focused on user communication and access management for group-related resources, not on the spatial or organizational relationships between users and physical meeting rooms for Calendar scheduling.

D . Restrict room sharing to a dynamic group based on user location.

Restricting room sharing to a dynamic group based on user location controls who can book the room, not necessarily whose nearby rooms are suggested when creating an event. Dynamic groups manage membership based on user attributes, but they don't inherently define a user's 'nearby' location for Calendar suggestions in the same way that OU-based organizational structure does.

Associate Google Workspace Administrator topics guides or documents reference: Dynamic groups are useful for managing user membership based on attributes, but they are not the primary mechanism for defining the spatial relationship between users and resources for Google Calendar's room suggestions.

Therefore, the most effective method to ensure Google Calendar suggests nearby office rooms to users based on their location is to add your users to organizational units (OUs) by location and add room resources to the corresponding OUs. This aligns the organizational structure with the physical locations, allowing Google Calendar to understand proximity for room suggestions.

Since user accounts are managed in Active Directory (AD) and synced to Google Workspace via Google Cloud Directory Sync (GCDS), the best approach to enforce the new password policy is to create the password policy within Active Directory and then enable password synchronization in GCDS. This ensures that the complex password requirements are enforced within AD, and when passwords are updated, they will be synchronized with Google Workspace, maintaining consistency across both systems.

Switching the former employee's account to an Archived User license ensures that their data and documents are preserved, and access is retained for the manager and team without incurring the full cost of an active Workspace license. Archived User licenses are a cost-effective way to maintain access to documents while preventing unauthorized access to the account.

Advanced mobile management in Google Workspace provides the necessary features for securing mobile devices without the need for third-party apps or additional licenses. This includes enforcing passcodes and enabling remote account wipe functionality for both iOS and Android devices. Advanced management ensures that both security requirements are met while keeping the setup efficient and within the organization's existing licenses.