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

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 decrease its call volume using an Experience site, NTO can use standard out-of-the-box functionality such as:

Create an FAQ Knowledge article. A Knowledgearticle is a document that provides information or a solution to a common issue or question. NTO can create an FAQ Knowledge article that answers the most frequently asked questions by its customers and publish it on its site.

Deploy a chatbot to address common questions. A chatbot is an automated conversational agent that can interact with customers using natural language. NTO can deploy a chatbot on its site that can answer common questions, provide information, or escalate issues to agents.

Enable Chatter Questions to encourage peer-to-self-service. Chatter Questions is a feature that allows customers to post questions on your site and get answers from other customers or experts. NTO can enable Chatter Questions on its site to encourage peer-to-self-service and reduce the need for support calls.

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 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 togrant additional permissions to specific users4

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.

This option allows UC to give retail store managers access to the records owned by their peers and subordinates. Super User access isa 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 Useraccess can be enabled for partner users or customer users with Customer Community Plus or Partner Community licenses2

The order in which the community manager should perform activation steps is A. To activate a site in Experience Cloud, you need to complete several steps, such as adding profiles and permission sets, enabling contacts as community users, setting welcome emails, and setting the site to active. The order of these steps is important, because some steps depend on others. For example, you need to add profiles and permission sets before you can enable contacts as community users, and you need to set welcome emails before you can set the site to active.

To fix the issue of Experience Cloud users not being ableto 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.

To move a site from one production org to another production org that is not directly connected, UC should use Lightning BoltExport 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 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

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.

The limitation that the consultant should consider related to sharing and visibility for the Customer Community license type is A. The Customer Community license type is a license type that allows external users to access your Experience Cloud site through a customer account. Customer Community users have limited access and visibility to data in your Salesforce org, and they cannot use roles or sharing rules to share records. To share records with Customer Community users, you need to use SharingSets, which are features that allow you to share records based on common account or contact fields.

This template allows CK to use out-of-the-box components that dynamically update the CMS content on its Experience Cloud site. Build Your Own (LWR) is a template that uses Lightning Web Components (LWC) to create fast and responsive pages. It also supports Salesforce CMS Connect, which allows CK to display CMS content from any CMS source on its site.

Service Your Way is a component that allows customers to choose how they want to interact with a service agent or a chatbot from a list of available channels, such as phone, chat, SMS, WhatsApp, or Facebook Messenger. Service Your Way can be added to any page in Experience Builder and configured to show different channels based on user attributes or device type.

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

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

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.

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.

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.

Two steps that the UC admin should take to grant access to each customer are B and C. To grant access to an Experience Cloud site, you need to assign a license type, a profile, and a permission set to each user. A license type determines what features and functionality a user can access on the site. A profile determines what objects and fields a user can see and edit on the site. Apermission set determines what additional permissions and settings a user can have on the site. To assign a profile and a permission set for a given experience, you need to select them from the drop-down menus in the Admin Workspace of your Experience Builder tool.

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 thetopics assigned to content and filter content by topics.

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 Servicetemplate or the Customer Community Plus license.

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.

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.

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, suchas accounts, contacts, cases, and leads1

To make a Knowledge article visible to both authenticated customers and unauthenticated guest users on the public knowledge base, you need to select the Visible to Public Knowledge Base checkbox when creating the article. This will allow you to share the article with public users on your site. You can also select other visibility options,such as Visible to Customer or Visible to Partner, if you want to share the article with other channels.

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

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

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

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.

To add a background image to arecord 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 youto 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 simplify topics but keep articles that have been assigned to the topics, you need to merge similar topics in Content Management. This will allow you to combine two or more topics into one and update the articles that have been assigned to the merged topics.

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.

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.

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.

To give customers the access they need, CK should use the Account Portal template. The Account Portal template is a pre-built site that includes features such as account management, case management, and refund claims. CKcan use this template to provide self-service options to its customers, such as viewing and updating their account information, creating and viewing cases, and submitting refund claims. CK can also provide access to articles from its Knowledge base using the Knowledge component or the CMS Connect component.

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.

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.

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.

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.

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

To set up a site and gather their customers’ communication preferences, CK should create a Lightning Bolt solution with a template and a login flow to gather the preferences. A Lightning Bolt solution is a package that contains an industry-specific template, theme, flows, apps, and components that can be used to create an Experience Cloud site. CK can create a Lightning Bolt solution that includes a template with the required pages and branding for its customers’ site. CK can also include a login flow in the Lightning Bolt solution, which is a flow that runs when a user logs in to the site. CK can use the login flow to collect the customers’ communication preferences and store them in Salesforce.

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

To implement SAML 550 for the Experience Cloud site, the UC administrator should use thesite 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 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.

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

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 thatincludes 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 orsearching for articles, posting or answering questions, creating or viewing cases, andfollowing or filtering topics. This can help AW Computing reduce the number of calls to its support organization.

Salesforce Partner Relationship Management (PRM) is a solution that helps you manage your partner lifecycle, from recruitment to enablement to co-selling. Some of the waysthat Salesforce PRM can help DF are:

Automating partner onboarding process. You can use Salesforce PRM to create guided onboarding flows that automate tasks, approvals, and notifications for your partners.

Providing reports and dashboards access to partners. You can use Salesforce PRM to share reports and dashboards with your partners that show their performance, pipeline, and revenue.

Preventing channel conflict. You can use Salesforce PRM to assign leads and opportunities to your partners based on rules and criteria that ensure fair distribution and avoid duplication.

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.

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.

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.

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.

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.