How to Delegate Email Access for a Traveling Executive?

You work for an international organization and your CEO frequently travels to other countries. You need to enable email access and configure the account for multiple administrative assistants. What should you do?

  1. Provide the executive administrative assistants with the account password of the CEO.
  2. Enable users to specify what sender information is included in delegated messages sent from their account.
  3. Create a group of administrative assistants. Enable delegated access to the mailbox of the CEO for that group. Source Reference Answer
  4. Log into the Gmail account of the CEO. Set up and share two separate email aliases.

Community Votes

C
100%

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

Community Insight

The exam tests secure delegation versus direct access, with the common trap being the assumption that aliases or password sharing adequately solve multi-user mailbox management.

This question evaluates secure Google Workspace mailbox delegation for executive accounts. Industry best practices and community consensus strongly favor group-based delegation over credential sharing or basic aliases.

Candidates frequently select Option D because aliases appear simpler, but aliases only route incoming mail and lack the outbound sending and folder management permissions required for true administrative assistance.

Community Discussion (3 comments)

dija123 👍 1 Selected: C
delegated access makes sense
Janoss 👍 2
C makes sense, others does not.
fabioevangelo 👍 1
C is my choice... https://apps.google.com/supportwidget/articlehome?hl=en&article_url=https%3A%2F%2Fsupport.google.com%2Fa%2Fanswer%2F11946994%3Fhl%3Den&assistant_id=generic-unu&product_context=11946994&product_name=UnuFlow&trigger_context=a Using email delegation A single Google account can support up to 1000 delegates. To avoid impacting account performance, we recommend allowing a maximum of 40 concurrent users. Google Workspace admins control whether messages sent by delegates include the email address of both the account owner and the delegate, or only the account owner. Google Groups can be added as account delegates. One Group counts as a single delegate for that account. Email aliases don't support delegates because an alias isn’t a Google Account.

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 security group and enabling delegated access is the enterprise-standard approach for managing executive inboxes securely. Delegation grants assistants controlled read/write permissions without exposing the primary account credentials. Google Workspace natively supports up to 1,000 delegates per mailbox, ensuring scalability for large administrative teams.

Why the Other Options Are Wrong

Sharing passwords (Option A) directly violates zero-trust security models and complicates audit trails. Configuring sender information (Option B) merely alters message headers but does not grant functional mailbox access. Aliases function strictly as routing addresses and cannot authenticate outgoing messages or manage shared folders. Forward-only mechanisms fail to meet the collaborative demands of executive support roles.

Community Comment Notes

Test-takers overwhelmingly validate Option C as the only compliant and operationally viable solution. Multiple high-voted comments reference Google’s official delegation documentation to confirm feature limits and permission scopes. The discussion reinforces that delegation aligns with modern IAM principles while solving real-world travel support scenarios.

Official Reference

Exam Strategy

Always prioritize least-privilege access patterns and centralized identity controls when evaluating resource-sharing scenarios. Look for group-based delegation, service accounts, or role assignments rather than temporary workarounds like shared credentials or forwarding rules.

Related Analysis

← Back to PWA Study Guide