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

This license type allows users to access standard objects, such as accounts, contacts, and cases, in a self-service site. However, it does not allow users to access custom objects, such as purchases. UC would need to use a different license type, such as Customer Community Plus, that supports custom objects.

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.

The Customer Account Portal template is designed for creating a site for existing customers who need to access their account information, such ascontracts, 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.

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.

To meet the requirements for both personas, GCC should create a portal for external researchers and give internal staff access to the main org. This will allow GCC to provide different features and permissions for each persona, as well as enable collaboration between them in a private Chatter group. For example, GCC can create a portal for external researchers using the Partner Central template, where they can view and update financial data,access reports and dashboards, and join Chatter groups. GCC can also give internal staff access to the main org using standard user licenses, where they can manage portfolio data, create workflows and processes, and join Chatter groups.

Two statements regarding data categories that are true are A and B. Data category visibility is controlled by roles, permission sets, or profiles. Child roles cannot see more data categories than their parent role, and if the parent role’s visibility changes, the child role’s category visibility is reset to match the parent’s. Customer Portal users and partner portal users inherit data category visibility settings of the role assigned to their account (owner) managers by default, unless they have a custom profile that overrides the role settings.

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.

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

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.

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

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

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

Partner lead routing allows UMS to assign leads to partners based on predefined criteria, such as location, product, or industry. This helps UMS distribute leads more efficiently andincrease partner engagement. Automated quoting capabilities allow partners to generate quotes for customers using UMS’s pricing and discount rules. This helps partners close deals faster and more accurately.

To 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 prevent usability issues, CK should provision and activate CDN in those regions where traffic is high. A CDN is a network of servers that delivers cached static content from websites to users based on the geographic location of the user. By provisioning and activating CDN in high-traffic regions, CK can improve the performance and availability of their public site for their users.

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

The sharing setting that would allow users to collaborate with their peers who work for the same partner firm, but not with any users outside of their firm, is Portal User Visibility. Portal User Visibility is a setting that allows portal users (such as Customer Community or Partner Community users) to see other portal users who have the same role or a role below them in the portal role hierarchy. This setting enables portal users to share information and collaborate with their peers within their own firm, but not with other firms.

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 ContentDelivery Network (CDN) is a feature that improves the performance of public sites by caching static content, such as images, CSS files, and JavaScript files, on servers that are closer to the site visitors. This reduces the load on the Salesforce servers and speeds up the page loading time. CK can enable and configure the CDN from Experience Builder settings.

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.

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

Manually by a moderator selecting ‘’Escalate to Case’’ in the Feed. A moderator is a user who has permission to manage content on your site. A moderator can escalate a question to a case by clicking on the ‘’Escalate to Case’’ action in the Feed menu of the question post.

Automatically via process Builder by meeting specified criteria. Process Builder is a tool that allows you to automate business processes based on criteria and actions. You can use Process Builder to create a process that escalates a question to a case when certain criteria are met, such as number of comments, number of likes, or time elapsed.

To give customers the ability to add authorized users toview usage, billing, and payment history, UMS should grant Delegated External User Administrator permission to customers. Delegated External User Administrator is a permission that allows customers to create new users or reset passwords for other customersin their own account. UMS can use Delegated External User Administration, which isa feature that allows UMS to assign specific users as delegated administrators who can manage external users in their own accounts.

To ensure the changes make it accurately to production, the administrator should create a change set, upload it to production, and deploy the change set. A change set is a collection of metadata components that can be moved from oneorg to another. The administrator can use change sets to migrate point-and-click changes, such as custom objects, fields, layouts, and settings, from the sandbox to the production org. The administrator can create a change set in the sandbox, add the components that have been changed, upload it to the production org, and deploy it in the production org.

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.

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

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.

Three bestpractices 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 andcustomization 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 tocreate 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.

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.

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.

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.

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.

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.

The Rich Content Editor component will be visible to all Platinum customers from California. This isbecause UMS has assigned the component solely to Platinum customers using Audience Targeting, which is a feature that allows UMS to display different content to different audiences based on criteria such as profile, location, domain, or user. UMS has alsoassigned the page variation for the Home page to customers from California using Page Variations, which is a feature that allows UMS to create different versions of a page and assign them to different audiences based on criteria such as record type, fieldvalue, or ownership.

Customer Community Plus and External Apps are two license types that have single SKUs that would support the requirement for UC customers. Customer Community Plus licenses allow users to access standard CRM objects, such ascases and accounts, and custom objects. They also support commerce solutions and custom case management. External Apps licenses allow users to access up to 10 custom objects per app and unlimited standard CRM objects. They also support commerce solutionsand custom case management.

The cause of the error is that accounts used in an External Account Hierarchy cannot be merged with another account. An External Account Hierarchyis 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 ExternalAccount Hierarchy cannot be merged with other accounts, because this would disrupt the hierarchy and the sharing settings.

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.

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.

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.

Audience targeting allows UMS to create audiences based on user attributes, such as profile, location, or language, and display different content or components to different audiences within the same site. For example, UMS can create an audience for premium customers and show them a special offer on the navigation menu, while hiding it from other customers. Audience targeting can beapplied to any component or page in Experience Builder.

To make Knowledge articles available to site users, you need to map topics to data categories and enable the “Share on Sites” setting. Topics are labels that you can assign to articles to make them easier to find and organize. Data categories are away of classifying articles based on a predefined hierarchy. You can map topics to data categories, so that when you assign a topic to an article, it automatically inherits the data category visibility settings. The “Share on Sites” setting allows you to share articles with public users on your site.

Three visibility options available in Experience Cloud are Audience, None, and Default. Visibility options allowyou to control who can see a page or a component on your Experience Cloud site. Audience is an option that allows you to display a page or a component only to users who belong to a specific audience. An audience is a group of users who share common attributes, such as profile, location, or language. None is an option that allows you to hide a page or a component from all users. Default is an option that allows you to display a page or a component to all users who have access to the site.

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.

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 dynamically populate the site with blog posts as new ones are added, CK should use a Grid component with CMS Collections. A Grid component is a componentthat 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.

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.

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.