How to Transfer Calendar Ownership When an Employee Resigns?
An employee at your organization is resigning. They are in charge of organizing and maintaining recurring team events. You want to preserve the existing meetings and transfer ownership to the resigning employee's manager. What should you do?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests understanding of admin-level data transfer versus user-level sharing, with the trap being manual event deletion or relying on guest permissions which do not transfer ownership.
This question tests proper calendar ownership transfer during employee offboarding in Google Workspace. The community consensus confirms that using the Admin console to transfer events and resources ensures meeting continuity without manual recreation.
Option B is the most common wrong answer because candidates assume deleting old events and recreating them is cleaner, but this destroys historical attendance records, resource bookings, and automated reminders tied to the original events.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Using the Admin console’s transfer feature during user deletion or suspension automatically migrates calendar events and owned resources to a designated recipient. This preserves all invitees, attachments, and historical data while seamlessly updating the organizer field to the manager. As noted in official documentation, suspended or deleted users’ events remain visible to guests, but only admins can officially reassign ownership to maintain compliance and audit trails [Comment 1].Why the Other Options Are Wrong
Deleting existing events permanently removes metadata, booking history, and automated notifications, forcing unnecessary manual work. Assigning an Archived User license merely restricts login access and does not trigger any ownership migration workflow. Sharing free/busy details only grants viewing permissions for scheduling conflicts, leaving the manager unable to edit, move, or officially own the recurring meetings.Community Comment Notes
Candidates unanimously selected Option A, validating it as the standard offboarding procedure. Multiple contributors referenced Google’s support article on transferring user data when deleting or suspending accounts, emphasizing that admin-level transfers are required rather than user-side sharing [Comment 2]. The discussion highlights that guest copies of events persist even after account deletion, reinforcing why administrative ownership transfer is essential for long-term maintenance.Official Reference
Exam Strategy
Always prioritize admin console data transfer features over user-level sharing or manual recreation during offboarding scenarios. Familiarize yourself with the exact steps in the Admin console for transferring user content, as exams frequently test the distinction between permission sharing and actual ownership migration.