Explanation:

Bloomington Caregivers wants to share Covid-19 info with everyone, even guests. Three hard limits apply to guest user access. Guest user external OWD is always Private for all objects. No way to change it. Guest users cannot get manual sharing on any record. Sharing links or manual shares skip them. Guest users cannot join public groups or queues. They stay isolated. These rules keep guest access tightly controlled and secure.

Why Option A Is Correct
Guest user external organization-wide default are always set to Private. Salesforce locks this setting. Admins cannot make any object Public for guests. This forces explicit sharing for anything guests see.

Why Option B Is Correct
Guest user can’t access records via manual sharing. Manual share buttons and sharing links do not work for guest profiles. Only criteria-based sharing or public pages expose data.

Why Option D Is Correct
Guest user can’t be members of public groups or queues. Groups and queues are for licensed users. Guests stay outside these structures for security.

Why Option C Is Incorrect
Guest user can’t records via manual existing records. This is poorly worded and repeats B. Manual sharing is already covered.

Why Option E Is Incorrect
Guest user external organization-wide defaults are always set to Public. False. They are always Private. No exception.

References:
Salesforce Help – Guest User Security
Trailhead – Secure Guest User Access

Explanation:

Northern Trail Outfitters (NTO) is creating an Experience Cloud site where authenticated external users (independent researchers) will collaborate with internal staff. To enable this collaboration, users must be able to see and interact with each other, which requires enabling Site User Visibility.

Here’s how each option compares:

✔️ B. Site User Visibility
Enables authenticated users of the site to see other authenticated users.
Required for collaboration features like Chatter, sharing, and visibility into submissions or discussions.
This is the minimum visibility setting needed for researcher-to-staff interaction.

❌ A. None
If visibility is set to “None,” users cannot see each other, which defeats the purpose of collaboration.
Not suitable for NTO’s use case.

❌ C. Guest User Visibility
Applies to unauthenticated users (e.g., public visitors).
Not relevant here since researchers are authenticated.

❌ D. Portal User Visibility
This is an outdated term and not a standard visibility setting in Experience Cloud.
May refer to legacy portal settings, but not applicable in modern Experience Cloud configurations.

🔗 Reference:
Salesforce Help: User Visibility Settings in Experience Cloud
Trailhead: Set Up and Manage Experience Cloud Sites

Explanation:

Within a Salesforce Experience Cloud site, each topic has its own dedicated detail page. When a user navigates to this page, they can find several metrics and pieces of information that provide insight into the topic's popularity and current relevance, including:
A feed with topic updates: This allows users to see the latest posts and conversations related to that topic.
Posts that use the topic: The total number of posts is available, providing a good comparative measure of how often people are using the topic.
People following the topic: This metric indicates the level of interest in the topic among the site's user base.
People who used the topic in the last 60 days: This shows recent activity and engagement.
Related Topics and Knowledgeable People: These lists help users explore further, confirming the topic's current engagement.

Why other options are incorrect:
A. Trending Topics Channel:
While this component highlights topics that are trending overall in the site, it doesn't provide specific, detailed metrics about a single topic's popularity over time. The topic's detail page gives a deeper look into its specific activity.
B. Collaboration Dashboard:
This is a backend administrative tool for monitoring overall site activity and user engagement, not a user-facing page for tracking the popularity of an individual topic.
D. Content Management Report:
This is also an administrative tool, used by content managers to review and report on content, rather than a user-facing feature.

Explanation:

Objective:
Ursa Major Solar (UMS) is building an Experience Cloud site for local installation companies (partners) whose installers need to collaborate with their co-workers (other installers within the same company) and UMS staff. The question asks for the minimum user visibility setting required to enable this collaboration.

Why B is Correct:
In Salesforce Experience Cloud, Site User Visibility (found in Setup > Experience Workspaces > Administration > Preferences) allows authenticated users (e.g., installers with Partner Community licenses) to see other users within the same site. This setting is essential for collaboration, enabling installers to view and interact with their co-workers and UMS staff through features like Chatter, shared records, or user profiles. For UMS’s partner portal, enabling Site User Visibility ensures that installers can collaborate with each other (e.g., via group discussions) and with UMS staff, meeting the requirement for a collaborative environment.

Why A is Incorrect:
Portal User Visibility is not a standard setting in Salesforce Experience Cloud. The correct term is Site User Visibility or related sharing settings for authenticated users. This option is a distractor due to incorrect terminology.

Why C is Incorrect:
Guest User Visibility applies to unauthenticated guest users accessing public site content. Since installers are authenticated users (likely Partner Community users) collaborating with co-workers and UMS staff, this setting is irrelevant.

Why D is Incorrect:
Community User Visibility is not a standard setting in Salesforce. The correct term is Site User Visibility for Experience Cloud sites. This option is a distractor and does not apply.

Implementation:
Go to Setup > Experience Workspaces > Administration > Preferences.
Enable Site User Visibility to allow authenticated users (installers and UMS staff) to see each other’s profiles and collaborate.
Assign Partner Community licenses to installers and configure sharing rules to ensure access to relevant records (e.g., Cases or custom objects for collaboration).
Test collaboration features (e.g., Chatter posts or group membership) as an installer user.

References
Salesforce Help: Control User Visibility in Experience Cloud
Trailhead: Experience Cloud Basics

Explanation:

🌍 Scenario Overview
Northern Trail Outfitters (NTO) has created region-specific product pages for North America, EMEA, and Asia Pacific. These pages are published in an Experience Cloud site, and the site manager has already applied visibility criteria to ensure users in each region see the correct content. Now, NTO wants to further control which users see specific pages by configuring page-level visibility settings.

🔍 Understanding Page Visibility Options in Experience Cloud
Salesforce Experience Cloud allows site managers to configure page variations and assign them to different visibility options. These options determine who sees what based on user attributes, audience membership, or fallback logic.

✅ A. None
This visibility setting hides the page variation from all users.
Useful when a page is under development or temporarily disabled.
The page remains in the site but is not rendered for any audience.
✅ D. Default
The Default variation is shown to users who do not match any audience criteria.
Acts as a fallback to ensure every user sees something.
Helps prevent blank pages or access errors for unmatched users.
✅ E. Audience The most powerful visibility option.
Allows site managers to assign page variations to specific audiences based on:
Profile
Location
Custom attributes
Login status

Enables personalized experiences across regions or user types.

❌ Incorrect Options
B. Visible
This is not a valid visibility setting in Experience Cloud.
Visibility is controlled through audience targeting, not a simple “Visible” toggle.
C. Personal
“Personal” is not a recognized visibility option.
May be confused with personalization features, but it’s not part of the page visibility configuration.

🔗 References
Salesforce Help: Page Visibility in Experience Builder
Salesforce Help: Assign Audiences to Page Variations