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

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

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

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

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

UMS can accomplish three goals with Experience Cloud moderation functionality:

• Track Flagging and moderation activity within the Experience site. Moderation functionality allows UMS to view reports and dashboards that show the flagging and moderation activity on its site, such as the number of flagged items, the number of moderated items, and the flagging reasons.
• Allow members to flag posts comments files, and messages that are inappropriate or spam. Moderation functionality allows UMS to enable members to flag content that violates the site’s guidelines or policies. Members can choose a flagging reason from a predefined list or enter their own reason.
• Designer specific users as moderators so that they can closely monitor the size. Moderation functionality allows UMS to assign specific users as moderators who have permission to manage content on its site. Moderators can review flagged items, delete or edit inappropriate content, ban or warn abusive users, or escalate issues to administrators.

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.

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.

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

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

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.

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.

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

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.

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

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

To 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 give guest users access to a custom object, CK can use guest user organization-wide defaults (OWD). OWD are a feature that allows you to set the default level of access that guest users have to records of a custom object. You can use OWD to grant Read Only or Read/Write access to guest users for a custom object. For example, CK can use OWD to give guest users Read Only access to the VolunteeringEvent object.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

ExperienceBundle is a feature that allows you to retrieve, deploy, create, update, or delete an Experience Cloud site’s metadata definition in a single API call. Some of the key features of ExperienceBundle are:

• ExperienceBundle enables creating experiences across orgs. You can use ExperienceBundle to move your site’s metadata from one org to another, such as from sandbox to production.
• ExperienceBundle provides editable community metadata in a human-readable format. You can use ExperienceBundle to edit your site’s metadata in JSON or XML format, which makes it easier to understand and modify.

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

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.

A recommended approach for implementing gamification is to use the Missions feature to assign badges to members automatically. Missions are a feature that allows you to create challenges and rewards for your site members based on their actions and behaviors. You can use Missions to define criteria and actions that trigger badges, points, or ranks for your members. For example, you can create a Mission that awards a badge to a member who posts a question, comments on an answer, or likes a post.

The ExperienceBundle Metadata API allows you to retrieve, deploy, create, update, or delete an Experience Cloud site’s metadata definition in a single API call. To use this API, you need to enable the “Enable ExperienceBundle Metadata API” setting in the Experience Cloud site’s administration settings.

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

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.

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.

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.

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.

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.

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 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 first step to create a site is to enable Digital Experiences in your org. This will allow you to access the Experience Cloud site creation wizard, where you can choose a template, a domain name, and a URL for your site.

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.

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.

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

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

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