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

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.

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.

Three key features of Metadata API are A, B, and C. Metadata API is an API that allows you to retrieve, 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, because it allows you to handle fine-grained customizations and dependencies.

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.

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

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.

Experience Tracker is a component that informs support agents working in the Service Console what actions a customer has taken on an Experience site. Experience Tracker shows information such as page views, searches, downloads, and case interactions that the customer has performed on the site. This helps agents understand the customer’s context and provide better service.

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

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 realtors at DR with social workers at NMH, based on criteria such as record type, field value, or ownership.

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

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.

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.

To capture the new users self-registering on the B2C site as person accounts in Salesforce, UC should create a custom self-registration page and Apex handler that creates a person account for each user. A custom self-registration page allows UC to customize the look and feel, fields, and logic of the self-registration process. An Apex handler is a class that implements the Auth.RegistrationHandler interface and defines the logic for creating a user and an account. UC can use an Apex handler to create a person account for each user based on the information they provide on the self-registration page.

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.

To enable autocomplete for guest users, the administrator should use the Search 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.

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.

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.

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.

The page view limit for an Experience site depends on the org edition and the license type of the site users. For an Unlimited org, the page view limit is 5 million per month for guest users, and unlimited for authenticated users. A page view is counted when a user requests a page that is served by the site.

To set up Lead Sharing or Lead Distribution for partners, two steps are to enable “Allow External Lead Sharing” in Digital Experience settings and create Assignment Rules for Lead Distribution. Enabling “Allow External Lead Sharing” allows partners to access leads that are shared with them through sharing rules or manual sharing. Creating Assignment Rules for Lead Distribution allows leads to be automatically assigned to queues or users based on criteria that you define.

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

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 the same role or a role below them in the role hierarchy. This also allows portal users to see internal users who are above them in the role hierarchy. Portal User Visibility can be enabled in the Sharing Settings page in Setup.

To grant Experience Builder access to two colleagues who will be responsible for creating and managing new microsites, the system administrator should grant Publisher and Builder roles. Publisher and Builder are two Experience Builder roles that define what users can do on the site. Publisher is a role that allows users to add contributors, publish changes, and activate or deactivate sites. Builder is a role that allows users to create and customize sites, but not publish them.

Customer Community Plus licenses allow users to access standard CRM objects, such as cases and accounts, and custom objects. They also allow users to collaborate with other users through Chatter groups, files, and topics. Customer Community Plus licenses are suitable for partner users who need to create or resolve cases for their customers and see case data on a dashboard, but do not manage leads, opportunities, or campaigns.

Data Category Visibility allows you to control which Knowledge articles are visible to which users based on data categories and user 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 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 dynamically populate the site with blog posts as new ones are added, CK should use a Grid component with CMS Collections. A Grid component is a component that displays content in a grid layout with rows and columns. A CMS Collection is a collection of content items that are created and managed in Salesforce CMS. CK can use a Grid component and select a CMS Collection as the content source. This will allow CK to showcase blog posts written by AW Computing thought leaders on its site and automatically update them as new ones are added.

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 its partners that features multiple custom components that provide insights and trends along with near real-time updates.

The members that will be able to see the Rich Content Editor component are those that are part of both the New York City audience and the Legal Department audience. Audience targeting is a feature that allows you to display pages and components to certain users based on their assigned audience. An audience is a group of users who share common attributes, such as profile, location, or language. When you assign an audience to a page or a component, only the users who belong to that audience can see it. If you assign multiple audiences to a page or a component, only the users who belong to all of those audiences can see it.

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.

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.

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

Audience targeting allows UMS to create audiences based on user attributes, such as profile, location, or language, and display different content or components to different audiences within the same site. For example, UMS can create an audience for premium customers and show them a special offer on the navigation menu, while hiding it from other customers. Audience targeting can be applied to any component or page in Experience Builder.

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 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 option allows UC to give retail store managers access to the records owned by their peers and subordinates. Super User access is a feature that grants community users access to records that are owned by users who have the same role or a role below them in the role hierarchy. Super User access can be enabled for partner users or customer users with Customer Community Plus or Partner Community licenses2

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.

Platform Portal is a user license type that allows users to access custom objects and a subset of standard CRM objects, such as accounts, contacts, cases, and dashboards. This license type is suitable for UMS’s premium B2B customers who need to access their account information, open cases, download NDAs, and create dashboards.

The Customer Account Portal template is designed for creating a site for existing customers who need to access their account information, such as contracts, 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.

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.

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.

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.

The reason for this issue is that the preconfigured Insights reports need to be modified to meet GDPR requirements. Insights is a feature that allows you 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.

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.

Before beginning work on these sites, the consultant should notify the stakeholders that the number of both moderation and rate rules exceeds the org limit. Moderation rules are rules that flag or block content based on keywords, phrases, or patterns. Rate rules are rules that limit the number of posts or comments a user can make in a given time period. The org limit for moderation rules is 10 and the org limit for rate rules is 5. Since each site needs 3 moderation rules and 4 rate rules, the total number of rules for 5 sites is 15 moderation rules and 20 rate rules, which exceed the org limit.

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.

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

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

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.