Experience-Cloud-Consultant Salesforce Certified Experience Cloud Consultant (EX-Con-101) Questions and Answers

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 UC to customize the self-registration process and create person accounts programmatically using Apex code. The standard self-registration configuration does not support personaccounts and requires an existing business account to associate the new users with. Restricting the account record type access for the Site Guest User does not affect the self-registration process and may cause errors.

To create a partner user from an enabled partner account, the correct sequence of steps is C. A partner user is a user who has access to your Experience Cloud site through a partner account. A partner account is an account that has the Is Partner checkbox enabled. To enable a partner user, you need to view the partner account contact, select Manage External User, select Enable Partner User, edit the user record to assign the correct role and profile, and save.

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

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

Partner Central and Build Your Own are two templates that ZRS can consider to build the portal for its partners. Partner Central is a template that is designed for managing partner relationships, such as recruiting, onboarding, training, and co-selling. Build Your Own is a template that allows you to create a custom site using Lightning Web Components and other web standards.

This license type allows third-party staff to access cases, leads, opportunities, contracts, and custom objects on behalf of UMS customers. Partner Community users can also create cases from questions, escalate questions to cases, and view Knowledge articles. Partner Community users cannot access quotes or reports and dashboards.

To find out how current and popular a topic is, site users can go to the topic’s detail page. The topic’s detail page shows information such as the number of followers, the number of posts, and the last activity date of the topic. Site users can alsosee the related topics and subtopics, as well as filter the content by type or time range.

Thisuser license allows users to access cases, Knowledge articles, reports and dashboards, and custom objects in a self-service site. It also provides access to Chatter groups and files, and allows users to edit their own profiles. Customer Community Plus users can also use email-to-case functionality and create records that have lookups to accounts or contacts5

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.

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.

Super User access is a feature that allows you to grant access to records owned by other users who have the same role or a role below them in the role hierarchy. You can use Super User access to give retail managers access to records owned by their peers and subordinates.

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

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.

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.

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.

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 capture information upfront on the Experience site, the administrator should create a pre-chat form to fill out before initiating Chat. A pre-chat form is a form that appears before a chat session starts and asks customers to provide some information, such as their name, email, phone number, or issue description. This helps agents to identify the customer and prepare for the chat session.

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.

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.

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.

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.

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.

Financial Services Community permission set license is a license type that allows users to accessFinancial 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.

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 createa public Knowledge base, NTO should select the Help Center template when building its site. The Help Center template is designed for creating self-service communities where users can find answers to common questions, access articles and FAQs, and contactsupport agents if needed. The Help Center template also supports multiple languages, mobile devices, and branding customization.

This step allows the system administrator to create a partner user from an existing contact that is associated with a partner account. The partner user inherits the role, profile, and permission setsfrom the contact. The system administrator can also specify a username, email address, and nickname for the partner user.

Three valid topic types are Featured Topic, Trending Topic, andStandard Topic. Topics are keywords or phrases that help users find and organize content in Experience Cloud sites. A Featured Topic is a topic that is manually selected by an administrator or moderator to be displayed prominently on the site. A Trending Topic is a topic that is automatically generated by an algorithm based on the popularity and recency of the content. A Standard Topic is a topic that is created by users or administrators and can be assigned to any content.

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.

For records created by guest users, NMH should keep in mind that queues cannot be assigned as owners, setting the default owner is an option in Experience Cloud sites, and any active user in an org can be assigned as the default owner. A queue is a location where records can be routed to await processing by a group of users. However, queues cannot be assigned as owners of records created by guest users because guest users do not have access to queues. Setting the default owner for records created by guests is an option in Experience Cloud sites that allows NMH to specify who will own the records created by guest users on their public site. Any active user in an org can be assigned as the default owner of records created by guest users, as long as they have the appropriate permissions and access to the object.

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.

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.

Two reasons for the import failure are A andD. 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.

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

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.

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.

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.

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.

Two Salesforce recommendations for setting up partner roles in large orgs are B and C. Partner roles are roles that are assigned to partner 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 set up partner roles, you should create themin a separate branch in your Role Hierarchy, which allows you to isolate partner data from internal data and control partner visibility and access. You should also grant partner users access to the partner account using a Sharing Rule, which allows you toshare records owned by internal users with partner users based on criteria that you define.

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.

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 ensure that the partner users are able to register, the site administrator should enable the Contacts under the Account as partner users. This will allow the site administrator to assign a username, password, and profile to each Contact and send them a welcome email with a link to activate their account and log in to the site.

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.

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.

A robots.txt file is a text file that tells web crawlers which pages or files the crawler can or can’t request from your site. This is used mainly to avoid overloading your site with requests; it is not a mechanism for keeping a web page out of Google. You can create a custom robots.txt file for your Experience Cloud site to control how search engines index your site.

To make your Experience Cloud site visible to search engines, you also need to make sure that your site is public and activated. A public site allows anyone on the internet to access your site without logging in. An activated site is live and ready for visitors.

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.

This option allows UMS to configure its search results to include cases, quotes, contracts, and Knowledge articles. TheGlobal 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.

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.