Question

Difficulty: MediumActivity Management: Tasks, Events, and Shared Activities

A Salesforce administrator at Nexus Biotech is configuring activity settings to allow medical sales representatives to log interaction events that involve several client stakeholders simultaneously. The administrator enables 'Allow Users to Relate Multiple Contacts to Tasks and Events' (Shared Activities). Which two statements accurately describe the standard system capabilities and record relationship rules when Shared Activities is enabled? (Select 2)

  1. A single event or task can be related to up to 50 contacts.Answer
  2. One contact must be designated as the primary contact on the activity record.Answer
  3. C
    A single shared task can be related simultaneously to up to 50 separate Account records.
  4. D
    Enabling Shared Activities automatically creates individual duplicate task records assigned to each related contact's owner.

Answer

With Shared Activities enabled, a single task or event can be related to up to 50 contacts (or leads), and one contact must be designated as the primary contact.
Enabling Shared Activities allows users to relate up to 50 contacts or leads to a single event or task. Within those related contacts, one must be designated as the primary contact for reporting and record display purposes.

Step-by-Step Solution

1
Analyze the limits of Shared Activities for Contact relationships
Salesforce Shared Activities allows relating up to 50 contacts or leads to a single activity record.
This enables sales representatives to track interactions with multiple stakeholders within one task or event without duplicating records.
2
Identify primary contact designation requirement
Salesforce requires selecting one primary contact among the related contacts.
The primary contact relationship determines default account rollup behavior and main contact association.
3
Evaluate WhatId (Related To) restrictions vs WhoId (Name) capabilities
Shared Activities expands the WhoId relationship (up to 50 contacts), but maintains the single WhatId restriction (one Account, Opportunity, Case, etc.).
Relating a task to multiple Accounts simultaneously is not supported by standard Shared Activities.

Key Concept

Shared Activities limits and behavior (WhoId vs WhatId restrictions)
Rate this question