How Should You Configure Google Groups for Confidential Access?
Short answer
B Make a security group to apply access policies.
Question
Key Takeaways
Exam tests differentiation between Google Group types, with the common trap being confusing security groups with communication or dynamic groups that serve entirely different operational purposes.
Use Google Security Groups to restrict access to sensitive data while enforcing the principle of least privilege. Community consensus strongly validates option B as the only configuration designed specifically for identity-based access policies rather than communication.
Common mistake: Option C (Dynamic Group) is frequently selected due to its appeal for automation, but it violates the explicit requirement for manual administrative control and precise least-privilege access management.
Expert Analysis
Why the Answer Is Correct
Security groups in Google Workspace are explicitly designed for identity-based access control rather than email distribution. They integrate directly with IAM policies, allowing administrators to grant or deny permissions to confidential resources while strictly adhering to the principle of least privilege. Since the scenario emphasizes manual membership management by administrators, a static security group provides the exact governance model required.
Why the Other Options Are Wrong
Moderated groups and collaborative inboxes are communication-focused tools optimized for email workflow and message filtering, not resource access control. Dynamic groups automatically add members based on directory attributes, which contradicts the requirement for deliberate administrative oversight and targeted permission scoping. None of these alternatives satisfy the core objective of securing confidential content through policy enforcement.
Community Comment Notes
Candidates consistently validate option B across multiple votes, highlighting its alignment with confidentiality and policy enforcement needs. Comment [1] correctly notes that security groups enable valid policy definitions for restricted content. Comments [2] and [3] reinforce that collaborative and moderated options lack the necessary access-control mechanisms, cementing B as the definitive choice.
Official Reference
These links open the official vendor documentation in a new tab.
Exam Strategy
Always map keywords like access control, policies, and least privilege directly to security groups during the exam. Avoid selecting dynamic or communication groups unless the question explicitly mentions automation rules, email moderation, or shared messaging workflows.
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 6 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 6
-
fabioevangelo 👍 2B parece ser uma saida indicada, uma vez que fala em conteudo confidencial e privilégio minimo. Definir um grupo e aplicar politicas seria uma opção valida.
-
AGHPE 👍 1 Answered BIt's B. option D is not valid, it is not the appropriate tool to protect confidential content.
-
magnopds 👍 1 Answered BThe option B makes more sense than the others options.
-
a17b29d 👍 2B makes the most sense
-
395aa67 👍 1B Is the correct answer
Show 1 more comment
-
dija123 👍 1 Answered BB is correct
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.