GOOGLE-WORKSPACE-ADMINISTRATOR practice question 5 of 25

All Human Resources employees at your company are members of the “HR Department” Team Drive. The HR Director wants to enact a new policy to restrict access to the “Employee Compensation” subfolder stored on that Team Drive to a small subset of the team. What should you do?

Full set: 199 questions

Domain Business initiatives

Answer options
A: Use the Drive API to modify the permissions of the Employee Compensation subfolder.
B: Use the Drive API to modify the permissions of the individual files contained within the subfolder.
C: Move the contents of the subfolder to a new Team Drive with only the relevant team members. Correct answer
D: Move the subfolder to the HR Director's MyDrive and share it with the relevant team members.
Correct Answer:
C. Move the contents of the subfolder to a new Team Drive with only the relevant team members.
Explanation

In Google Workspace, permissions for shared drives (formerly Team Drives) are inherited from the top level. All members of a shared drive have access to all files and folders within it. It is not possible to set more restrictive permissions on a subfolder to prevent members of the parent shared drive from accessing it. The correct administrative action is to isolate the sensitive content. Creating a new, separate shared drive for the "Employee Compensation" data and adding only the authorized subset of HR employees as members ensures that access is properly restricted and that the data remains owned by the organization, not an individual.

Why Incorrect

A. The Drive API cannot override the fundamental permission model of shared drives. You cannot use it to restrict access for existing members to a subfolder.
B. Similar to option A, the Drive API cannot be used to remove inherited permissions from individual files for members of the parent shared drive.
D. Moving the folder to a user's "My Drive" makes that user the owner. If that user leaves the company, it creates data ownership and access continuity problems, which shared drives are designed to prevent.

References

1. Google Workspace Admin Help, "Control access to files and folders in shared drives": Under the section "How folder access works in a shared drive," the documentation states, "All members of a shared drive can see all the files and folders in it." It also notes, "You can’t restrict access to a specific folder in a shared drive." This directly invalidates options A and B.

2. Google Workspace Learning Center, "Best practices for shared drives": In the section "Organize shared drives based on access needs," the guidance recommends creating shared drives for specific projects or content with distinct access requirements. It advises, "If a folder has a very different purpose or audience from the parent folder, consider creating a separate shared drive for it." This directly supports the solution in option C.

3. Google Drive Help, "Shared drives overview": This document explains a key benefit of shared drives: "Files in a shared drive belong to the team instead of an individual. Even if members leave, the files stay in the shared drive so your team can keep sharing information..." This highlights the administrative risk of using an individual's "My Drive" for critical team data, making option D an inferior choice compared to C.

Scroll to Top