Salesforce Experience-Cloud-Consultant Salesforce Certified Experience Cloud Consultant (SP23) Exam Practice Test

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.

To create a site that gives customers access to Knowledge articles and peer-to-peer conversations, AW Computing should use the Customer Service template. The Customer Service template is a pre-built site that includes features such as Knowledge, Chatter, Cases, and Topics. AW Computing can use this template to provide self-service options to its customers, such as browsing or searching for articles, posting or answering questions, creating or viewing cases, and following or filtering topics. This can help AW Computing reduce the number of calls to its support organization.

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.

This step allows the system administrator to create a partner user from an existing contact that is associated with a partner account. The partner user inherits the role, profile, and permission sets from the contact. The system administrator can also specify a username, email address, and nickname for the partner user.

Criteria-Based Audiences are a feature that allows you to display different content to different audiences based on criteria such as profile, location, domain, or user. However, there are some considerations when using Criteria-Based Audiences, such as:

• Components in the template header and footer sections cannot be assigned to an audience. These sections are shared across all pages in your site and can’t be customized for different audiences.
• Salesforce must be contacted if you need to use the domain criteria in sandbox or Developer Edition orgs. Domain criteria allow you to target audiences based on the domain name they use to access your site. However, this feature is not enabled by default in sandbox or Developer Edition orgs.
• Record Type criteria cannot be assigned to a component. Record Type criteria are only available for page variations and navigation menu items.

The reason for this issue is that the Record Detail component populates the recordID associated with the object for the page template, so this component will not work for this use case. The Record Detail component is a component that displays the fields and values of a record on your Experience Cloud site. The recordID is a unique identifier that specifies which record to display. The Record Detail component uses the recordID associated with the object for the page template, which means that it can only display one record per object per page. For example, if you have a page template for Account, you can only display one Account record on that page using the Record Detail component. To display multiple records of different objects on a page, you need to use other components, such as Related List or Record List.

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.

The step that denotes the completion of an Experience Cloud site setup is activating the site. Activating the site is the final step that makes your Experience Cloud site live and accessible to your users and visitors. Before activating the site, you need to complete other steps such as creating pages, adding components, configuring settings, assigning permissions, and testing functionality. After activating the site, you can still make changes and updates as needed.

External Apps is a user license type that allows users to access up to 10 custom objects per app and unlimited standard CRM objects. This license type is suitable for the researchers who need to access at least 20 custom objects for the coffee company’s solution.

To implement the new style guide and unify branding across all of its Experience sites, UC should create a custom theme and apply it to all sites. A theme is a collection of branding assets and style settings that define the look and feel of your site. You can create a custom theme that matches your style guide and apply it to multiple sites using the Theme Management feature in Experience Builder.

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.

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.

Reputation is a feature that allows you to reward community members for their contributions and engagement. When you enable reputation for your community, some things happen automatically, such as:

• Inactive and active members are assigned default reputation points. Inactive members get zero points, while active members get 10 points.
• Default point system and set of reputation levels become available. You can use the default point system or customize it to suit your needs. You can also use the default reputation levels or create your own.

Salesforce Partner Relationship Management (PRM) is a solution that helps you manage your partner lifecycle, from recruitment to enablement to co-selling. Some of the ways that Salesforce PRM can help DF are:

• Automating partner onboarding process. You can use Salesforce PRM to create guided onboarding flows that automate tasks, approvals, and notifications for your partners.
• Providing reports and dashboards access to partners. You can use Salesforce PRM to share reports and dashboards with your partners that show their performance, pipeline, and revenue.
• Preventing channel conflict. You can use Salesforce PRM to assign leads and opportunities to your partners based on rules and criteria that ensure fair distribution and avoid duplication.

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.

To help UC with user management, UC should delegate external user administration to its partners. This will allow UC to grant permission to its partners to create new users or reset passwords for partner employees without involving UC’s administrators. UC can use Delegated External User Administration, which is a feature that allows UC to assign specific users as delegated administrators who can manage external users in their own accounts.

UC should create two separate digital experiences for its different customer segments and employees. This will allow UC to provide different features, content, and branding for each experience, as well as control the access and visibility of records. For example, UC can create a customer service site for B2C customers and employees, where they can view and create cases, access knowledge articles, and chat with agents. UC can also create a partner portal for B2B customers and employees, where they can view and update billing information, access contracts, and work on low-severity B2C customer issues.

To make an external user an Experience Site Moderator, two of the several moderation permissions available to assign are Access Experience Management and Manage Experiences. Access Experience Management allows an external user to access Experience Workspaces and Builder from an Experience Cloud site. Manage Experiences allows an external user to create, edit, and delete experiences, as well as manage settings and content for existing experiences.

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.

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.

The cause of the error is that accounts used in an External Account Hierarchy cannot be merged with another account. An External Account Hierarchy is a feature that allows you to create a hierarchy of partner accounts and contacts that mirrors the structure of your partner’s organization. This helps you manage data access and visibility for your partners. However, accounts that are part of an External Account Hierarchy cannot be merged with other accounts, because this would disrupt the hierarchy and the sharing settings.

Three permissions that are included for a delegated administrator are A, D, and E. A delegated administrator is a user who has limited administrative privileges to perform certain user management tasks on behalf of an administrator. A delegated administrator can create and edit external user records, generate new passwords for external users, and manage permission sets for external users on their account. A delegated administrator cannot manage object access or add external users to multiple accounts.

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 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.

To implement the new style guide and unify branding across all of its Experience sites, UC should create a custom theme and apply it to all sites. A theme is a collection of branding assets and style settings that define the look and feel of your site. You can create a custom theme that matches your style guide and apply it to multiple sites using the Theme Management feature in Experience Builder.

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.

To create a do-it-yourself site for its existing and prospective customers, UC should focus on two Experience Cloud features:

• Guest user and public access settings. These settings allow you to control what unauthenticated users can see and do on your site, such as viewing articles, manuals, and FAQs, or asking and answering questions.
• Content Delivery Network. This is a feature that allows you to improve the performance of your site by caching static resources, such as images, JavaScript, and CSS files. This can enhance the user experience and reduce the load on your server.

Salesforce Partner Relationship Management (PRM) is a solution that helps you manage your partner lifecycle, from recruitment to enablement to co-selling. Salesforce PRM comes with some standard features that you can leverage without any code customization, such as:

• Case Escalation: You can enable your partners to escalate cases to you when they need your help or expertise.
• AI-Powered Knowledge Base: You can provide your partners with relevant and personalized knowledge articles powered by Einstein Article Recommendations.
• Chat: You can enable your partners to chat with you or other partners in real time using Embedded Service Chat or Salesforce Chat Snap-ins.

External users can be assigned as approvers on records or added directly to approval queues, as long as they have the appropriate user license and profile permissions. You also need to create a digital experience for those users, so they can access the approval process from the Experience Cloud site.

Two statements regarding data categories that are true are A and B. Data category visibility is controlled by roles, permission sets, or profiles. Child roles cannot see more data categories than their parent role, and if the parent role’s visibility changes, the child role’s category visibility is reset to match the parent’s. Customer Portal users and partner portal users inherit data category visibility settings of the role assigned to their account (owner) managers by default, unless they have a custom profile that overrides the role settings.

To create a new partner user for an existing site, you need to first create a contact record for the partner user, then click “Manage External User” on the contact detail page, and then click “Enable Partner User”. This will allow you to provide user details and save the user record.

To prevent usability issues, CK should provision and activate CDN in those regions where traffic is high. A CDN is a network of servers that delivers cached static content from websites to users based on the geographic location of the user. By provisioning and activating CDN in high-traffic regions, CK can improve the performance and availability of their public site for their users.

Two options that make it possible to have a vertical navigation menu in the customer portal are B and D. A navigation menu is a component that allows users to navigate through different pages and sections of your Experience Cloud site. By default, the navigation menu is horizontal, but you can change it to vertical by using different options. One option is to download an app from AppExchange, which is a marketplace where you can find and install apps, components, and solutions for your Experience Cloud site. Another option is to write custom code, which allows you to create your own custom components and layouts for your Experience Cloud site.

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.

To make a Knowledge article visible to both authenticated customers and unauthenticated guest users on the public knowledge base, you need to select the Visible to Public Knowledge Base checkbox when creating the article. This will allow you to share the article with public users on your site. You can also select other visibility options, such as Visible to Customer or Visible to Partner, if you want to share the article with other channels.

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.

Three topic types that can be used in an Aura site are:

• Standard Topic. This is a topic that is created by users or administrators and assigned to content, such as posts, files, or articles. Users can follow or unfollow standard topics and see the related content on the topic detail page.
• Featured Topic. This is a topic that is selected by administrators to highlight important or popular content on the site. Featured topics appear on the home page or on the topic catalog page of the site.
• Navigational Topic. This is a topic that is used to organize content into categories or subcategories on the site. Navigational topics appear on the navigation menu of the site and allow users to browse content by topic.

CMS Connect allows you to display content from an external content management system (CMS) in your Experience Cloud site. You can use CMS Connect to render a header and footer from your CMS in your site, as well as other content types such as articles, banners, or images.

To grant access to each customer to only one site, UC should create a permission set and select a permission set for a given site. A permission set is a collection of settings and permissions that give users access to various tools and functions. UC can create a permission set for each site that specifies the site access and the object permissions for the customer users. UC can then select a permission set for a given site in the Experience Builder, which will assign the permission set to all new and existing users of that site.

Experience Cloud can be used for employee apps, such as an onboarding app for new hires. However, there are some considerations when creating an employee app, such as:

• Not all Chatter posts inside Chatter groups within the employee app will be available in the main org. Only posts in public groups or groups that are shared with the main org will be visible in both places.
• Chatter posts related to a record will be available in the employee app as well as the main org. However, users need to have access to the record in both places to see the posts.

This option allows UC to control the access to the partner application form and ensure that only qualified partners can apply. Token-based referral links are unique and expire after a certain time, which adds an extra layer of security. Creating an app for the internal team also allows UC to track the performance of the referral program and reward the existing partners accordingly1

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 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.

When setting up partner roles, you need to keep in mind some considerations, such as:

• The default limit for the number of roles for portals is 50,000 per org. You can request an increase from Salesforce if you need more roles.
• Once created, roles cannot be deleted. You can only deactivate them or rename them.

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.

This option allows UC to control the access to the partner application form and ensure that only qualified partners can apply. Token-based referral links are unique and expire after a certain time, which adds an extra layer of security. Creating an app for the internal team also allows UC to track the performance of the referral program and reward the existing partners accordingly1

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.

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.

To allow site users to tag site content with custom tags or member-created topics, you need to enable two permissions for site users in Setup:

• Create Topics. This permission allows users to create new topics and assign them to content, such as posts, files, or articles. Users can also edit or delete the topics they created.
• Member Can Access Topics. This permission allows users to access the topic management features on the site, such as viewing, following, or unfollowing topics. Users can also see the topics assigned to content and filter content by topics.

To meet the requirement of distributing leads to partners, UMS needs to take at least three steps:

• Create a Lead Process for Lead Distribution. A lead process is a set of stages that a lead goes through from creation to conversion. UMS can create a lead process that defines how leads are distributed to partners based on criteria such as region, industry, or product.
• Create a Lead Queue for Lead Distribution. A lead queue is a list of leads that are assigned to a group of users who share the workload. UMS can create a lead queue for its partners and assign leads to the queue based on the lead process.
• Configure Lead creation Leadon low Distribution inside PRM Workspace. PRM Workspace is a feature that allows UMS to manage its partner relationships, such as recruiting, onboarding, training, and co-selling. UMS can configure lead creation and distribution settings inside PRM Workspace, such as enabling partners to create their own leads, setting up lead assignment rules, and defining lead notification preferences.

To ensure the changes make it accurately to production, the administrator should create a change set, upload it to production, and deploy the change set. A change set is a collection of metadata components that can be moved from one org to another. The administrator can use change sets to migrate point-and-click changes, such as custom objects, fields, layouts, and settings, from the sandbox to the production org. The administrator can create a change set in the sandbox, add the components that have been changed, upload it to the production org, and deploy it in the production org.

This user license allows users to access cases, Knowledge articles, reports and dashboards, and custom objects in a self-service site. It also provides access to Chatter groups and files, and allows users to edit their own profiles. Customer Community Plus users can also use email-to-case functionality and create records that have lookups to accounts or contacts5

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.

This option allows UC to grant customers access to the appropriate site. Site membership is a feature that defines which users can access a site and what permissions they have. UC can assign the profile for all customer users to the site membership of each site and specify the default page access and object permissions for that profile. UC can also assign permission sets to the site membership to grant additional permissions to specific users4

The Embedded Service component allows you to embed a chat window in your Experience Cloud site, so customers can chat with agents while browsing the site. You can add the Embedded Service component to any Builder page and configure its properties, such as the chat button label, pre-chat fields, and offline support.