How to Securely Share Files With External Partners in Google Workspace?

PWA By islever Editorial Last updated

Short answer

B Create a Shared Drive and grant Contributor access to the HR team.

Question

Your organization has hired a recruiting firm that is responsible for reviewing resumes and job descriptions of prospective summer interns. Employees at your organization need to collaborate with the external firm on these documents. You must set permissions and ensure the recruiting firm employees can't remove the files. What should you do?
  1. Create a Google Group, add the HR team, and create a shared folder for content storage and editing.
  2. Create a Shared Drive and grant Contributor access to the HR team. Correct Answer
  3. Enable client-side encryption for the organizational unit (OU) for which the HR team are members.
  4. Create a Shared Drive and grant Content Manager access to the HR team.

Key Takeaways

Tests precise understanding of Shared Drive permission tiers, with the common trap being confusion between Contributor and Content Manager deletion rights.

This scenario tests knowledge of Google Workspace Shared Drives versus personal folder permissions, highlighting how role-based access controls prevent unauthorized deletions. Community consensus confirms that Shared Drives paired with Contributor access provide the optimal balance of external collaboration and data preservation.

Common mistake: Option D is frequently selected incorrectly because candidates assume higher access levels improve collaboration, overlooking that Content Managers retain full delete privileges which violates the prompt's constraints.

Expert Analysis

Why the Answer Is Correct

Shared Drives are specifically engineered for team-based workflows where document ownership remains with the organization rather than an individual user. Assigning Contributor access enables external partners to view, edit, and organize files while explicitly stripping deletion privileges, which directly satisfies the prompt’s security constraint. This configuration eliminates the risk of accidental data loss during high-turnover periods like summer intern hiring. Community feedback overwhelmingly supports this approach, noting that Contributors simply cannot delete files [1]. Furthermore, Shared Drives avoid the administrative overhead of manually transferring ownership when internal staff changes [2].

Why the Other Options Are Wrong

Option A relies on a standard shared folder anchored to a single user’s My Drive, creating a critical single point of failure if that employee departs or mishandles sharing settings. Option C introduces client-side encryption, which safeguards data at rest but provides zero functionality for managing collaborative editing rights or deletion restrictions. Option D assigns Content Manager permissions, which inadvertently grant the exact delete capability the scenario explicitly forbids. Choosing higher-tier access levels often stems from confusing collaboration needs with administrative control.

Community Comment Notes

Test-takers universally agree on option B, with multiple voters emphasizing that Contributor roles natively prevent file deletion [1]. Several candidates point out that Shared Drives offer superior scalability compared to standard shared folders by decoupling file ownership from individual accounts [2]. The unanimous voting distribution underscores a clear understanding that granular permission mapping is essential for third-party collaborations. These insights reinforce the importance of memorizing Google Workspace role definitions before the exam.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

Always map explicit constraints like 'cannot delete' to Google Workspace permission tiers, remembering that Contributors edit but lack removal privileges. Prioritize Shared Drives over personal folders for external partnerships to maintain organizational ownership and prevent data loss during personnel transitions.

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. Janoss 👍 2
    B - must be. Contributor cant delete files.
  2. professionalCrammer23 👍 1 Answered B
    B because although option A can work, it requires at least one person to own all the files and share with the rest of the team. A shared drive makes more sense in this case
  3. ptsironis 👍 1 Answered B
    B is correct

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

How to Fix Non-Google File Access Issues in Google Drive?

S-grade

How to First Troubleshoot Google Meet Video Issues?

S-grade

How to Restrict Temporary Employees' Email Domains in Google Workspace?

S-grade

How to Securely Share Files with External Users Without Google Accounts?

S-grade

← Back to PWA Study Guide