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

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. The Customer Service template is designed for this purpose and offers a responsive and customizable layout2

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

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.

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 and any child accounts in the hierarchy3

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

CK should keep in mind that Salesforce CDN is not supported in sandbox environments. Salesforce CDN is a feature that allows CK to improve the performance of its site by caching static resources on servers that are closer to CK’s site visitors. However, this feature is only available in production environments and not in sandbox environments, such as Partial and Full sandboxes. Therefore, CK should not use Salesforce CDN for its UAT process.

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 use standard profiles in an experience, the step that is required is to enable the “Allow using standard external profiles for self-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 cannot be 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.

This option allows UMS to showcase the Home page in different ways for its employees and customers. Page variations are different versions of a page with different layouts, components, and content. UMS can create page variations for the Home page and use audience targeting to display different variations to different audiences based on user attributes, such as profile or user type3

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.

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.

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.

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.

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.

Content Management in Workspaces is where UMS can create the CMS collection before configuring the CMS Collection component in Experience Builder. Content Management allows UMS to create, manage, and publish content from Salesforce to its customer portal. UMS can create a CMS collection that contains a group of news articles from a workspace and then use the CMS Collection component to display the collection on its site.

To troubleshoot the problem of the site taking a long time to load, the system administrator should use Salesforce Community Page Optimizer. This is a tool that analyzes the performance of an Experience Cloud site and provides recommendations for improving the page load time. The tool checks for issues such as component density, image size, caching settings, and network latency.

The requirement when creating portal users through Just-In-Time (JIT) provisioning is A. JIT provisioning is a feature that allows you to create portal users on demand when they log in using an external identity provider, such as Facebook or Google. To use JIT provisioning, you need to have a FederationIdentifier field on the user object, which is a unique identifier that links the portal user with the external identity provider. The FederationIdentifier field must match the value of the NameID element in the SAML assertion sent by the identity provider.

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.

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.

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

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.

To differentiate between the leads created by partners and the leads created by its own Sales team, UMS should create lead record types and page layouts for lead distribution. A record type is a way to offer different business processes, picklist values, and page layouts to different users based on their profiles. A page layout is a way to control the layout and organization of detail and edit pages in Salesforce. By creating lead record types and page layouts, UMS can customize the fields and values that are displayed to partners and Sales team members.

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.

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.

Partner Super User access is a feature that allows you to grant access to records owned by other partner users who have the 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.

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

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.

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

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.

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

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

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.

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.

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.

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.

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 solve these requirements, the administrator should create branding sets, audience targeting, and navigation menu targeting. Branding sets are collections of branding elements, such as colors, fonts, images, and logos, that you can apply to your Experience Cloud site. Audience targeting is a feature that allows you to display pages and components to certain users based on their assigned audience. Navigation menu targeting is a feature that allows you to display different navigation menu items to different users based on their assigned audience. By using these features, the administrator can create different branded experiences for each partner, control the access to the Leads inbox component and the Leads tab, and customize the navigation menu for each partner.

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.

A question can be escalated to a case in two ways:

• Manually by a moderator selecting ‘’Escalate to Case’’ in the Feed. A moderator is a user who has permission to manage content on your site. A moderator can escalate a question to a case by clicking on the ‘’Escalate to Case’’ action in the Feed menu of the question post.
• Automatically via process Builder by meeting specified criteria. Process Builder is a tool that allows you to automate business processes based on criteria and actions. You can use Process Builder to create a process that escalates a question to a case when certain criteria are met, such as number of comments, number of likes, or time elapsed.

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.

To fix the issue of Experience Cloud users not being able to view Contacts and Accounts, you should configure sharing rules on each object to give Read Only access to Experience Cloud users. Sharing rules allow you to extend sharing access to users in public groups, roles, or territories. You can use sharing rules to grant Read Only access to Contacts and Accounts owned by internal users to Experience Cloud users.

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

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.

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

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.

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.

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.

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

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.