How to Apply a Shorter Retention Policy to a Specific OU in Google Vault?

Your default Vault retention policy for Gmail is set to 365 days. Your legal department has just informed you that emails sent and received by the customer support department are sensitive, and must be retained for only 30 days. You must enforce this new retention policy in the simplest way. What should you do?

  1. Change the current default retention policy in Vault for Gmail to 30 days, and apply it to the customer support organizational unit (OU). Configure a custom retention policy for Gmail for 365 days for your domain.
  2. Create two custom retention policies in Vault: one for 30 days that is applied to the customer support organizational unit (OU), and one for 365 days that is applied to all other OUs in your directory.
  3. Change the current default retention policy for Gmail to 30 days. Configure two custom retention policies in Vault: one for 30 days that is applied to the customer support organizational unit (OU), and one for 365 days that is applied to all other OUs in your directory.
  4. Create a custom retention policy in Vault for Gmail for 30 days, and apply it to the customer support organizational unit (OU). Source Reference Answer

Community Votes

D
100%

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

Community Insight

Tests understanding of Vault policy inheritance and scoping, with the common trap being overcomplicating the setup by modifying the global default or duplicating rules across multiple OUs.

Learn how to efficiently override default Google Vault retention policies using organizational units without disrupting other departments. Community consensus strongly confirms creating a single targeted custom policy as the simplest and most compliant solution.

Option A is frequently chosen incorrectly because test-takers mistakenly believe the global default must be updated first, overlooking that custom policies automatically override defaults for targeted scopes without affecting others.

Community Discussion (3 comments)

mostafa97 👍 1
D is correct
apb98 👍 1 Selected: D
This approach is the simplest and most efficient.
dija123 👍 1 Selected: D
D is very simple and correct.

Comments & Corrections

No comments 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.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Creating a single custom retention policy scoped directly to the customer support OU immediately overrides the default 365-day rule for that specific group while leaving all other organizational units untouched. This leverages Google Vault’s hierarchical evaluation model, where more specific scopes take precedence over broader defaults. It requires minimal configuration steps, perfectly aligning with the requirement for the simplest operational approach.

Why the Other Options Are Wrong

Option A incorrectly modifies the global default policy, which would temporarily reduce retention for every user before a new domain-wide policy is applied, creating unnecessary data loss risk. Option B and C introduce administrative bloat by splitting policies across multiple OUs or duplicating the 30-day rule, increasing the chance of misconfiguration. Vault does not require applying identical policies to every OU when the existing default already covers them adequately.

Community Comment Notes

Test-takers consistently highlight the emphasis on operational simplicity in this scenario, with multiple comments confirming that D is the most efficient approach. Users note that overriding defaults or creating redundant policies violates cloud compliance best practices and exam logic. The unanimous voting pattern demonstrates that recognizing scope-based inheritance is key to answering correctly.

Official Reference

Exam Strategy

Always prioritize options that minimize changes to existing configurations while meeting the exact requirement. In cloud administration exams, phrases like 'simplest way' typically point to leveraging built-in inheritance or scoping mechanisms rather than building complex multi-policy structures.

Related Analysis

← Back to PWA Study Guide