Community-Cloud-Consultant Practice Test Questions

Explanation:

Why Option A?
The Customer Service (Napili) template allows direct editing of object pages in Community Builder.
Since the object page already exists, the fastest method is to:
Edit the page.
Drag & drop the Feed Publisher and other collaboration components (e.g., Chatter Feed).
Publish the changes.
No need to create a new page or install external apps.

Why Not Other Options?

B. Create a new object page → Redundant; editing the existing page is faster.
C. Install a collaboration Lightning app → Unnecessary; standard components (e.g., Feed Publisher) are already available.
D. Add a page variation → Overcomplicates the process for a simple update.

Key Components to Add:
Feed Publisher → Enables posts/comments.
Chatter Feed → Displays discussions.
Rich Text → For formatted content.

Steps in Community Builder:
Go to Builder > Pages > Select the object page.
Drag Feed Publisher and other components into the layout.
Click Publish.

Reference:
Customize Pages in Napili
Add Chatter Feeds to Communities

Explanation:

🔍 Let’s examine each option carefully:
🔹 A. Use Customers Account, Customer Community Plus License, and Sharing Rules – ❌
The use of Account object (business accounts) doesn't enforce a 1-to-1 relationship.
Customer Community Plus license is powerful, but sharing rules would make customer-specific data sharing harder to control at an individual level.
Too broad for tightly controlled data access.

🔹 B. Customers Account, Customer Community License, and Sharing Rules – ❌
Same problem as A — Customer Account implies business account model, not individual accounts.
Sharing rules do not scale well for individual-based access — especially if each customer should only access their own records.

🔹 C. Use Person Account, Customer Community License, and Sharing Set – ✅ Correct
Person Accounts are perfect for B2C models where each account = one customer.
Customer Community License is cost-effective and supports basic access to their own data.
Sharing Sets are designed to give access based on user's Account or Contact association, perfect for Person Accounts.
Meets the requirement: Customers can’t see other’s data unless explicitly granted.
📘 Reference:
Salesforce Help: Sharing Sets Overview

🔹 D. Use Person Account, Customer Community Plus License, and Super User access – ❌
Super User access is only available for Partner Users, not for Customer Community Plus users.
While Plus license gives more flexibility (e.g., reporting, roles), it’s overkill unless customers are collaborating or managing multiple records beyond their own.
Also, the requirement says only a few users need partner-style access — this doesn’t justify upgrading the entire community to Plus licenses.

✅ Final Recommendation:
C. Use Person Account, Customer Community License, and Sharing Set
This configuration gives:
One customer per account (Person Account)
Access to their own records (Sharing Set)
Controlled, secure visibility
Cost-effective license (Customer Community)

Explanation:

Universal Containers (UC) is migrating to a new Salesforce Experience Cloud (formerly Community Cloud) site, and they need to quickly launch a Community where users can ask questions and provide answers.

Let’s break down the options:

🔹 A. Partner Central
Used for: Business-to-business (B2B) use cases — managing reseller, distributor, or partner
Includes features like: lead distribution, deal registration, and marketing development funds.

❌ Not designed primarily for Q&A or customer self-service.
🔹 B. Salesforce Tabs + Visualforce
Used for: Full customization using Visualforce; shows Salesforce tabs as-is.

✅ Flexible, but…
❌ Not ideal for fast deployment. Requires development effort.
❌ Poor user experience compared to modern templates like Customer Service.

🔹 ✅ C. Customer Service (Correct Answer)
Purpose-built for: Customer support and self-service.
Includes: Knowledge articles, case creation, and Chatter Q&A functionality out-of-the-box.
✅ Ideal for fast deployment. It’s a Lightning template with drag-and-drop setup in Experience Builder.
✅ Supports "Ask a Question," "Answer," "Upvote", etc., which matches UC’s requirements.

🔹 D. Customer Account Portal
Used for: Authenticated users managing their account details, such as payment info or support cases.
❌ Not specifically designed for community-style Q&A.

📘 Reference:
Salesforce Help: Experience Cloud Templates
Trailhead: Build Your Own Community

Explanation:

A. Specify font family, style, and weight
Community Builder allows admins to customize typography, including font family, style (italic, normal), and weight (bold, light).
This ensures brand consistency in text across the community.

B. Apply a color scheme that is appropriate for the Universal Containers template with the color palette
The Theme Editor in Community Builder lets admins define primary and secondary colors, button styles, and background colors.
This aligns the community with Universal Containers' brand guidelines.

D. Use custom CSS to apply Universal Containers styles
For advanced branding (e.g., unique layouts, hover effects), custom CSS can be uploaded in Community Builder.
This is useful when out-of-the-box theming options are insufficient.

Why the Other Options Are Incorrect:
C. Adjust kerning values in a variety of typefaces
Kerning (spacing between characters) is too granular for standard branding and isn’t a native feature in Community Builder.

E. Adjust the pixel width of the masthead
Masthead width is typically controlled via templates or CSS, not directly in Community Builder’s theme settings.

Reference:
Salesforce Help: Customize Community Themes
Trailhead: Brand Your Community

Explanation:

Reputation in Salesforce Experience Cloud (formerly Community Cloud) is part of Gamification. It lets you award points and define levels to encourage user engagement by performing actions like posting, answering questions, or liking posts.

✅ C. Enable Reputation in the Community
Before anything else, the Reputation system must be enabled. This is done through the Community Management console under Reputation Settings.

✅ B. Configure Reputation points and levels in the Community Management console
Once Reputation is enabled, you can set up actions and how many points they earn, and define Reputation levels (e.g., "Newbie", "Expert", "MVP") based on point thresholds.

❌ A. Create a custom Lightning component for Reputation and add it to the home page
This is unnecessary. Salesforce provides prebuilt components like the Reputation Leaderboard. A custom component is only needed for highly specialized UI use cases.

✅/❌ D. Add the Reputation Leaderboard component to a page in the Community
While this can enhance visibility of Reputation, it is not required to “set up” Reputation itself. This is a nice-to-have, but not a necessary setup step for enabling or configuring Reputation. So not one of the best two correct answers.

❌ E. Add a Visualforce Reputation Leaderboard component
This is outdated. Lightning components are used in modern Experience Builder communities. Visualforce components may still work, but are no longer best practice.

📚 References:
Salesforce Help: Enable and Configure Reputation
Trailhead: Set Up Reputation Levels

Explanation:

Community Builder is the best choice for creating a Community with out-of-the-box login, logout, self-registration, and error pages. It offers prebuilt, customizable pages via Experience Builder, supporting modern templates (e.g., Customer Service, Partner Central) with drag-and-drop configuration.
Login/Logout: Standard Lightning components in Theme Settings.
Self-Registration: Configurable in Administration > Login & Registration.
Error Pages: Customizable in Experience Builder > Pages.
Reference: Salesforce Help: Experience Builder Pages.

Force.com Sites (B) requires custom Visualforce/Apex for these features, not out-of-the-box.
A is incorrect because functionality isn’t limited to Napili/Koa templates.
C is wrong as Force.com Sites needs more custom work.
E is incorrect; legacy portals are outdated, and Experience Cloud supports error pages.
Exam Tip: Choose Community Builder for modern, user-friendly Community setup unless legacy tech is specified.
Reference: Trailhead: Experience Cloud Basics.

Explanation:

Salesforce recommends designing Partner Communities to scale up to 1 million users to ensure optimal performance and maintainability. This isn’t a hard limit from a licensing standpoint, but a best practice based on underlying infrastructure, data modeling, and sharing rule complexity.

Once user volume begins approaching or exceeding 1 million, considerations such as:
Performance degradation
Longer page load times
Increased sharing recalculations
Profile, role, and group complexity
…can negatively impact user experience.

🔍 Why Other Options Are Incorrect
A. 5,000,000
Exceeds recommended design threshold; would require deep architectural review and likely custom solutioning.
B. 10,000,000
Not a realistic out-of-the-box scalability target for Experience Cloud Communities.
C. 2,000,000
Still beyond the recommended best practice for standard community implementation.

📚 Reference
Salesforce: Experience Cloud Limits and Best Practices
Salesforce Developer Guide: Community Limits

Explanation:

To specify featured topics for a Salesforce Experience Cloud Community, navigate to Community Builder (Experience Builder). In Experience Builder, go to Content > Topics > Featured Topics to select and manage topics displayed prominently on the Community’s homepage or navigation. This is part of Experience Cloud’s content management capabilities, allowing admins to curate topics for visibility.
Reference: Salesforce Help: Manage Topics in Experience Cloud.

Why Other Options Are Incorrect:
A. Community Manager: Incorrect because Community Manager (also known as Community Management) is used for moderation tasks, such as monitoring posts, managing members, and handling reported content. It does not provide functionality to manage or feature topics.
Reference: Salesforce Help: Community Management.

B. Force.com Site Settings: Incorrect because Force.com Sites are for creating public websites using Visualforce, not for managing Experience Cloud Communities or their topics. They lack the content management features of Experience Builder.
Reference: Salesforce Help: Force.com Sites Overview.

D. Sites Settings: Incorrect because “Sites Settings” is not a specific Salesforce feature or interface for Experience Cloud. It may be confused with Force.com Sites or general setup, but it does not relate to managing Community topics.
Reference: No direct Salesforce feature named “Sites Settings” exists for this purpose.

E. Community Settings: Incorrect because Community Settings (in Setup > Feature Settings > Digital Experiences) is for configuring general Community settings like enabling the Community, setting member visibility, or login preferences. It does not include topic management or featuring topics.
Reference: Salesforce Help: Set Up Experience Cloud.

Exam Tip: This question tests the Content (12%) section of the Salesforce Experience Cloud Consultant exam. Focus on Experience Builder for content-related tasks like topics, and rule out options tied to moderation (Community Manager) or legacy tech (Force.com Sites).

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.