Free COMMUNITY-CLOUD-CONSULTANT Practice Test Questions and Answers (2026)

Salesforce Experience Cloud provides specific branding controls for system-generated emails, such as Chatter notifications. Within the Administration workspace, under the "Emails" section, administrators can directly configure several branding elements. This includes setting a custom "From Name" and "From Email Address" to control the sender's identity. Additionally, administrators can upload a company logo to be displayed in the email header and can define custom text or HTML for the email footer, ensuring all communications align with the company's brand identity.

C. Email format: The overall layout and structure of the notification email body are determined by Salesforce's default templates and cannot be fundamentally altered, only the header and footer can be customized.

D. Fonts: There is no global setting to change the font for the entire email. While fonts can be styled within the custom HTML of the header and footer, it is not a direct customization option for the email as a whole.

1. Salesforce Help: Brand Your Experience Cloud Site's Emails. This document explicitly details the customization options. It states

"You can change the branding on these emails by adding your logo

changing the colors

and modifying the footer text." It also provides instructions: "In the From Name and From Email Address fields

enter a name and email address to appear in the From field of the email header." This directly supports options A

B

and E.

2. Salesforce Help: Email Templates in Experience Cloud. This guide reinforces the branding capabilities

explaining

"You can use the default email templates or create your own to ensure that every email sent from your site is branded." It then directs users to the Administration > Emails page where the Header (for logo)

Footer

and From Address settings are located.

Salesforce provides a native feature called Salesforce Surveys, which is the standard and most efficient way to accomplish this task. This feature includes a standard "Survey" Lightning component that can be dragged and dropped onto any page within an Experience Cloud site using the Experience Builder. To trigger the survey upon case closure, an administrator would typically use a Flow to automatically send a survey invitation link to the customer. The link directs the customer to the survey hosted within the community, which is rendered using the standard component. This approach leverages built-in functionality without requiring custom development or third-party applications.

A. Build a Surveys Lighting Component: This is incorrect because it involves unnecessary custom development. A standard, fully functional component already exists for this purpose, making a custom build inefficient.

B. Use an AppExchange Survey Lightning Component: This is incorrect because relying on a third-party AppExchange package is not necessary. Standard Salesforce functionality fully supports this requirement. AppExchange solutions are for extending, not replacing, core features.

C. Build a Surveys Visualforce Page: This is incorrect as Visualforce is a legacy UI framework. For modern Experience Cloud sites built with Lightning, using a standard Lightning component is the best practice.

1. Salesforce Help

Add a Survey to Your Experience Cloud Site: "Use the Survey component to embed a survey in your Experience Cloud site page. You can add the component to any page. From Experience Builder

drag the Survey component from the Components panel onto the page." This directly confirms the existence and purpose of the standard component.

2. Salesforce Help

Salesforce Surveys: "Use Salesforce Surveys to create engaging surveys to collect feedback and data from your users or customers... Add surveys to your Experience Cloud sites to gather feedback from members." This establishes Salesforce Surveys as the primary tool for this use case.

3. Salesforce Help

Automate Sending Surveys: "Use Process Builder or Flow Builder to email survey invitations to users when a record is created or updated." This document explains the automation part of the scenario (triggering on case closure)

which complements the use of the standard component for displaying the survey.

A Salesforce Administrator has several methods to test and validate an Experience Cloud site's functionality. The three most direct and distinct methods are:

1. Impersonation (Login As): The administrator can log in as a specific external user directly from that user's contact record. This allows the admin to see the site exactly as that user does and test features specific to their profile and permissions.

2. Direct Access (Internal User): As an internal user who is a member of the site, the administrator can access it via the App Launcher. This validates the experience for internal employees, partners, or support agents who use the site.

3. End-to-End Login (Test User): The administrator can use the credentials of a dedicated test user (a customer or partner user) to perform a clean login through the site's public login page. This validates the entire authentication process and user experience from an external perspective.

A. Select a Customer user record and select the Login option: While technically possible, this describes the same "Login As" feature as option B. Option B (from the contact record) is a more common administrative workflow. Choosing B, C, and D provides three distinct validation methods.

E. Preview the Community as a specific Community user in the preview mode of the Community builder: The preview mode in Experience Builder is a design tool to check layout and audience visibility. It is not a full, functional login and cannot be used to reliably validate features involving data creation, Apex, or complex flows.

1. For option B: Salesforce Help

"Log In to an Experience Cloud Site as a User". This document states

"From the contact record

select Log in to Experience as User." This confirms the ability to impersonate a user directly from their contact record for validation.

2. For option C: Salesforce Help

"Who Can Access Experience Cloud Sites?". This guide explains that internal users can be members of a site. Standard Salesforce navigation

including the App Launcher

is used by internal users to access the sites they are members of.

3. For option D: Salesforce Help

"Create Experience Cloud Site Users". This documentation outlines the process of creating external users from contact records. This process generates a user with login credentials that can be used for testing the standard login flow on the site's login page.

4. For option E (Why it's incorrect): Salesforce Help

"Preview Your Experience Cloud Site". This article clarifies the purpose of the preview mode: "Previewing your site is a great way to see what it looks like for a specific audience... The preview shows a non-functional

high-level view of your site’s layout and branding." This confirms it is not a true login for feature validation.

The Customer Community Plus license is the most appropriate choice. While a standard Customer Community license can be configured to run reports, the Customer Community Plus license provides more robust capabilities, including the ability to create, edit, and run reports and dashboards. Crucially, this license type includes access based on a role hierarchy and advanced sharing rules, which are essential for a "large customer" to control data visibility and generate meaningful reports on their own records. This makes it the definitive solution for meeting this requirement.

B. Lightning External Apps: This license is designed for building custom digital experiences with a focus on custom objects and is not the primary choice for deep, standard CRM reporting functionality.

C. High Volume Customer Portal: This is a legacy portal license type. Modern implementations use Experience Cloud licenses like Customer Community and Customer Community Plus. It is not the correct current solution.

D. Portal Manager: This is not a license type. It refers to a permission or role that allows a community user to manage other users within their same account, not to run reports.

3. References

1. Salesforce Help: Experience Cloud User Licenses

Reference: This document provides a detailed comparison of different Experience Cloud licenses.

Citation: In the "License Details" or feature comparison table, it explicitly states that Customer Community Plus users can "Create, edit, and run reports" and have "Roles and advanced sharing." In contrast, the standard Customer Community license notes users "Can run reports if the 'Run Reports' permission is enabled," but lacks the creation/editing and advanced sharing capabilities, making the Plus license the superior and more direct solution for this business need.

2. Salesforce Help: Who Can See What in Experience Cloud Sites

Reference: This guide explains the access and visibility models for different licenses.

Citation: The section on "Experience Cloud Site User Visibility" details how role hierarchies, which are only available with Customer Community Plus and Partner Community licenses, are fundamental to controlling record access. This directly impacts what data a user can see in a report, making the Customer Community Plus license essential for complex reporting scenarios.

3. Salesforce Help: Report and Dashboard Considerations for Experience Cloud Sites

Reference: This document outlines specific considerations for using reports in communities.

Citation: It clarifies that external users' ability to see data in reports and dashboards is determined by their profile, sharing rules, and role hierarchy. Since the Customer Community Plus license is the one that introduces a role hierarchy for customers, it is the designated license for advanced reporting needs.

The Experience Builder (formerly Community Builder) provides several declarative, point-and-click options for branding. Within the Theme panel, users can directly upload a Company Logo, select different fonts and sizes for Header Fonts, and set an Overlay Colour on components like the Hero section to improve text readability over background images. These are all standard, out-of-the-box branding features that do not require code.

A. Custom Fonts: Implementing a truly custom font (one not in the standard list) is not a declarative feature; it requires uploading the font as a static resource and applying it via custom CSS.

C. Accessibility Colours Selection: This is not a specific feature. While the color palette includes a contrast checker to aid accessibility, it is a verification tool, not a distinct feature for "selecting" pre-defined accessible colors.

1. Salesforce Help - Update Your Site's Branding in Experience Builder: This document details the declarative options in the Branding panel.

Images: "Upload a logo to represent your company." (Supports option B)

Fonts: "Choose fonts for headings and body text from the provided menus." (Supports option E)

2. Salesforce Help - Hero Component: This document describes the properties of the standard Hero component.

Background Color: "Select a color to overlay the background image or video." (Supports option D)

3. Salesforce Help - Use Custom Fonts in Your Experience Cloud Site: This document explicitly states the process for using non-standard fonts.

"To use custom fonts in your Experience Cloud site

upload the font file to your site as a static resource. Then

use custom CSS to apply the font to the desired elements." (Demonstrates why option A is incorrect as it's not declarative).

The foundational step to onboard a new partner organization into a Salesforce Partner Community is to first represent that organization within Salesforce. This is accomplished by creating a business Account for the partner company. Subsequently, this Account must be explicitly enabled as a partner account. This action is critical as it establishes the partner relationship in the system, automatically creates a partner role in the role hierarchy, and is the absolute prerequisite for creating partner users associated with that company. Without a partner-enabled account, you cannot proceed to create contacts and enable them as community users.

A. Add partner contacts to the Community as members: This step occurs much later. Contacts must first be created under a partner account and then enabled as partner users before they can be granted membership to a community.

C. Allow partner users to self-register and gain access: Self-registration is a configuration for how users can join, not the initial administrative step to set up a specific, known partner company. The question implies a direct setup by an admin.

D. Create a partner profile for the company: While a partner profile is necessary to create a partner user, a suitable profile (e.g., the standard 'Partner Community User') likely already exists in an established community. The first action specific to onboarding a new company is creating its account record.

1. Salesforce Help Documentation: Create Partner Accounts. This document explicitly states the initial procedure: "To create partner users

you first create a partner account. Partner accounts are Salesforce accounts that a channel manager uses to manage partner organizations... On an existing business account

open the dropdown menu and click Enable as Partner." This confirms creating and enabling the account is the primary step.

2. Salesforce Help Documentation: Create Partner Users. The prerequisites section of this guide notes: "Before creating partner users

make sure that you have a partner account and at least one partner profile to use." This establishes that the partner account must exist before user creation can begin.

3. Trailhead Module: Get Started with Experience Cloud for Partners. In the unit "Enable Partner Accounts and Create Partner Users

" the prescribed workflow begins with enabling an Account as a partner account

followed by creating contacts

and then enabling those contacts as partner users. This reinforces the correct sequence of operations.

Give every Main Distributor access to two communities:

1) a single “Main Distributor” community where all Main Distributors are members and can collaborate with one another, and

2) one separate community that contains the Main Distributor plus ONLY the Regional Distributors it manages.

Because community membership is assigned per user, a partner user can belong to multiple communities. Members of one community are invisible to users who aren’t members of that same community, so Regional Distributors assigned to different Main Distributors cannot see or collaborate with each other, while Main Distributors can still meet together in their shared community.

B. One community with user-visibility off blocks Regional-to-Regional collaboration and prevents Main Distributors from finding each other.

C. Lacks a place where all Main Distributors can collaborate across geographies.

D. Creates hundreds of communities, prevents Regional Distributors managed by the same Main Distributor from collaborating in one place, and is costly to maintain.

1. Salesforce Help

“Add Members to Your Community” → “Users Can Belong to Multiple Communities”

Summer ’24 release notes (help.salesforce.com/articleView?id=networksaddmembers.htm) section “Membership Rules”.

2. Digital Experiences Implementation Guide

“Manage Community Membership and Visibility”

p. 47-49: “Members of one community can’t see or interact with users who aren’t members of that community.”

3. Salesforce Help

“Community User Visibility Settings” (help.salesforce.com/articleView?id=networkssettingsuservisibility.htm) – explains that disabling visibility hides all users inside the community.

The Napili, Koa, Kokua, and Aloha templates are all built on the Salesforce Lightning framework. A core feature of this framework is its responsive design, which ensures the user interface automatically adapts for optimal viewing and interaction across various devices, including desktops, tablets, and smartphones. This inherent responsiveness makes them the ideal choices for building a mobile-ready community from the start, providing a modern, mobile-first experience without requiring extensive custom development for different screen sizes.

D. Visualforce + Tabs: This template is not built on the responsive Lightning framework. It requires significant custom development with Visualforce and CSS to achieve a mobile-friendly experience, unlike the other inherently responsive options.

1. Salesforce Help - Which Experience Cloud Template Should I Use?: This document describes the various templates. It explicitly states that templates like Customer Service (formerly Napili) are "powerful

responsive

self-service" solutions. The Aloha

Koa

and Kokua templates are also based on the same responsive Lightning technology.

Reference: Salesforce Help

Article 000322239

"Which Experience Cloud Template Should I Use?".

2. Salesforce Help - Salesforce Tabs + Visualforce: This documentation clarifies that the "Salesforce Tabs + Visualforce" template allows you to use your org's tabs and Visualforce pages. It is not a Lightning-based template and does not offer the out-of-the-box responsive design characteristic of the other options.

Reference: Salesforce Help

Article 000322239

"Which Experience Cloud Template Should I Use?"

Section on "Salesforce Tabs + Visualforce".

3. Salesforce Help - Experience Builder Overview: The documentation on Experience Builder

the tool used to customize these templates

emphasizes its role in creating responsive sites that work on any device. This capability is native to the Lightning-based templates (Napili

Koa

Kokua

Aloha).

Reference: Salesforce Help

Article 000319816

"Experience Builder Overview".

The most direct and standard method for an administrator to add a company logo to the Experience Cloud (formerly Community) login page is through the Administration settings within the Experience Workspace. The "Login & Registration" section provides a specific "Logo File" upload option, allowing the administrator to brand the default login page without needing to create custom pages or write code. This declarative feature is designed precisely for this purpose.

B: Specifying a new custom login page is a more complex approach. It's unnecessary when the requirement is simply to add a logo to the standard login page.

C: The CSS editor is used for advanced styling and branding overrides. The primary mechanism for adding the login page logo is the dedicated upload field, not CSS.

D: Login Flows are used to customize the user's path after they enter credentials, such as for multi-factor authentication or accepting terms, not for branding the initial login page itself.

1. Salesforce Help - Customize Your Site’s Login Page: This document explicitly outlines the procedure. It states

"From Administration | Login & Registration

you can brand your login page with your logo... Logo File—Upload a file for your logo. The file is stored in the site’s asset library." This directly supports option A as the correct method.

Source: Salesforce Help

Experience Cloud

"Customize Your Site’s Login Page".

2. Salesforce Help - Login & Registration Page Settings for Experience Cloud Sites: This page details the available settings within the Login & Registration section of the Administration workspace. It lists "Logo File" as a configurable option for the login page.

Source: Salesforce Help

Experience Cloud

"Login & Registration Page Settings for Experience Cloud Sites".

For authenticated users in an Experience Cloud site, the language displayed is fundamentally determined by the language setting on their individual User Profile. This is the primary, out-of-the-box mechanism Salesforce uses to present the site in the user's preferred language upon login. While other components can be used to modify this setting, the User Profile's language field remains the single source of truth for the user's default language preference. Ensuring this profile data is correct is the foundational step.

A. Develop a custom lightning component...: Incorrect. Custom development is unnecessary as standard Salesforce functionality natively supports this requirement through user profile settings and standard components.

B. Install the Google Translation component...: Incorrect. This provides on-the-fly machine translation, which is different from serving a professionally translated site based on user preference, the standard Salesforce approach.

D. Place the Language Picker Component...: Incorrect. While the Language Picker is a standard component that allows users to change their language, it works by updating the language setting on the User Profile. Option C describes the core mechanism itself, making it more fundamental and precise.

E. Multi-Language support is not available...: Incorrect. Multi-language support is a core and robust feature available for all Experience Cloud site templates, including the Napili (Customer Service) template.

References

1. Salesforce Help Documentation: How Does My Experience Cloud Site Determine Which Language to Use?

Content: This official document explicitly states the hierarchy for language determination.

Quote/Section: Under the section for authenticated users, it specifies, "For authenticated users, the language is determined by the language setting on their user account." This directly supports option C as the primary mechanism.

Source: Salesforce Help Portal.

2. Salesforce Help Documentation: Give Users a Choice with the Language Picker Component

Content: This document describes the function of the Language Picker component.

Quote/Section: It clarifies the component's behavior for logged-in users: "For authenticated users, the language they select is saved to their user profile, and they see the site in that language the next time they log in." This demonstrates that the component is a user interface for modifying the fundamental setting described in option C, not a separate mechanism.

Source: Salesforce Help Portal.

3. Salesforce Help Documentation: Update and Edit Translations in Experience Builder Sites

Content: This guide on managing translations reinforces the language framework.

Quote/Section: The process of exporting and importing translation files via the Translation Workbench is predicated on having defined languages for the site and for users. The user's language setting is the key that determines which translated content is served to them.

Source: Salesforce Help Portal.

The most efficient and accurate method to simplify topics while retaining article associations is to use the merge feature. When topics are merged in the Content Management Workspace, Salesforce automatically retags all articles and feed posts from the source topics with the master topic's name. This action consolidates the topic structure as required for the rebranding, preserves the link between articles and the new simplified topic, and maintains a seamless user experience by redirecting from old topic pages.

B. Keep existing Topics and reassign Articles to newly created Topics: This is a highly inefficient, manual process that is prone to error and does not leverage the platform's built-in capabilities for this exact scenario.

C. Delete existing Topics and assign Articles to newly created Topics: Deleting a topic permanently removes its association from all articles and posts. This would require the administrator to manually re-tag all affected articles, which is laborious and unnecessary.

D. Mark old Topics as Inactive and assign Articles to the new Active Topics: Salesforce does not have a feature to mark individual topics as "Inactive." Topics are either present and used, or they are deleted or merged.

1. Salesforce Help - Merge Topics: "You can merge topics to consolidate similar topics and make it easier for users to find information in your site. When you merge topics

Salesforce redirects users from the old topic detail pages to the new one and retags all feed items with the new topic name." This is performed in Experience Workspaces | Content Management | Topics.

2. Salesforce Help - Delete Topics: "When you delete a topic

it’s permanently removed from all posts and records. All the topic’s followers lose their followership." This confirms that deleting a topic breaks the association with content like articles.

3. Salesforce Help - Assign Topics to Knowledge Articles: This document outlines the process of assigning topics but highlights that merging is the correct procedure for consolidation. The manual reassignment described in options B and C is a workaround

not the intended solution for simplification.

The core requirements are for customers to manage complex hierarchies and create their own Accounts and Contacts. This level of access and control necessitates a license with role-based sharing capabilities. The Customer Community Plus license is specifically designed for such B2B scenarios, providing users with roles and advanced sharing that allows them to own and manage records like Accounts. The standard Customer Community license does not include roles and is insufficient for this use case.

Given the "high volume of customers," offering both the member-based (Customer Community Plus) and login-based (Customer Community Plus Login) licenses provides Universal Containers with the flexibility to choose the most cost-effective model based on user login frequency.

A. Customer Community Login: This license does not provide users with roles or the advanced sharing capabilities required to manage complex account hierarchies or create new Account records.

B. Customer Community: Like its login-based counterpart, this license is for simpler B2C scenarios and lacks the role-based structure needed for customers to manage multiple accounts.

1. Salesforce Help: Experience Cloud User Licenses. This document outlines the capabilities of different license types.

Reference Details: Under the "Customer Community Plus" section

it states

"These users can access reports and dashboards and have roles and advanced sharing." This directly supports the need for managing complex hierarchies. In contrast

the "Customer Community" license description notes that these users do not have roles.

2. Salesforce Help: Who Can You Grant Super User Access To? This document clarifies that super user access

which allows external users to manage other users and view data for their account

is only available for the Customer Community Plus

Partner Community

and other higher-tier licenses

not the standard Customer Community license. This reinforces the "Plus" license's suitability for managing complex account structures.

Reference Details: The article explicitly lists the required licenses: "Available in: Enterprise

Performance

Unlimited

and Developer Editions with the Customer Community Plus or Partner Community license."

3. Salesforce Help: Experience Cloud Licenses. This overview table compares license features.

Reference Details: The comparison table clearly shows that "Roles and Advanced Sharing" is a feature of "Customer Community Plus" and "Partner Community" licenses

but not "Customer Community" licenses. This is the key differentiator for the scenario's requirements.

The "Build Your Own" template is the most suitable option as it provides the greatest flexibility for custom development. The scenario requires starting with a basic community (Home and Record Detail pages) and then scaling with significant regional customizations, including unique branding, themes, pages, and components. The "Build Your Own" template offers a minimal, unstyled framework, making it the ideal foundation for a highly tailored and evolving Experience Cloud site built with custom Lightning components, which directly addresses the NPO's long-term requirements for adaptability and regional differentiation.

A. Salesforce Tabs + Visualforce template: This is a legacy template. It is not based on the Lightning component framework and is less flexible for modern, responsive design and component-based customizations.

C. Non-Profit Success Pack template: This is not a standard, out-of-the-box Experience Cloud template. The Non-Profit Success Pack (NPSP) is a managed package that provides a data model, not a UI template for communities.

D. Help Center template: This template is purpose-built for knowledge bases and self-service support. It is too specific and would require significant effort to adapt to the broader, evolving needs of disaster relief management.

1. Salesforce Help Documentation

"Which Experience Cloud Template Should I Use?": This document outlines the use cases for various templates. It describes the "Build Your Own" template as providing "the basic pages that every Experience Cloud site needs... Add more pages and components for a customized experience. Use this template for a custom design that is heavily based on your brand." This directly supports the choice for a highly customized

branded solution.

2. Salesforce Help Documentation

"Build Your Own Template for Experience Cloud": This page specifies

"The Build Your Own template provides the essential pages for an Experience Cloud site... It’s a bare-bones template

perfect for developers who want to create a custom experience with their own components and branding." This confirms its suitability for the described scenario.

3. Salesforce Help Documentation

"Considerations for the Salesforce Tabs + Visualforce Template": This source notes that this template does not use Lightning components and that many features

such as themes and branding properties in Experience Builder

are not available

making it unsuitable for the stated requirements.

4. Salesforce Help Documentation

"Help Center Template": This document describes the template's focus: "The Help Center template lets users search for and view articles

and contact support if they can’t find what they’re looking for." This highlights its specific purpose

which is narrower than the NPO's needs.

The most effective and scalable method to control access to an Experience Cloud site (Community) is by managing its members through profiles and permission sets. In the Administration workspace, under the "Members" section, an administrator can specify which profiles are allowed to log in. By selecting only the "U.S. customer" profile, the administrator ensures that only users assigned to this profile can become members of the new U.S. community, effectively restricting access as required. This is the standard administrative control for defining a site's audience.

A. Add U.S. users to the Community sharing set.

A sharing set is used to grant community users access to records they don't own, not to control their ability to log in to the community itself.

C. Add the U.S. customer public group to the Community as members of the Community.

Public groups cannot be used to define community membership. Membership is managed exclusively through profiles and permission sets in the Administration workspace.

D. Add each U.S. customer as a Community member from their contact record.

This is a manual, one-by-one process for creating individual users. It is not a scalable method for defining or limiting membership rules for the entire community.

1. Salesforce Help

Add Members to Your Experience Cloud Site: "You control site membership by assigning profiles and permission sets to your members... From Setup

enter All Sites in the Quick Find box

then click All Sites. Next to your site

click Workspaces. Select Administration | Members. To add members using profiles

select the profiles you want to grant access to." This directly supports option B as the correct procedure.

2. Salesforce Help

Who Can See What in Experience Cloud Sites: This document outlines the layers of security. The first layer is profile-based access

which determines if a user can log in to the site at all. "Profiles and permission sets determine what members can do within a site... and which data they can access."

3. Salesforce Help

Set Up a Sharing Set: "Sharing sets grant site users access to records that are associated with their accounts or contacts based on their user profiles." This confirms that sharing sets are for record-level access for existing members

not for controlling membership itself

making option A incorrect.

There are several methods within Salesforce to require users to accept an agreement.

1. Login Flows (E): This is a primary feature designed to customize the user login experience. A flow can be triggered upon login to check if a user has accepted the terms. If not, it can present a screen with the agreement, which the user must accept to proceed into the community.

2. Audiences and Page Variations (B): This Experience Builder feature allows for displaying different page content based on user criteria. An administrator can create an "un-consented" audience and show them a page variation containing only the agreement. Upon acceptance, a user record field is updated, moving them out of that audience.

3. Custom User Registration (A): For communities that allow self-registration, the registration page can be customized to include a mandatory checkbox and a link to the user agreement, ensuring acceptance before an account is even created.

C. Build a site.com page...: Site.com is a legacy product. Modern communities are built with Experience Builder. This method is outdated and not a recommended practice for this requirement.

D. Redirect users to a custom page...: This describes the result of a Login Flow but is not the feature itself. Option E (Login Flows) is the more precise and correct answer as it names the specific Salesforce tool used to implement this logic.

1. Login Flows: Salesforce Help

"Login Flows". This document states

"You can use login flows to build a custom login experience...For example

collect and update user data

configure multi-factor authentication

or integrate third-party strong authentication methods...or display a message

such as a terms of service agreement."

2. Audiences and Page Variations: Salesforce Help

"Create and Manage Audiences in Experience Cloud". This documentation explains how to use criteria

including fields on the User object

to define audiences. "After you define an audience

you can create page variations in Experience Builder and assign the audience to them...to deliver a unique experience for each audience." This supports using a custom field to track agreement acceptance.

3. Custom User Registration: Salesforce Help

"Customize the Self-Registration Experience". This guide details how to modify the self-registration process. While it focuses on adding fields

the underlying principle of customizing the CommunitiesSelfReg controller or using a configurable self-reg page allows for adding logic for terms of service acceptance. For example

adding a required checkbox custom field to the registration form.

The Salesforce Tabs + Visualforce template is the most appropriate choice because it directly meets all the specified requirements. It provides a standard, tab-based interface that is ideal for desktop users and is not mobile-responsive by default, aligning with the explicit negative requirement. This structure allows for easy access to standard tabs like Reports and Dashboards. Furthermore, it supports displaying external objects either through standard tabs or custom Visualforce pages, which is necessary for viewing invoices. The branding is simple and can be easily limited to a logo, fitting the classic interface style.

B. Aloha Template: This template is designed as a single sign-on (SSO) portal or app launcher, not for displaying internal Salesforce data like reports, dashboards, or records within the community itself.

C. Kokua Template: This is a specialized, responsive template focused on providing a knowledge base and case deflection. It is not the primary choice for general access to reports and external object data.

D. Napili Template: Now known as the Customer Service template, this is a modern, feature-rich, and mobile-responsive template. The requirement that mobile responsiveness is not needed makes this template less suitable than the desktop-focused Salesforce Tabs + Visualforce.

1. Salesforce Help. (2024). Which Experience Cloud Template Should I Use?. Salesforce

Inc.

Reference for Correct Answer (A): The documentation describes the Salesforce Tabs + Visualforce template as a standard Salesforce structure that "isn't mobile-friendly out of the box." It supports standard functionality like tabs and allows for deep customization with Visualforce

making it ideal for the desktop-only requirement and for displaying external objects.

Reference for Incorrect Answer (B): The Aloha template is described as a tool for "giving users access to other Salesforce orgs or apps using single sign-on (SSO)."

Reference for Incorrect Answer (C): The Kokua template is detailed as a "configurable

self-service template that focuses on knowledge and case management."

Reference for Incorrect Answer (D): The Customer Service (formerly Napili) template is described as a "powerful

responsive

self-service template

" which contradicts the non-responsive requirement.

To enable self-registration, an administrator navigates to the site's Workspaces > Administration > Login & Registration page. This area was formerly known as Community Manager. While basic self-registration can be configured declaratively by selecting a profile and an account, many business scenarios require custom logic. This is achieved by modifying the default CommunitiesSelfRegController Apex class. A primary reason for this customization is to control how new users are associated with a specific business Account, which involves modifying the Apex logic to use a designated Account ID, rather than the default behavior of creating a new account for each user.

A: Incorrect. Self-registration is managed in the Administration workspace, not the Community Builder, which is used for site branding, theming, and component layout.

B: Incorrect. While the setting is in a community's settings, "Community Manager" (or Workspaces) is the more precise term for the specific administrative area, not the global settings.

C: Incorrect. The primary logic in the self-registration controller concerns User, Contact, and Account creation, not modifying it with the Community ID.

D: Incorrect. An administrator selects a profile for new users from a lookup field in the configuration UI; they do not "modify the profile lookup" itself.

1. Salesforce Help: Set Up Self-Registration for Your Experience Cloud Site. This document outlines the primary steps: "From Workspaces

select Administration

and then select Login & Registration. Under Registration

select Allow external users to self-register." It also mentions specifying an Account and Profile.

2. Salesforce Help: Customize the Self-Registration Process. This guide details the use of a custom Apex controller for advanced scenarios. It states

"Salesforce provides a default Apex controller... You can modify the controller to customize self-registration." The example logic focuses on creating and associating User

Contact

and Account records.

3. Apex Developer Guide: Auth.CommunitiesSelfRegHandler Class. This official documentation describes the Apex handler for self-registration. The createUser method signature is global virtual Id createUser(User u

String password

Auth.UserData data)

where the logic inside handles the creation of the user and its related Account/Contact

confirming the controller's role in this process. The customization often involves hardcoding or dynamically retrieving an Account ID.

To customize the Account record detail page to show only the record details, an administrator has two valid methods within the Experience Builder.

1. Directly Edit the Page (B): The most straightforward approach is to navigate to the default Account Detail page, remove all unnecessary components (like Tabs, Feed, or Related Lists), leaving only the Record Detail component, and then publish the changes.

2. Use a Page Variation (A): A more flexible and non-destructive method is to create a page variation for the Account Detail page. The admin can then build this new variation with only the Record Detail component, set it as the active variation for the intended audience, and publish. This preserves the original layout for potential future use or for other audiences.

Both options describe a complete and correct procedure to fulfill the requirement.

C. Make a copy of the Account detail object, remove the components NOT needed, and publish.

This is incorrect because you customize object pages in Experience Builder, not the underlying Salesforce object. The terminology is wrong and misrepresents the action.

D. Create a standard page, add the Account record detail component, and publish.

This is incorrect because a "standard page" is a generic content page. To display data for a specific record, a context-aware "object page" is required.

1. Salesforce Help

Experience Cloud

Customize Object Pages in Experience Cloud Sites: This document outlines the process of modifying object pages. It states

"From the Pages menu in Experience Builder

you can access your site’s object pages... You can customize the page layout and edit the properties of the components on the page." This supports the direct edit method (Option B).

2. Salesforce Help

Experience Cloud

Use Page Variations to Tailor Your Experience Cloud Site Pages: This source details the use of page variations. It explains

"Page variations let you create different versions of a page... For example

you can have one version of your home page for customers and another for partners." This supports using a page variation as a valid method (Option A).

3. Salesforce Help

Experience Cloud

Create Custom Pages with Experience Builder: This document differentiates page types

clarifying that object pages are used "to view and manage your Salesforce object data

" which is the requirement

making the use of a "standard page" (Option D) inappropriate for this task.

The Partner Super User feature is specifically designed to grant users in a partner account visibility into all data owned by other users who have the same role or a role below them in the account's role hierarchy. This directly fulfills the requirement for a "CEO type of access" by providing a comprehensive view of the dealership's data. The administrator first enables Super User access on the partner account record itself. Then, they grant the specific permission to the designated users, typically through a dedicated permission set, without needing to alter the fundamental sharing model or role structure.

1. Salesforce Help

Article: Configure Super User Access. This document outlines the exact procedure. It states

"Super user access applies to cases

leads

custom objects

and opportunities only... Super users can access data that is owned by other partner users who have the same role or a role below them in the role hierarchy." This directly maps to the scenario's requirement.

2. Salesforce Help

Article: Give Super User Access to Your Partners and Customers. This guide specifies the steps: "From the account record’s contact related list

find the contact record of the user you want to give super user access to... In the contact record’s detail page

click the action menu and select Enable Super User Access." This confirms the administrative action required.

3. Salesforce Help

Article: Who Sees What in Experience Cloud Sites. In the section "Sharing and Record Visibility in Portals and Communities

" the Super User capability is described as a specific mechanism to extend record access within the account-based role hierarchy

contrasting it with other sharing mechanisms. It clarifies that this is the standard solution for granting managers or executives broader access within their own company's account.

An ISV (Independent Software Vendor) partner develops applications for commercial distribution on the AppExchange. The most appropriate mechanism for this is a Managed Package. Managed Packages are designed for ISVs to sell and distribute applications, as they are fully upgradeable after installation, support versioning, and protect the developer's intellectual property (e.g., Apex code is hidden). A Lightning Bolt Solution, intended as a distributable product for a specific industry like healthcare, fits this model perfectly.

B. Metadata API: This is a tool for programmatic deployment of metadata between orgs, not a packaging and distribution method for a commercial ISV product.

C. Change Set: Change Sets are used to move customizations between related orgs within a single company (e.g., from sandbox to production) and are not for distribution to external customers.

D. Unmanaged Package: This package type is not upgradeable by the ISV and does not protect intellectual property, making it unsuitable for a commercial, supported solution.

1. Salesforce Help: Create and Distribute Lightning Bolt Solutions. This document explicitly states

"To distribute your solution to other orgs or to sell it on AppExchange

you package it. We recommend using a managed package to distribute a Lightning Bolt Solution."

2. Salesforce Help: Packages. This page details the different package types. For Managed Packages

it specifies

"A managed package is a collection of application components that is posted as a unit on AppExchange

and is associated with a namespace and a License Management Organization. To support upgrades

a package must be managed." This aligns with the ISV's need to maintain and upgrade their solution.

3. Trailhead: AppExchange App Development > Determine Your AppExchange Strategy. This module explains

"Managed packages are for ISVs who want to sell apps on AppExchange... They’re upgradeable

and they prevent customers from seeing your proprietary code." This directly supports the use of managed packages for an ISV's Lightning Bolt Solution.