Experience-Cloud-Consultant Salesforce CertifiedExperience Cloud Consultant (SU24) Questions and Answers

Explanation: 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 away 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.

This option allows CK to use Google as an external identity provider and enable customers to log in to the site using their Google credentials. CK can also access customers’ basic profile data, such as name, email, and picture, by specifying the scopes and attributes in the authentication provider settings. CK can also use the authentication provider to configure single sign-on (SSO) and just-in-time (JIT) provisioning for the site.

For records created by guest users, NMH should keep in mind that queues cannot be assigned as owners, setting the default owner is an option in Experience Cloud sites, and any active user in an org can be assigned as the default owner. A queue is a location where records can be routed to await processing by a group of users. However, queues cannot be assigned as owners of records created by guest users because guest users do not have access to queues. Setting the default owner for records created by guests is an option in Experience Cloud sites that allows NMH to specify who will own the records created by guest users on their public site. Any active user in an org can be assigned as the default owner of records created by guest users, as long as they have the appropriate permissions and access to the object.

The Customer Account Portal template is designed for creating a site for existing customers who need to access their account information, such ascontracts, billing, and support. The template includes features such as login, registration, profile management, case management, and commerce integration. The template also supports Knowledge articles, manuals, and FAQs.

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

To use standard profiles in an experience, the step that is required is to enable the “Allow using standard external profiles forself-registration, user creation, and login” option in Setup. A profile is a collection of settings and permissions that determine what users can see and do in Experience Cloud. Standard profiles are predefined profiles that come with Salesforce and cannotbe edited or deleted. To use standard profiles for external users in an experience, you need to enable the “Allow using standard external profiles for self-registration, user creation, and login” option in Setup, which gives you access to use standard profiles such as Customer Community User or Partner Community User.

To simplify topics but keep articles that have been assigned to the topics, you need to merge similar topics in Content Management. This will allow you to combine two or more topics into one and update the articles that have been assigned to the merged topics.

This permission allows the manager to create, edit, and delete all users in the org, including internal users. This permission overrides the sharing settings and role hierarchy that normally restrictaccess to user records. To limit the manager’s access to only community users, the manager should be given the Manage External Userspermission instead2

Thisuser 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

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

Three KPIs that could be used to measure the chatbot’s impact on customer service are B, C, and D. CSAT is a metric that measures how satisfied customers are with their chatbot experience on a scale of 1 to 5 stars. Case deflection is a metric that measures how many cases are avoided or resolved by the chatbot without escalating to an agent. Average Handle Time is a metric that measures how long it takes an agent to handle a case from start to finish. Bot Session Time is a metric that measures how long it takes a chatbot to handle a conversation from start to finish. By comparing these metrics, you can evaluate the chatbot’s performance and efficiency in providing customer service.

Partner Super User access is a feature that allows you to grant access to records owned by other partner users who havethe same role or a role below them in the role hierarchy. You can apply Partner Super User access to three objects: Opportunities, Accounts, and Custom Objects.

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.

Explanation: One thing that NTO should consider when building the HR help desk app is that the app can centralize knowledge and self service in to one experience site. This means that NTO can use Experience Cloud to create a site that provides access to Knowledge articles, Cases, Chatter, and other features that can help its employees find answers, request assistance, and collaborate with HR staff. NTO can use Employee Cloud, which is a solution that allows NTO to create employee experience sites using Experience Cloud.

To distribute leads to its partners in the portal, UMS can leverage the Lead Inbox component if it elects to use Partner Central template. The Lead Inbox component is a standard component that displays a list of leads assigned to the partner user or their partner account. The partner user can view, accept, or reject the leads from the Lead Inbox component.

The Rich Content Editor component will be visible to all Platinum customers from California. This isbecause 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 alsoassigned 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, fieldvalue, or ownership.

To prevent authenticated external users from searching for Quote and Contract objects but not Opportunity or Asset objects, you need to remove Opportunity and Asset from the object list in the Global Search Result component property editor and the Autocomplete object list in the Search component property editor. The Global Search Result component displays the search results for all objects that match the search term. The Autocomplete object list displays the suggested objects that match the search term as you type. You can customize these components by selecting or deselecting the objects that you want to include or exclude from the search.

Site User Visibility allows users within the same site to see each other, regardless of their role or sharing group membership. This is useful forcollaboration between independent researchers and NTO staff on their research-related submissions.

This license type allows third-party staff to access cases, leads, opportunities, contracts, and custom objects on behalf of UMS customers. Partner Community users can also create cases from questions, escalate questions to cases, and view Knowledge articles. Partner Community users cannot access quotes or reports and dashboards.

Data Category Visibility allows you to control which Knowledge articles are visible to which users based on data categories anduser roles, permission sets, or profiles. You can assign data category visibility at different levels, such as the org-wide default, the role hierarchy, or the permission set.

To limit the fields available in the customer portal, the administrator should use Field-Level Security to remove access to the unwanted fields. Field-Level Security is a feature that allows the administrator to control the visibility and editability of fields for different profiles and permission sets. The administrator can use Field-Level Security to hide or make read-only the technical codes and internalinformation fields for the customer portal profile or permission set.

Partner Central is a template that is designed for creating asite that supports channel sales, lead distribution, and deal registration. The template includes features such as partner recruitment, onboarding, training, co-selling, lead management, opportunity management, and deal registration.

To ensure that customers do not receive a welcome email when the site is once again active, the administrator should disable the Send welcome email checkbox for the site. This will prevent the site from sending an email to existing members when the site is activated. The administrator can disable the Send welcome email checkbox in the Administration section of Experience Builder.

This setting allows the CMS content to be searchable within the channel where it is published. To enable search for a channel, open the CMS Channels tab in Salesforce CMS, select Edit beside a channel, and click theSearch toggle. Additionally, if the site is created with Experience Builder, the Global Search Box component must be configured to include the Content object4

A sharing set is a feature that grants community users access to records that have a lookup relationship with their user record or their account or contact record. For example, a sharing set can grant customers access to cases that have the same contact as their user record, regardless of the case owner or role hierarchy. Sharing sets are easy to configure and do not require code.

This option allows NTO to manage its B2B accounts with multiple levels of hierarchy and grant record access based on the account relationship. External Account Hierarchy is a feature that enables this functionality for Customer Community Plus users. With this feature, users can view and edit records associated with their own account andany child accounts in the hierarchy3

This license type allows users to access accounts, contacts, leads, opportunities, orders, price books, products, and custom objects in a partner community. Channel Account users can also register deals and collaborate with UMS on sales opportunities. Channel Account users cannot access reports and dashboards, cases, or Knowledge articles.

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

This setting allows guest users to view images and other content that are stored as asset files or CMS content in your Experience Cloud site. You need to enable this setting if you want guest users to see images on your customer portal.

To enable the installers to collaborate with their co-workers and UMS staff, UMS needs to enable Portal User Visibility. This is a user visibility setting that allows portal users to see other portal users who have thesame role or a role below them in the role hierarchy. This also allows portal users tosee internal users who are above them in the role hierarchy. Portal User Visibility can be enabled in the Sharing Settings page in Setup.

Build Your Own (LWR) is a template that allows you to create a high-performance site using Lightning Web Components and other web standards. This template is suitable for Insightopia to create a site for itspartners that features multiple custom components that provide insights and trends along with near real-time updates.

An External Account Hierarchy is a feature that allows you to create a hierarchy of accounts for your partners and grant access to records based on the hierarchy level. You can use an External Account Hierarchy to grant View access to cases created by child companies to their parent company.

This option allows UMS to approve the first post of any new member who has joined within 7 days or less. UMS can create a moderation rule that applies to posts and comments, and specify the member criteria as “Joined Date is within last 7 days”. UMS can alsochoose the action as “Require Approval” and assign a moderator group to review and approve the posts.

This option allows UMS to reduce the call volume by providing customers with self-service options, such as knowledge articles, FAQs, case management, chat, and feedback. TheCustomer Service template is designed for this purpose and offers a responsive and customizablelayout2

To configure the chat functionality, the administrator should use the Chat Agent Guided Setup Flow and Service Console. Chat is a feature that allows customers to chat live with support agents from an Experience Cloud site. The Chat Agent Guided Setup Flow is a tool that walks you through the steps of setting up chat, such as creating chat buttons, chat deployments, chat queues, and chat skills. The Service Console is a workspace that allows agents to manage multiple chat sessions, view customer information, and access other tools and resources.

Financial Services Community permission set license is a license type that allows users to accessFinancial 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 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.

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

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 criteriafor each object.

Three key features of Metadata API are A, B, and C. Metadata API is an API that allows you toretrieve, deploy, create, update, or delete customization information in your Salesforce org, such as custom objects, fields, tabs, or pages. Metadata API is ideal when multiple work streams are involved, because it allows you to manage changes across different environments and teams. Metadata API can be used programmatically as well as declaratively, because it supports both code-based tools and point-and-click tools for working with metadata. Metadata API is ideal for when the changes are complex, becauseit allows you to handle fine-grained customizations and dependencies.

Explanation: The administrator should create a digital experience for agents and share the URL with employees. A digital experience is a branded online destination that allows you to connect with your customers, partners, or employees. By creating a digital experience for agents, the administrator can provide them with a portal where they can view Knowledge articles and chat live with a support agent. By sharing the URL with employees, the administrator can allow them to access the digital experience as well.

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

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

Sharingsets allow you to grant access to records that have a lookup relationship to the same account or contact that the community user has. You can use sharing sets to share opportunities with partner community users who belong to the same account as the opportunity owner.

Criteria-based sharing rules allow you to share records based on field values. You can use criteria-based sharing rules to share opportunities with partner community users who meet certain criteria, such as region, industry, or status.

To enable autocomplete for guest users, the administrator should use theSearch component property editor, open the Autocomplete section, and click desired objects to appear in autocomplete. Select “publicly available”. Autocomplete is a feature that suggests search terms based on what users type in the search box. The Search component property editor is a tool that allows you to customize the settings and behavior of the Search component on your Experience Cloud site. By selecting “publicly available”, you can make autocomplete suggestions visible to guest users who are not logged in.

The reason for this issue is that the preconfigured Insights reports need to be modified to meet GDPR requirements. Insights is a feature that allowsyou to measure and analyze the adoption and engagement of your Experience Cloud sites using preconfigured reports and dashboards. However, some of these reports may not comply with GDPR, which is a regulation that protects the privacy and data rights of individuals in the European Union. To use Insights for the Experience Cloud site for Europe, the Community manager needs to modify the preconfigured reports to meet GDPR requirements, such as anonymizing user data, obtaining user consent, and deleting user data upon request.

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.

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 asaccounts, contacts, cases, and opportunities. Partner Community users can also register deals and collaborate with UMS on sales opportunities.

Two ways the consultant should associate the articles with topics are A and D. Topics are keywords or phrases that help users find and organize content in Experience Cloud sites. To associate articles with topics, you can select the appropriate topics on the Knowledge tab within Lightning Experience, which allows you to view and edit articles in a list or Kanban view. You can also manually add one or more topics to each article within Workspaces, which allows you to create and manage articles in a collaborative environment.

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.

Partner lead routing allows UMS to assign leads to partners based on predefined criteria, such as location, product, or industry. This helps UMS distribute leads more efficiently andincrease partner engagement. Automated quoting capabilities allow partners to generate quotes for customers using UMS’s pricing and discount rules. This helps partners close deals faster and more accurately.

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.