Salesforce Experience-Cloud-Consultant Salesforce Certified Experience Cloud Consultant (EX-Con-101) Exam Practice Test

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.

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.

BC should look closely into Lightning Bolt solutions during the evaluation phase. Lightning Bolt solutions are industry-specific solutions that include prebuilt themes, templates, pages, components,and business logic for Experience Cloud sites. Lightning Bolt solutions can help BC create personalized experiences for its providers, vendors, installers, and patients by providing them with best practices and ready-made features for their industry. BC can find and install Lightning Bolt solutions from AppExchange or create their own custom solutions using Lightning Bolt framework.

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 ona page, you need to use other components, such as Related List or Record List.

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 andperforming actions based on their inputs. A guest user is a user whoaccesses 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.

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

Standard Topic. This is atopic that is created by users or administrators and assigned to content, such as posts, files, or articles. Users can follow or unfollow standard topics and see the related content on the topic detail page.

Featured Topic. This is a topic that is selectedby administrators to highlight important or popular content on the site. Featured topics appear on the home page or on the topic catalog page of the site.

Navigational Topic. This is a topic that is used to organize content into categories or subcategories on the site. Navigational topics appear on the navigation menu of the site and allow users to browse content by topic.

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

This value is used to map the user’s identity from the externalidentity provider to the user record in Salesforce. The Federation ID must be unique for each user and must match the value of the SAML attribute that is sent by the identity provider during the SSO process. The Federation ID can also be used for JIT provisioning, which creates or updates users on the fly when they log in to the site.

Two Community licenses that allow records to be shared with a criteria-based sharing rule are Partner Community and Customer Community Plus. Theselicense types allow users to access custom objects and a subset of standard CRM objects, such as accounts, contacts, cases, and dashboards. These license types also support advanced sharing features, such as role hierarchy, sharing rules, manual sharing, and Apex sharing.

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.

CDN can help performance by caching public resources, such as images, JavaScript, and CSS files. This can enhance the user experience and reduce the load on CK’s server. CDN stands for Content Delivery Network, which 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.

To implement thenew 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 createa person account for each user based on the information they provide on the self-registration page.

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

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

Case Escalation: You can enable your partners to escalate cases to you when they need your help or expertise.

AI-Powered Knowledge Base: Youcan provide your partners with relevant and personalized knowledge articles powered by Einstein Article Recommendations.

Chat: You can enable your partners to chat with you or other partners in real time using Embedded Service Chat or Salesforce Chat Snap-ins.

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 orblock content based on keywords, phrases, or patterns. Raterules 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 numberof rules for 5 sites is 15 moderation rules and 20 rate rules, which exceed the org limit.

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

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

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.

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.

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

DealRegistration allows UMS to enable its partners to register deals and work with UMS on sales opportunities. UMS can also set up approval processes and validation rules for deal registration and track the deal status and revenue. Lead Distribution allows UMSto assign leads to partners based on predefined criteria, such as location, product, or industry. UMS can also monitor the lead conversion rate and partner performance. Market Development Fund allows UMS to allocate funds to partners for marketing activities, such as events, campaigns, or webinars. UMS can also create budgets, approval workflows, and reports for market development fund.

To set up a topic catalog, the step that is required is to enable Topic Hierarchy and create at least one topic with two subtopics. A topic catalog is a feature that allows you to display all the topics and subtopics on your Experience Cloud site in a hierarchical structure. Users can see the topic catalog by clicking the More Topics link on the navigation menu. To use the topic catalog, you need to enable Topic Hierarchy, which allows you to create topics and subtopics up to three levels deep. You also need to create at least one topic with two subtopics, which will populate the topic catalog with some content.

Three visibility optionsavailable in Experience Cloud are None, Default, and Audience. Visibility options allow you to control who can see a page or a component on your Experience Cloud site. None is an option that allows you to hide a page or a component from all users. Defaultis an option that allows you to display a page or a component to all users who have access to the 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 userswho share common attributes, such as profile, location, or language.

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

The step that denotes the completion of anExperience 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.

Three items that are reportable by a site administrator throughGoogle 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 averagetime on page, and the conversion rate.

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

The default limit for the number of roles for portals is 50,000 per org. You can request an increase from Salesforce if you need moreroles.

Once created, roles cannot be deleted. You can only deactivate them or rename them.

Three actions that are performed automatically when asite 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 userrecord 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.

Branding sets allow you to customize the look and feel of your Experience Cloud site by applying different colors, fonts, images, and logos. You can create multiple branding sets for different audiences and assign them using audience targeting. For example, you can create a special branding set for your Platinum customers and apply it only to them.

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.

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.

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

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.

This functionality allows UMS to create a case from aquestion that has not received a response or has received an unsatisfactory response. UMS can enable this functionality from Experience Builder settings and specify the criteria for escalating a question, such as the number of days without a reply or the number of downvotes. UMS can also assign a queue or an owner for the escalated cases and notify them by email.

ExperienceBundle is a feature that allows you toretrieve, 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 tomove 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, whichmakes it easier to understand and modify.

To dynamically populate the site with blog posts as new ones are added, CK shoulduse 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.

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

User criteria allow you to target audiences based on user fields on CRM objects, such as department, role, or region. You can use user criteria to set up different pages in the portal for different departments and roles within those departments.

To allow UC’s customers to log into CK’s site, an Experience Cloud consultant should recommend establishing SSO between the two Experience Cloud sites by using one org as an identity provider and the other org as a service provider. SSO is a feature that allows users to authenticate withone system and access multiple systems without entering their credentials again. To use SSO between two Experience Cloud sites, you need to use one org as an identity provider (IdP), which is the system that verifies the user’s identity and issues a security token. You also need to use the other org as a service provider (SP), which is the system that accepts the security token and grants access to its resources.

Three things that BC should keep in mind about unauthenticated or guest user access are A, B, and D. Unauthenticated or guest useraccess 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:

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

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 templateis 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 support the sharing requirement of using advanced sharing rules for thecustom object, CK should grant two user license types to customers: Partner Community User and Customer Community Plus Login User. These license types allow customers to access custom objects and a subset of standard CRM objects, such as accounts, contacts, cases, and dashboards. These license types also support advanced sharing features, such as role hierarchy, sharing rules, manual sharing, and Apex sharing.

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.

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.

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.

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

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, suchas:

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.

Two ways thatSalesforce PRM can help DF accelerate channel sales are B and C. Salesforce PRM is a solution that allows you to manage your partner relationships and empower them to sell your products and services. By using Salesforce PRM, DF can automate partner tieringin Channel sales hierarchy, which allows them to assign different tiers and benefits to their partners based on their performance and potential. DF can also automate partner lead routing, which allows them to distribute leads to their partners based on criteria such as location, product, or skill. These features can help DF increase partner engagement and loyalty, optimize lead conversion, and grow channel revenue.

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.

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 creationwizard, where you can choose a template, a domain name, and a URL for your site.