Explanation:

To determine the correct license and edition combinations for launching a Salesforce Community that is accessible from:
Internet Explorer 9
Salesforce Mobile App

We need to examine two things:
✅ Whether the Salesforce Edition supports Communities
✅ Whether the license type supports Customer access and Community functionality

✅ What’s required?
1. Salesforce Editions that support Communities:
Enterprise Edition
Unlimited Edition
Performance Edition
(⚠️ NOT Salesforce Essentials or Professional Edition by default – they require add-ons or don't support Communities at all)

2. User License Types for Communities:
Customer Community (basic)
Customer Community Plus (advanced sharing, roles, reporting)
Partner Community (for B2B-style communities with more access)
Now let’s evaluate the options:

❌ A. Salesforce Essentials and Customer Community
Incorrect. Essentials Edition does NOT support Communities out of the box.
No ability to add Experience Cloud site licenses.

✅ B. Enterprise Edition and Customer Community Plus
Correct.
Enterprise Edition supports Communities.
Customer Community Plus provides advanced features like roles and sharing, ideal for external users needing more access.

✅ C. Professional Edition and Customer Community Plus
❌ Incorrect, even though Customer Community Plus is supported in theory, Professional Edition has limited Community capabilities and requires additional licenses and API access.
Not a recommended or reliable solution for Community Cloud implementations.

✅ D. Unlimited Edition and Customer Community
Correct.
Unlimited Edition fully supports Communities.
Customer Community is good for high-volume, self-service portals.

✅ E. Enterprise Edition and Customer Community
Correct.
Enterprise supports Communities.
Customer Community is suitable for basic use cases, and works with the Salesforce Mobile app and even legacy browsers like IE9.

⚠️ Note about Internet Explorer 9:
Official Salesforce support for IE9 is deprecated.
However, Experience Cloud (formerly Community Cloud) did support it with limitations, especially in Classic Communities or Visualforce-based pages.
Lightning-based Communities are not fully compatible with IE9.
For true IE9 compatibility, you may need to use Visualforce-based templates.

📚 References: Salesforce Editions & Licenses: Compare Features
Salesforce Help: Community Licenses
Supported Browsers

Explanation:

To enable Community users to log in to a Salesforce Experience Cloud site using Facebook and Google credentials, the Administrator should use Auth Provider and Registration Handler.

Auth Provider: This feature configures external authentication providers (e.g., Facebook, Google) in Salesforce, allowing users to log in with their social credentials. It handles the OAuth flow and redirects users to the provider’s login page for authentication.
Setup: In Setup > Auth. Providers, create a new provider for Facebook and Google, using their respective App ID and Secret. Salesforce provides out-of-the-box support for these providers, simplifying configuration.
Reference: Salesforce Help: Configure an Auth Provider.

Registration Handler: An Apex class that manages user creation or updates based on data from the external provider (e.g., email, name). The auto-generated Registration Handler template can be customized to assign profiles, roles, or contacts for Community users.
Setup: In the Auth Provider setup, select “Automatically create a registration handler template” or create a custom Apex class implementing Auth.RegistrationHandler.
Reference: Salesforce Help: Registration Handler.

Why Other Options Are Incorrect:
A. Custom Lightning Component and Apex Class: Incorrect because custom Lightning Components are not required for social login; Salesforce provides standard components (e.g., Social Login component) for Auth Providers. An Apex class is used for the Registration Handler, but it’s part of option D, not a standalone solution.
B. Single Sign-on and AppExchange: Incorrect because Single Sign-on (SSO) typically refers to SAML or OpenID Connect for enterprise authentication, not social logins like Facebook/Google. AppExchange solutions are unnecessary since Salesforce natively supports these providers.
C. Auth Provider and Flow: Incorrect because Flows are not used for social login configuration. They can automate processes but are not part of the standard setup for Auth Providers or user registration.
Exam Tip: This question tests the Implementation (22%) section of the Salesforce Experience Cloud Consultant exam. Focus on understanding Auth Providers and Registration Handlers for social logins, and rule out options involving non-standard or unrelated features like Flows or AppExchange.
Reference: Trailhead: Social Sign-On Setup.

Explanation:

Why D is the Best Fit:
Universal Containers wants to ensure customer questions are answered in a timely manner within a Community where Q&A activity occurs. That’s a perfect use case for:
✅ D. Question-to-Case Functionality
Converts unanswered or flagged Questions in a Community into Cases, so agents can handle them formally.
Enables SLAs, escalation rules, and prioritization using the standard Service Cloud toolkit.
Supports timely response and resolution with greater visibility.
📎 Salesforce Help — Question-to-Case Overview

⚠️ Why the Other Options May Not Fulfill the Requirement
❌ A. Enable Knowledge and Articles
Provides searchable help content via Knowledge Base.
Helps proactively, but doesn’t ensure customer questions get answered in real-time or within SLAs.
❌ B. Enable Entitlement and Milestone
Adds support for SLAs using Entitlements and Milestones on Cases.
Needs Cases to work—so it’s useful after questions are converted to cases (via D). Not a standalone solution here.
❌ C. Enable Case Escalation Rules
Automates escalation of Cases based on rules.
Like B, requires questions to be converted to Cases first (which only D enables).

Explanation:

The requirements describe a need for delegated sharing and management of access to partner account data (Leads and Opportunities) — specifically by Channel Managers, who should have fine-grained control over who on their team can access partner accounts and with what level of access.
This is a textbook use case for Account Teams in Salesforce.

✅ B. Leverage Account Teams
Account Teams allow users (like Channel Managers) to:
✅ Add or remove individuals (employees) to an account.
✅ Specify their level of access (Read or Read/Write) for:
Accounts
Opportunities
Contacts
Cases
✅ Manage their own group of users for account collaboration.
✅ Provide record-level access without requiring custom sharing rules or code.

This directly fulfills all 4 requirements mentioned:
Grant/remove employee access to the partner account ✅ Yes
Specify access level (Read/Read-Write) ✅ Yes
Add/remove group of employees ✅ Yes (add multiple users with different roles/access)
Manage their own group of employees ✅ Yes (Channel Managers can manage the Account Team)

❌ A. Manual Shares
Manual sharing allows record sharing but:
Only works one record at a time.
Doesn’t scale.
Cannot be managed or automated by Channel Managers easily.
Cannot share with groups.
Not maintainable or user-managed — Admins would need to intervene.

❌ C. Public Groups
Public groups are good for admin-defined sharing rules.
But users cannot manage public groups themselves.
Not a good fit for delegated management or dynamic access per partner account.

❌ D. Sharing Rules
Sharing rules are static and admin-managed.
You cannot use sharing rules to allow users to manage access dynamically.
Cannot meet the “Channel Managers should grant/remove access themselves” requirement.

📚 References:
Salesforce Help: Account Teams Overview
Trailhead: Collaborate on Accounts with Account Teams

Explanation:

A. Reputation Leaderboard
Provides visibility into user activity comparisons by displaying top contributors.
Encourages engagement by showing rankings (fulfilling the third requirement).

B. Featured Topics
Highlights new and recommended discussions prominently on the homepage.
Helps users quickly find trending or important topics (first requirement).

D. Contact Support Button
Offers a direct way to contact Universal Containers (second requirement).
Can link to a case form, chat, or email for quick assistance.

Why the Other Options Are Incorrect:
C. Breadcrumb → Navigation aid, but doesn’t address any of the three requirements.
E. Record Detail → Displays data for a single record, irrelevant to collaboration or quick access.

Reference:
Lightning Components for Communities
Leaderboard Setup
Final Answer: A, B, D ✅ Let me know if you need implementation details!

Explanation:

The first step to set up partner users for a Salesforce Experience Cloud Community is to create the account and enable it as a partner account. This establishes the partner company as a valid entity in Salesforce, allowing the creation of partner users who can access the Community.

Why: Before partner users can be added to the Community, an account must exist for the partner company. Enabling the account as a partner account (in Setup > Feature Settings > Communities > External Account Hierarchy) activates partner-specific features, such as the ability to create partner users with the appropriate profile and role for Community access.
How: In Salesforce, navigate to Accounts, create a new account for the partner company, and enable it as a partner account by selecting “Enable as Partner” from the account’s action menu. This step is foundational for associating contacts and users with the partner account.
Reference: Salesforce Help: Enable Partner Accounts.

Why Other Options Are Incorrect:
A. Create a partner profile for the company: Incorrect because creating a partner profile is not the first step. Profiles are assigned to users after the partner account is enabled and contacts are created. The account must exist first.
Reference: Salesforce Help: Partner User Profiles.

B. Add partner contacts to the Community as members: Incorrect because contacts cannot be added to the Community without an existing partner account. Contacts are created under the account, and enabling the account as a partner is a prerequisite.
Reference: Salesforce Help: Add Community Members.

D. Allow partner users to self-register and gain access: Incorrect because self-registration requires the partner account and user setup to be completed first. Additionally, self-registration is not typically used for partner users, as admins usually control access for security reasons.
Reference: Salesforce Help: Self-Registration.

Exam Tip: This question aligns with the Implementation (22%) and Sharing and Security (20%) sections of the Salesforce Experience Cloud Consultant exam. Focus on the sequence of setup steps for partner users, starting with account creation and enablement.
Reference: Trailhead: Partner Community Setup.

Explanation:

When using the Koa Community Template (a Lightning-based Experience Builder template), you manage pages directly through the Experience Builder interface, not via Community Manager or custom development tools.

Here’s what makes Option C correct:

✅ C. Create a new page in the Community Builder
Direct method supported for all Lightning-based templates including Koa.
Allows you to choose from:
Standard page types (e.g., Article Detail, Record Detail)
Blank pages or custom layouts
Pages created here can be fully styled using drag-and-drop Lightning Components.
📎 Reference: Salesforce Help — Create Pages in Experience Builder

❌ Why the Other Options Are Incorrect
A. Install the Community Page Manager from the AppExchange
No such required app — page creation is native to Experience Builder.
B. Create a new page from in the Community Manager
Community Manager handles user access and preferences, not page creation.
D. Clone an existing page in the Community Builder
While cloning is possible, the question asks to create a new page, not replicate one.
E. Ask your developer to create a new Visualforce Page
Not needed for Lightning-based templates like Koa. Visualforce is legacy and typically used in Classic Sites.

Explanation:

In a Salesforce Customer Service Community, users can ask and answer questions using Chatter Questions. If customers want to be notified about new posts related to specific products, the best solution is to subscribe to Topics.

✅ D. Subscribe to Topics associated with Questions and posts
Topics in Salesforce are tags or labels applied to questions, articles, or posts (e.g., “Trekking Poles”, “Hiking Boots”).
When a user subscribes to a Topic, they will receive notifications when:
New questions or posts are tagged with that topic.
New answers are posted under that topic.
This is the recommended and user-friendly approach to keep customers informed about updates related to specific products.

📌 This aligns exactly with the requirement:
“Customers have asked how to be notified of new questions or information posted in the Community about specific products.”

❌ A. Subscribe to an RSS feed about Questions and posts
RSS feed support is not native to Salesforce Communities.
Not a supported or practical option for most users.

❌ B. Subscribe to Questions and posts
Salesforce does not allow subscribing to all questions or posts globally.
Users can follow individual questions, but that’s not scalable or automatic.

❌ C. Follow users associated with Questions and posts
Following a user only notifies you when that specific user posts.
It does not ensure notifications about a specific product or topic.
Doesn’t meet the requirement of being notified about products, not people.

📚 References:
Salesforce Help: Follow and Subscribe in Chatter
Trailhead: Collaborate in Chatter

Explanation:

1. B: The person who posted the question can select the best answer
In Chatter Questions, the original poster (OP) can mark a reply as the "Best Answer", which pins it to the top of the thread.
This ensures the solution is immediately visible to others.

2. D: An authorized user can pin a post to the top of the feed
Users with moderation permissions (e.g., Community Managers, Admins) can manually pin posts to highlight important content.
Requires "Moderate Chatter" or similar permissions.

3. E: The community moderator can select the best answer
Moderators can override or assign a "Best Answer" if the OP doesn’t act.
Critical for maintaining thread quality.

Why Other Options Are Incorrect?
A: Any community member can pin a post → False. Only authorized users (OP, moderators, or admins) can pin.
C: The person who answered the question → False. Answerers cannot self-promote their posts as "Best Answer."

Reference:
Salesforce Help: Best Answers in Chatter
Moderation Permissions

Explanation:

To meet Universal Containers' requirements for their Support Community, where customer and partner users use Customer Community and Partner Community licenses, customer users need to see all cases for their account (including those opened by colleagues) and collaborate with all Community users, the Salesforce Admin should take the following two actions:

A. Select the Community User Visibility checkbox:
Why: This setting enables customer users to collaborate with all Community users (both customer and partner users) by allowing them to view profiles, posts, and files shared in the Community, as well as participate in Chatter groups and discussions. It ensures visibility for collaboration across the Community.
How:In Setup > Feature Settings > Digital Experiences > Settings, check the “Community User Visibility” option to enable external users (like those with Customer Community or Partner Community licenses) to see and interact with other Community users’ content.
Reference: Salesforce Help: Community User Visibility.

D. Create a Sharing Set on the Case object:
Why: A Sharing Set grants access to records (e.g., cases) based on the user’s account or contact. For customer users to see all cases opened for their account (including those by colleagues), a Sharing Set on the Case object can be configured to provide Read or Read/Write access to all cases associated with their account. This is critical for external users with Customer Community licenses, as they don’t inherit the same sharing rules as internal users.
How: In Setup > Security > Sharing Settings, create a Sharing Set for the Customer Community profile, selecting the Case object and granting access based on the user’s account. For example, set “Read Only” or “Read/Write” for cases where the Case.AccountId matches the user’s AccountId.
Reference: Salesforce Help: Sharing Sets for External Users.

Why Other Options Are Incorrect:
B. Enable Super User access for customer users: Incorrect because Super User access is specific to Partner Community users, not Customer Community users. It allows partner users to view records owned by other users under the same account or role hierarchy, but it’s not applicable for Customer Community licenses and doesn’t address collaboration with all Community users. Reference: Salesforce Help: Super User Access.

C. Set up Delegated Admin access for customer users: Incorrect because Delegated Admin access allows users to manage specific administrative tasks (e.g., user management, role assignments) within the Community. It does not grant visibility to cases or enable collaboration with other Community users, which are the core requirements.
Reference: Salesforce Help: Delegated Administration.

Exam Tip: This question aligns with the Sharing and Security (20%) and Implementation (22%) sections of the Salesforce Experience Cloud Consultant exam. Focus on understanding Sharing Sets for external users and the Community User Visibility setting for collaboration. Rule out options like Super User or Delegated Admin that apply to specific license types or unrelated administrative tasks.
Reference: Trailhead: Sharing and Security in Experience Cloud.

Explanation:

Universal Containers is using a Napili template (now known as the Customer Service template) for its Experience Cloud (Community). When users click on a Topic, a list of related Knowledge Articles is displayed.
The VP of Support wants to limit the number of articles shown to only 10 per topic — this is about controlling UI display behavior, not changing article content or visibility settings.

✅ A. Set the Number of Articles property inside the Page Editor
This is the correct and standard way to limit the number of articles shown in the Top Articles for Topics or Featured Topics components.
In Experience Builder (Community Builder):
You can select the component (e.g., Top Articles for Topics)
In the component properties panel, there is a “Number of Articles” setting
You can set it to 10 or any other number
This directly satisfies the requirement.

❌ B. Update Knowledge Settings inside Setup
Knowledge settings control things like language, article types, and data categories — not how many articles are displayed in the Community.

Not relevant for display control within templates.

❌ C. Make sure Top Articles for Topics is enabled in Community Management
This enables the component, but does not control the article count.
It’s a prerequisite, not a solution to limiting the number shown.

❌ D. Add the Top Articles component inside the Community Builder
Adding the component is necessary, but does not fulfill the requirement alone.
The question is not about adding the component, but about controlling how many articles appear — which is done by setting the number of articles in the component’s properties (Option A).

📚 References:
Salesforce Help: Customize Knowledge in Communities
Trailhead: Create and Customize a Community

Explanation:

Why This Is Correct
In Salesforce Experience Cloud, community membership can be controlled based on user profiles or permission sets. Since Universal Containers already has distinct profiles for customer segments, the simplest and most scalable way to restrict access is by selecting only the U.S. customer profile when configuring community membership.
This is done in the “Members” section of the Experience Workspaces or Digital Experiences setup.
Only users whose profiles are included will be allowed to access the new U.S. community.
Profiles allow bulk assignment, making it easier to manage ongoing membership logic.
🔎 Perfect fit for communities serving different regional user groups!

❌ Why The Other Options Don’t Work
A. Add U.S. users to the Community sharing set
Sharing Sets don’t govern membership—they control record visibility once users are inside the community.
C. Add the U.S. customer public group
Public Groups can be used in Sharing Rules, but not for community member assignment directly.
D. Add each U.S. customer from their contact record
Way too manual and inefficient—membership isn't set via contact records, but from profiles/permission sets at the user level.