Explanation:
A Chatter Stream (also called a "Custom Feed" or "Stream") allows users to aggregate posts, updates, and announcements from multiple Chatter groups, records (e.g., Accounts, Opportunities), and specific users (e.g., CEO) into a single, unified feed. This provides a consolidated view of collaboration across the organization without navigating to each group or record individually.

Correct Option: D

Chatter Stream is a customizable feed that pulls from selected sources: groups, records, people, and topics.

The administrator or users can create streams to combine CEO announcements, group discussions, and record updates.

Streams appear in the Chatter tab alongside the default "Following" feed.

Perfect for executives or teams needing a single view of important activity.

Incorrect Option: A

A Chatter Group is a single collaborative space for a specific team or topic. It does not aggregate multiple groups or record updates into one place.

Users would have to visit each group separately.

Does not meet "single place" requirement.

Incorrect Option: B

Chatter Daily Digest is an email summary of activity, not an interactive, real-time single view within Salesforce.

It provides periodic snapshots, not a live feed.

Not suitable for ongoing collaboration and updates in one place.

Incorrect Option: C

Chatter Feed (e.g., the default "Following" feed) shows updates from people and records the user follows, but it does not allow curated aggregation of multiple groups and specific announcements by an administrator.

Less flexible than a custom Stream.

Reference:
Salesforce Help Article: Create and Manage Chatter Streams – Use Chatter streams to aggregate posts from multiple groups, records, and people (e.g., CEO) into a single, consolidated feed. Chatter groups, daily digest emails, and default feeds do not offer the same level of curated aggregation across diverse sources.

Explanation:

This question evaluates the administrator's proficiency in managing Service Level Agreements (SLAs). The goal is to identify a tool that can monitor the elapsed time of a record (2 hours) and automatically perform both a field update (reassignment to a queue) and a notification (alerting a manager).

🟢 Option C: Case Escalation Rules
Case Escalation Rules: This is the correct feature because it is designed to monitor how long a Case has been open based on specific criteria. An administrator can set an escalation action to trigger after 2 hours for unassigned cases, which will automatically change the owner to the "Urgent Case Queue" and simultaneously send an email alert to the support manager.

🔴 Option A: Case Scheduled Reports
Case Scheduled Reports: While reports can be used to identify cases that have been open for more than 2 hours, they are not an automation tool. Scheduled reports simply send a snapshot of data via email at specific times; they cannot independently change record owners or provide the immediate, real-time response required to move cases to an urgent queue.

🔴 Option B: Case Dashboard Refreshes
Case Dashboard Refreshes: Dashboards provide a visual representation of data but are passive monitoring tools. Even if a dashboard is refreshed to show stagnant cases, it lacks the logic to execute actions. It cannot automatically reassign a record or send alerts, as it is intended for data visualization rather than workflow automation.

🔴 Option D: Case Assignment Rules
Case Assignment Rules: These rules are used to route a Case to a specific user or queue the moment it is created or manually updated. They do not have a time-tracking engine and cannot "wait" for 2 hours to pass before taking action, making them unsuitable for requirements involving duration-based triggers or time thresholds.

🔧 Reference:
→ Salesforce Help: Escalation Rules
This official Salesforce Help topic confirms that escalation rules automatically reassign cases and can notify users when cases remain open for a specified period.

Explanation:
By default, custom objects do not automatically support activities (tasks and events). To allow users to relate tasks to a custom object (Course), the administrator must enable Allow Activities on the Course object in Object Manager. This setting adds the necessary activity fields and related lists to the object, enabling the Task's "Related To" lookup to include Course records.

Correct Option: B

Allow Activities is a checkbox on the custom object definition (Object Manager → Course → Edit → "Allow Activities").

Once enabled, users can relate Tasks and Events to Course records.

The "Related To" (Name) lookup field on Task will list Course records as valid targets.

No code or complex configuration required.

Incorrect Option: A

Sharing rule grants record-level access (read/write) to Course records but does not enable activities on the Course object.

If Allow Activities is off, even full access cannot relate a task to a Course.

Incorrect solution.

Incorrect Option: C

Adding Open Activities related list to the Course page layout displays existing activities but does not enable the ability to relate tasks to Course records.

The related list appears only after Allow Activities is enabled.

This is a display change, not a functional enablement.

Incorrect Option: D

Updating the user's profile to grant Edit access to the Task object allows creating/editing tasks but does not enable Course as a valid "Related To" target. The user can create tasks related to Accounts, Contacts, Opportunities, etc., but not to Course until Allow Activities is turned on. Incorrect focus.

Reference:

Salesforce Help Article: Allow Activities on Custom Objects – To relate tasks and events to a custom object, enable "Allow Activities" in the object's properties. Sharing rules, page layout changes, and Task object permissions do not activate this relationship. This setting is required for the "Related To" lookup on activities to include the custom object.

Explanation:
The requirement specifies a private discussion forum where new members can be added, but non-members should not be able to see any information about the group (including its existence, description, or member list). A Chatter Unlisted Group is the correct choice because unlisted groups do not appear in search results, browse lists, or user profiles for non-members, making the group completely invisible to outsiders.

Correct Option: A

Chatter Unlisted Group is hidden from non-members; they cannot see the group exists, its members, or its posts.

Administrators or members can add new members directly.

Perfect for sensitive discussions requiring maximum privacy.

Non-members cannot request to join because they cannot find the group.

Incorrect Option: B

Chatter Private Group requires approval to join, and non-members can still see that the group exists (group name, description, and member count may be visible).

Non-members can also see the group in search results and request membership.

Does not meet "non-members cannot see any information about the forum."

Incorrect Option: C

Chatter Public Group is visible to everyone; anyone can view posts and join without approval.

Completely inappropriate for sensitive records.

Opposite of the requirement.

Incorrect Option: D

Private Chatter Channel is not a standard Chatter group type. Chatter Channels are part of Slack integration or specific collaboration features, not native groups for record discussions.

Not available as a standard group privacy setting.

Reference:
Salesforce Help Article: Chatter Group Types – Unlisted groups are completely hidden from non-members (no visibility of name, members, or posts). Private groups are visible but require approval to join. Public groups are open to all. Unlisted groups are best for sensitive discussions.

Explanation:

This question tests how to structure campaigns for effective reporting in Salesforce. The requirement is to track ROI both at the individual event level (monthly) and at the overall series level. This requires a parent-child relationship between campaigns to enable roll-up reporting.

✅ Correct Option:

C. Use Campaign Hierarchy where the monthly events roll up to a parent Campaign.
Campaign Hierarchy allows multiple child campaigns (monthly events) to roll up into a parent campaign (event series). This structure enables reporting on both individual campaign performance and aggregated ROI at the series level. It simplifies tracking and provides built-in roll-up metrics, making it the most efficient and scalable solution for this requirement.

❌ Incorrect Options:

A. Create individual Campaigns that all have the same name.
Using the same name does not create any relationship between campaigns. Salesforce treats them as separate records, making it difficult to aggregate data or report on overall ROI for the event series.

B. Configure Campaign Member Statuses to record which event Members attended.
Campaign Member Statuses track engagement within a single campaign but do not link multiple campaigns together. They do not support roll-up reporting across multiple events or series.

D. Add different record types for the monthly event types.
Record Types help categorize campaigns but do not establish relationships or enable roll-up reporting. They do not help aggregate ROI across multiple campaigns.

🔧 Reference:
⇒ Salesforce Campaign Hierarchy
Explains how campaign hierarchy enables parent-child relationships and roll-up reporting for campaign performance.