Certified Experience Cloud ConsultantDemo

Salesforce AppExchange is the marketplace for Lightning Bolt Solutions. These solutions can package custom Lightning apps, business-process flows, and Experience Builder assets, and Salesforce supports publishing and distributing them through AppExchange.

A Salesforce Content Delivery Network caches publicly cacheable resources and serves cached content from distributed CDN servers, often closer to users. This reduces load times and improves site performance.

A Record Detail component typically receives its Record ID automatically from the record context of the page that contains it. Consequently, multiple instances on a single object page resolve the record ID associated with that page template rather than independently loading Account, Case, and Opportunity records for the logged-in portal user. The component therefore cannot provide the three distinct object records required here.

External Account Hierarchies are available with Customer Community Plus licenses and support business accounts. They share data owned by external users associated with child accounts upward to users at parent accounts, which provides parent-level visibility into department-level opportunities. Person accounts cannot be included in such a hierarchy, but their use for a separate B2C business does not prevent using a hierarchy for B2B business accounts.

Portal User Visibility allows portal users in the same customer or partner portal account to see one another. A partner firm is represented by its partner account, so this setting enables collaboration within that firm without granting visibility to users associated with other partner accounts.

Preconfigured Insights reports in the Salesforce Communities Management package require the Experience Cloud site to use Chatter. A site without Chatter cannot use those reports.

A delegated external user administrator can create and edit external-user records, reset external-user passwords, and manage designated permission sets for external users on the administrator’s own account. Managing users across other accounts requires additional external-account authorization, and object access is not included in this delegated administration scope.

Portal Super User access lets eligible Experience Cloud partner users access records owned by other partner users at the same role level and by users beneath them in the account role hierarchy. This directly provides retail managers access to peer and subordinate records.

For large Salesforce organizations, partner roles should be moved to a separate branch of the role hierarchy, and partner users should receive access to the partner account through a sharing rule. This configuration improves performance during realignment operations when account ownership changes.

Customer Community Plus is appropriate for partner users who need case access, standard sharing, and reports or dashboards, but do not require access to sales objects. Salesforce states that Customer Community Plus can be used for partners when they do not need opportunities, leads, or campaigns.

Salesforce CMS search must be enabled on the relevant CMS channel. After that channel setting is enabled, an Experience Builder Global Search Box can be configured to search the Content object and return published CMS content in that channel.

Salesforce requires the org-level Digital Experiences setting Allow using standard external profiles for self-registration, user creation, and login to be enabled for standard external profiles to be used for Experience Cloud site access. The setting is disabled by default and is not configured individually on a profile or through a permission set.

Lightning Bolt Solutions package reusable community-related assets—such as Experience Builder templates and pages, custom Lightning apps, and flows—into a portable solution. Building the solution once and reusing it reduces implementation time, and the package can be distributed to other orgs or sites.

Salesforce Partner Central lead distribution uses lead page layouts to control the fields and behavior shown to partner users, and lead assignment rules to apply criteria that route leads to a lead inbox queue or directly to partner users.

When an Experience Cloud navigation menu links to objects, custom list views for custom objects are included as package dependencies. Custom list views for standard objects are not included as dependencies, and the deployed navigation item uses the default list view.

Provisioning and activating the Salesforce CDN should occur when site traffic is low to minimize user disruption. Provisioning can make the site inaccessible, and activation can temporarily cause connection or DNS errors.

Experience Cloud uses topics to make Knowledge articles discoverable in a site. Mapping topics to data categories and enabling automatic topic assignment causes articles published in those data categories—including articles added later—to receive the mapped topics automatically.

Partner Community users can receive Opportunity access through a criteria-based sharing rule targeted to a Partner Community role. A sharing set can also grant access to Opportunity records for a Partner Community profile. Customer Community users do not support standard sharing rules, and Customer Community Plus users cannot be granted shared access to Opportunities.

ExperienceBundle stores Experience Builder site metadata in editable, human-readable files and supports programmatic editing of sites built with Experience Builder. It does not apply to every site type or create sites across organizations.

Salesforce Experience Cloud images are asset files, and the Administration workspace preference Let guest users view asset files and CMS content available to the site grants guest users access to those assets on publicly accessible pages.

After a Salesforce CDN domain configuration change is activated, SAML Single Sign-On Settings must be reconfirmed for every HTTPS custom URL in that domain. This makes SAML SSO settings for the domain’s custom URLs a potential area of impact.

Experience Cloud SEO is available for public sites, and the site must be activated to implement SEO successfully. A custom robots.txt file provides rules to control search-engine crawling and indexing for specific site areas. Sitemap refreshes occur automatically on a weekly and partial daily schedule; a month-end manual refresh is not required.

Question-to-Case lets a moderator create a case by selecting the Escalate to Case action in the question feed. It also supports criteria-based automatic escalation; current Salesforce documentation implements this automation with a flow on the Feed Item object, corresponding to the Process Builder-based automation described in older product terminology. Case Assignment Rules are not supported for Question-to-Case, and a comment alone does not create a case.

In Salesforce Experience Cloud, navigational topics structure content for browsing, featured topics highlight important or popular content, and content topics organize original content by common themes. Content assigned to any of these topic types is included in site search results.