Experience-Cloud-Consultant Salesforce Certified Experience Cloud Consultant (SP23) Questions and Answers

Three features that CK should use to organize content on its site are Content Topics, Content Graph, and Navigation Tree. Content Topics are keywords or phrases that help users find and organize content in Experience Cloud sites. Content Topics can be assigned to any content, such as articles, posts, or files. Content Graph is a feature that analyzes the relationships between content and topics and suggests relevant content to users based on their interests and preferences. Navigation Tree is a component that allows you to create a hierarchical structure of topics and subtopics that users can browse through to find content.

To allow UC’s customers to log in to CK’s site, an Experience Cloud consultant should recommend establishing SSO between the two Experience Cloud sites by using one org as an identity provider and the other org as a service provider. SSO is a feature that allows users to authenticate with one system and access multiple systems without entering their credentials again. To use SSO between two Experience Cloud sites, you need to use one org as an identity provider (IdP), which is the system that verifies the user’s identity and issues a security token. You also need to use the other org as a service provider (SP), which is the system that accepts the security token and grants access to its resources.

To remove all the spammers’ posts and comments from the Experience Cloud site, DR should utilize the Insights reports by creating and using a custom action to remove them. Insights reports are reports that show the activity and engagement metrics on DR’s site, such as page views, likes, comments, flags, and moderation actions. DR can use Insights reports to identify the spammers’ posts and comments based on the flagging reasons or other criteria. DR can also create a custom action that allows DR to remove multiple posts or comments at once from the Insights reports.

This license type allows the realtors to access Knowledge articles, reports and dashboards, and Leads in the digital experience. Partner Community users can also access standard and custom objects, such as accounts, contacts, cases, and opportunities. Partner Community users can also register deals and collaborate with UMS on sales opportunities.

Financial Services Community permission set license is a license type that allows users to access Financial Services Cloud objects and features, such as policies, claims, referrals, and goals. Insurance Agent Portal Lightning template is a template that is designed for insurance agents who need to manage their leads, opportunities, policies, claims, and referrals. These two features are available for DR to implement a solution involving insurance agent persona.

Two reasons for the import failure are A and D. To import Customer Portal users to the Experience Cloud, you need to have a portal role record and a contact record for each user. A portal role record is a record that defines the role of a portal user in the portal hierarchy. A contact record is a record that contains the personal information of a portal user, such as name, email, phone, etc. If these records are missing, the import will fail.

To share records with partners who will work on low-severity B2C customer issues, DR should use sharing rules. Sharing rules allow you to extend sharing access to users in public groups, roles, or territories. You can use sharing rules to share records owned by internal users with partners based on criteria such as record type, field value, or ownership.

Three best practices when configuring self-registration for an Experience Cloud site are A, B, and C. Self-registration is a feature that allows users to create their own accounts on your Experience Cloud site without an invitation. To configure self-registration, you need to assign a default profile for self-registered users, which determines their access level and permissions on your site. A best practice is to assign a cloned standard site profile as the default, which gives you more control over the settings and customization of the profile. Another best practice is to use a restrictive default profile to begin with, which limits the access and visibility of self-registered users until they are verified or approved by an administrator. A third best practice is to create a separate profile for your self-service site and your partner portal, which allows you to differentiate the access and functionality of different types of users on your sites.

To create a partner user from an enabled partner account, the correct sequence of steps is C. A partner user is a user who has access to your Experience Cloud site through a partner account. A partner account is an account that has the Is Partner checkbox enabled. To enable a partner user, you need to view the partner account contact, select Manage External User, select Enable Partner User, edit the user record to assign the correct role and profile, and save.

This license type allows the realtors to access Knowledge articles, reports and dashboards, and Leads in the digital experience. Partner Community users can also access standard and custom objects, such as accounts, contacts, cases, and opportunities. Partner Community users can also register deals and collaborate with UMS on sales opportunities.

To move a site from one production org to another production org that is not directly connected, UC should use Lightning Bolt Export and Installation. Lightning Bolt is a feature that allows UC to export a site as a package that contains the site template, theme, pages, components, and content. UC can then install the package in another org using the AppExchange or a URL link.

Customer Community Plus licenses have a limit of 2 million users per org, which could be a potential issue for UC if they have a large global customer base that exceeds this limit. The other options are not limitations of the Customer Service template or the Customer Community Plus license.

To update brand colors across all of its sites, UMS should use the Site Builder tool. Site Builder is a tool that allows you to edit the look and feel of your Experience Cloud sites using a drag-and-drop interface. You can change the theme, layout, components, and branding of your sites without coding. Site Builder also supports Lightning templates, which are responsive and modern templates for Experience Cloud sites.

Partner Central and Build Your Own are two templates that ZRS can consider to build the portal for its partners. Partner Central is a template that is designed for managing partner relationships, such as recruiting, onboarding, training, and co-selling. Build Your Own is a template that allows you to create a custom site using Lightning Web Components and other web standards.

Three items that are reportable by a site administrator through Google Analytics for Experience Cloud sites are B, C, and E. Google Analytics is a tool that allows you to measure and analyze the traffic and behavior of your Experience Cloud site visitors. Google Analytics can report on various items, such as:

• Search Activity: This item shows how users search for content on your site, such as the number of searches, the search terms used, the number of results returned, and the click-through rate.
• User Login History Option: This item shows how users log in to your site, such as the number of logins, the login methods used, the login duration, and the login frequency.
• Contact Support page Activity: This item shows how users interact with your contact support page, such as the number of visits, the bounce rate, the average time on page, and the conversion rate.

This option allows UMS to configure its search results to include cases, quotes, contracts, and Knowledge articles. The Global Search Results component is a new component that supports multiple objects and facets in the search results. UMS can add this component to the Search page and select the objects that they want to display in the property editor.

Audience targeting allows you to display different content to different audiences based on criteria such as profile, location, domain, or user. However, there are some limitations of audience targeting, such as:

• You can’t assign audiences to the components in the template header and footer sections. These sections are shared across all pages in your site and can’t be customized for different audiences.
• You can’t assign record-based criteria to a component or branding set. Record-based criteria are only available for page variations and navigation menu items.

One possible cause of this issue is that the sender’s email address was changed and not verified. The sender’s email address is the email address that appears as the sender of the welcome emails to the customer users. If the sender’s email address is changed, it needs to be verified by clicking on a link in a verification email. If the verification is not completed, the welcome emails will not be sent.

When building an HR help desk app using Experience Cloud, you need to consider some points, such as:

• HR user profile is not only available in Employee Cloud with Employee permission set license. HR user profile is a standard profile that can be used with any user license type that supports Experience Cloud access.
• In order to protect employee privacy, the HR help desk app does not need to be created in a different org than the main org. You can use sharing settings and permissions to control who can access what data in your org.
• In order to leverage organizational structure, the HR help app must be created in the main org. This will allow you to use role hierarchy and public groups to share data based on your org structure.
• HR user profile is not only available in Enterprise and Performance Editions with HR permission set license. HR user profile is available in any edition that supports Experience Cloud.

The Rich Content Editor component will be visible to all Platinum customers from California. This is because UMS has assigned the component solely to Platinum customers using Audience Targeting, which is a feature that allows UMS to display different content to different audiences based on criteria such as profile, location, domain, or user. UMS has also assigned the page variation for the Home page to customers from California using Page Variations, which is a feature that allows UMS to create different versions of a page and assign them to different audiences based on criteria such as record type, field value, or ownership.

To decrease its call volume using an Experience site, NTO can use standard out-of-the-box functionality such as:

• Create an FAQ Knowledge article. A Knowledge article is a document that provides information or a solution to a common issue or question. NTO can create an FAQ Knowledge article that answers the most frequently asked questions by its customers and publish it on its site.
• Deploy a chatbot to address common questions. A chatbot is an automated conversational agent that can interact with customers using natural language. NTO can deploy a chatbot on its site that can answer common questions, provide information, or escalate issues to agents.
• Enable Chatter Questions to encourage peer-to-self-service. Chatter Questions is a feature that allows customers to post questions on your site and get answers from other customers or experts. NTO can enable Chatter Questions on its site to encourage peer-to-self-service and reduce the need for support calls.

Service Your Way is a component that allows customers to choose how they want to interact with a service agent or a chatbot from a list of available channels, such as phone, chat, SMS, WhatsApp, or Facebook Messenger. Service Your Way can be added to any page in Experience Builder and configured to show different channels based on user attributes or device type.

Two considerations for creating partner users and granting access are B and C. Partner users are external users who access your Experience Cloud site through a partner account. A partner account is an account that has the Is Partner checkbox enabled. To create partner users and grant access, you need to assign them a license type and a profile. Two license types that are suitable for partner users are Partner Community and Customer Community Plus. These license types allow partner users to access standard CRM objects, such as accounts, contacts, leads, opportunities, and cases, as well as custom objects and tabs. They also allow partner users to use roles and sharing rules to share records with other users.

To share records with Customer Community users using Sharing Sets, you should create one Sharing Set and add the objects to share in the Sharing Set. A Sharing Set is a feature that allows you to share records with Customer Community users based on common account or contact fields. For example, you can share records with users who have the same account ID or contact ID as the record owner. To use Sharing Sets, you need to create one Sharing Set and add the objects that you want to share in the Sharing Set. You can then define the access level and criteria for each object.

Two ways that Salesforce PRM can help DF accelerate channel sales are B and C. Salesforce PRM is a solution that allows you to manage your partner relationships and empower them to sell your products and services. By using Salesforce PRM, DF can automate partner tiering in Channel sales hierarchy, which allows them to assign different tiers and benefits to their partners based on their performance and potential. DF can also automate partner lead routing, which allows them to distribute leads to their partners based on criteria such as location, product, or skill. These features can help DF increase partner engagement and loyalty, optimize lead conversion, and grow channel revenue.

Three actions that are performed automatically when a site is created in Experience Cloud are A, C, and E. A guest role is a role that defines the access level and permissions of guest users on your site. A guest profile is a profile that determines what guest users can see and do on your site. A guest user record is a user record that represents the guest user on your site. These actions are performed automatically when you create a site in Experience Cloud, so you don’t have to manually create them.

Salesforce Content Delivery Network (CDN) is a feature that allows you to improve the performance of your site by caching static resources, such as images, JavaScript, and CSS files. However, changing the Salesforce CDN has some implications, such as:

• Changing the Salesforce CDN impacts definitions of all Lightning Web Components used in public pages. You need to redeploy your components after changing the CDN to ensure that they work properly.
• Changing the Salesforce CDN does not affect SAML SSO settings for all custom URLs in that domain. SAML SSO settings are independent of the CDN settings.
• Changing the Salesforce CDN does not impact the AppExchange packages in the org that use Documents object. Documents object is not affected by the CDN settings.
• Changing the Salesforce CDN does not overwrite LDS defaults. LDS defaults are not affected by the CDN settings.

This option allows UC to customize the self-registration process and create person accounts programmatically using Apex code. The standard self-registration configuration does not support person accounts and requires an existing business account to associate the new users with. Restricting the account record type access for the Site Guest User does not affect the self-registration process and may cause errors.

When selecting a template for your sites and portals, you need to keep in mind some points, such as:

• Insurance Agent Portal template becomes available once Financial Services Cloud is correctly set up in an org. This template is designed for insurance agents who need to manage their leads, opportunities, policies, claims, and referrals.
• Industry-specific templates as well as Lightning Bolt solutions are available today. Templates are preconfigured site designs that include pages, components, and settings. Lightning Bolt solutions are industry-specific solutions that include templates, themes, flows, apps, and components.

Page variations allow you to create different versions of a page for different audiences. You can use the flexible page layout to customize the components and layout of each page variation. You can also target each page variation to a specific audience based on criteria such as location, profile, or record type.

Salesforce AppExchange is a marketplace where customers can find and install pre-built solutions for various industries and use cases. Lightning Bolt solutions are industry-specific templates that include themes, components, pages, and business logic. They are built by Salesforce partners and can be customized to fit specific needs3

To grant access to each customer, the UC admin should select a permission set and a profile for a given experience. A permission set is a collection of settings and permissions that give users access to various tools and functions in Experience Cloud. A profile is a collection of settings and permissions that determine what users can see and do in Experience Cloud. By selecting a permission set and a profile for each experience, the UC admin can control the access level of each customer user.

BC should look closely into Lightning Bolt solutions during the evaluation phase. Lightning Bolt solutions are industry-specific solutions that include prebuilt themes, templates, pages, components, and business logic for Experience Cloud sites. Lightning Bolt solutions can help BC create personalized experiences for its providers, vendors, installers, and patients by providing them with best practices and ready-made features for their industry. BC can find and install Lightning Bolt solutions from AppExchange or create their own custom solutions using Lightning Bolt framework.

The sharing setting that would allow users to collaborate with their peers who work for the same partner firm, but not with any users outside of their firm, is Portal User Visibility. Portal User Visibility is a setting that allows portal users (such as Customer Community or Partner Community users) to see other portal users who have the same role or a role below them in the portal role hierarchy. This setting enables portal users to share information and collaborate with their peers within their own firm, but not with other firms.

Two steps that the UC admin should take to grant access to each customer are B and C. To grant access to an Experience Cloud site, you need to assign a license type, a profile, and a permission set to each user. A license type determines what features and functionality a user can access on the site. A profile determines what objects and fields a user can see and edit on the site. A permission set determines what additional permissions and settings a user can have on the site. To assign a profile and a permission set for a given experience, you need to select them from the drop-down menus in the Admin Workspace of your Experience Builder tool.

The Experience Cloud consultant should recommend creating a digital experience for agents and an app for employees. A digital experience is a branded online destination that allows you to connect with your customers, partners, or employees. An app is a collection of items that work together to serve a particular function. By creating a digital experience for agents, DR can offer them a portal where they can manage claims, access resources, and collaborate with DR employees. By creating an app for employees, DR can provide them with a workspace where they can approve settlements and adjustments, view reports and dashboards, and communicate with agents.

To ensure that the partner users are able to register, the site administrator should enable the Contacts under the Account as partner users. This will allow the site administrator to assign a username, password, and profile to each Contact and send them a welcome email with a link to activate their account and log in to the site.

To set up a site and gather their customers’ communication preferences, CK should create a Lightning Bolt solution with a template and a login flow to gather the preferences. A Lightning Bolt solution is a package that contains an industry-specific template, theme, flows, apps, and components that can be used to create an Experience Cloud site. CK can create a Lightning Bolt solution that includes a template with the required pages and branding for its customers’ site. CK can also include a login flow in the Lightning Bolt solution, which is a flow that runs when a user logs in to the site. CK can use the login flow to collect the customers’ communication preferences and store them in Salesforce.

Permission sets are a feature that allows you to grant additional permissions to users without changing their profiles. You can use permission sets to control Knowledge article visibility by granting users access to specific article types and actions. For example, you can create a permission set that allows users to view only certain article types and assign it to your customer portal users.

Three fields that are required for creating Experience Cloud users using Data Loader are A, B, and E. Data Loader is a tool that allows you to import or export large amounts of data in or out of your Salesforce org. To create Experience Cloud users using Data Loader, you need to have some required fields in your CSV file, such as:

• Profile Id: This field specifies the profile that determines what users can see and do on your Experience Cloud site.
• First Name: This field specifies the first name of the user.
• Currency: This field specifies the currency that applies to the user’s data.

Other required fields include Last Name, Alias, Email, Username, Community Nickname, Contact Id (or Account Id), and IsActive.

The Content Delivery Network (CDN) is a feature that improves the performance of public sites by caching static content, such as images, CSS files, and JavaScript files, on servers that are closer to the site visitors. This reduces the load on the Salesforce servers and speeds up the page loading time. CK can enable and configure the CDN from Experience Builder settings.

To implement SAML 550 for the Experience Cloud site, the UC administrator should use the site login URL as an endpoint where SAML assertion is made. SAML 550 is a protocol that allows users to authenticate with a third-party identity provider and access Salesforce resources without entering their Salesforce credentials. The site login URL is the URL that users use to access the Experience Cloud site. By using the site login URL as an endpoint, the UC administrator can configure SAML settings to redirect users to the identity provider for authentication and then back to the Experience Cloud site.

To create Experience Cloud users, you need to add them to an account as contact records. Then, you can enable them as Experience Cloud users and assign them a user license and profile.

To enable the guest user to run the flow, UC should set the “Enable Lightning Flows for Guest User” toggle option to ON in Setup. A flow is a tool that allows you to automate business processes by guiding users through screens and performing actions based on their inputs. A guest user is a user who accesses your Experience Cloud site without logging in or registering. To allow guest users to run flows on your site, you need to enable the “Enable Lightning Flows for Guest User” option in Setup, which gives guest users access to run flows that are embedded in Lightning pages or Visualforce pages.

Three visibility options available in Experience Cloud are Audience, None, and Default. Visibility options allow you to control who can see a page or a component on your Experience Cloud site. Audience is an option that allows you to display a page or a component only to users who belong to a specific audience. An audience is a group of users who share common attributes, such as profile, location, or language. None is an option that allows you to hide a page or a component from all users. Default is an option that allows you to display a page or a component to all users who have access to the site.

To add a background image to a record list of products in its digital experience, an administrator should build a custom Lightning component. A Lightning component is a reusable unit of user interface that you can create and customize using code. A custom Lightning component allows you to add your own functionality and design to your Experience Cloud site. To add a background image to a record list of products, an administrator should build a custom Lightning component that uses the SLDS Background Image utility class and the lightning-record-list base component.

This user license allows partners to register deals and work with UC on sales opportunities. It also provides access to reports and dashboards, campaigns, orders, price books, and products. Partner Community Plus users can also access standard and custom objects, such as accounts, contacts, cases, and leads1

To make Knowledge articles available to site users, you need to map topics to data categories and enable the “Share on Sites” setting. Topics are labels that you can assign to articles to make them easier to find and organize. Data categories are a way of classifying articles based on a predefined hierarchy. You can map topics to data categories, so that when you assign a topic to an article, it automatically inherits the data category visibility settings. The “Share on Sites” setting allows you to share articles with public users on your site.

Three things that BC should keep in mind about unauthenticated or guest user access are A, B, and D. Unauthenticated or guest user access is a feature that allows users to access your Experience Cloud site without logging in or registering. Unauthenticated or guest users have limited access and visibility to data in your Salesforce org, and they have some restrictions, such as:

• Guest user external organization-wide defaults are always set to Private. This means that guest users cannot access any records that are owned by external users (such as Customer Community or Partner Community users) unless they are explicitly shared with them.
• Guest user can’t access records via manual sharing. This means that guest users cannot access any records that are shared with them by using the Sharing button on the record detail page.
• Guest user can’t be members of public groups or queues. This means that guest users cannot access any records that are shared with them by using public groups or queues as criteria.

Branding sets allow the administrator to define the colors, fonts, logos, and images for different parts of the site, such as the header, footer, and body. Page variations allow the administrator to create different versions of a page with different layouts, components, and content. Audience targeting allows the administrator to create audiences based on user attributes, such as profile or company name, and display different branding sets or page variations to different audiences within the same site.

To support the sharing requirement of using advanced sharing rules for the custom object, CK should grant two user license types to customers: Partner Community User and Customer Community Plus Login User. These license types allow customers to access custom objects and a subset of standard CRM objects, such as accounts, contacts, cases, and dashboards. These license types also support advanced sharing features, such as role hierarchy, sharing rules, manual sharing, and Apex sharing.

To set up a topic catalog, the step that is required is to enable Topic Hierarchy and create at least one topic with two subtopics. A topic catalog is a feature that allows you to display all the topics and subtopics on your Experience Cloud site in a hierarchical structure. Users can see the topic catalog by clicking the More Topics link on the navigation menu. To use the topic catalog, you need to enable Topic Hierarchy, which allows you to create topics and subtopics up to three levels deep. You also need to create at least one topic with two subtopics, which will populate the topic catalog with some content.