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

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.

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.

To add partners and internal users to the customer Experience site, the recommended way is to enable the partner accounts and the internal accounts as customers; the usersunder these accounts will then automatically gain access to the customer site. A customer account is an account that has the Is Customer checkbox enabled. This indicates that the account is part of your customer network and can access your customer Experience site. To enable an existing account as a customer, you need to edit the account record and check the Is Customer checkbox. This will automatically grant access to the customer site to all the users under that account, without creating new user recordsor profiles.

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

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.

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.

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.

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

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.

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.

Platform Portal is a user license type that allows users to access custom objects and asubset of standard CRM objects, such as accounts, contacts, cases, and dashboards. This license type is suitable for UMS’s premium B2B customers who need to access their account information, open cases, download NDAs, and create dashboards.

To access Experience Cloud sites, CK’s employees should use the Salesforce Unlimited user license. This license allows employees to access Salesforce and Experience Cloud sites with the same login and credentials. It also provides unlimited custom objects, tabs, and apps, as well as enhanced storage and support. The Salesforce Unlimited user license is the most comprehensive and flexible license for Salesforce users.

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

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.

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.

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 optimize the public knowledge base, a consultant should recommend to bulk-import the top performing articles to Salesforce and select the public knowledge base channel. This will allow NTO to import only the most relevant and useful articles from the external system and make them available to public users on its site. The public knowledge base channel is a feature that allows NTO to share articles with unauthenticated users on its site.

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.

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

To meet the requirement of distributing leads to partners, UMS needs to take at least three steps:

Create aLead Process for Lead Distribution. A lead process is a set of stages that a lead goes through from creation to conversion. UMS can create a lead process that defines how leads are distributed to partners based on criteria such as region, industry, or product.

Create a Lead Queue for Lead Distribution. A lead queue is a list of leads that are assigned to a group of users who share the workload. UMS can create a lead queue for its partners and assign leads to the queue based on the lead process.

Configure Lead creation Leadon low Distribution inside PRM Workspace. PRM Workspace is a feature that allows UMS to manage its partner relationships, such as recruiting, onboarding, training, and co-selling. UMS can configure lead creation and distribution settings inside PRM Workspace, such as enabling partners to create their own leads, setting up lead assignment rules, and defining lead notification preferences.

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

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

Salesforce Content Delivery Network (CDN) is a feature that allows you to improve the performance of your site by caching static resources, such as images, JavaScript, and CSS files. However, changing the Salesforce CDN has some implications, such as:

Changing the Salesforce CDN impacts definitions of all Lightning Web Components used in public pages. You need to redeploy your components after changing the CDN to ensure that they work properly.

Changing the Salesforce CDN does not affect SAML SSO settings for all custom URLs in that domain. SAML SSO settings are independent of the CDN settings.

Changing the Salesforce CDN does not impact the AppExchange packages in the org that use Documents object. Documents object is not affected by the CDN settings.

Changing the Salesforce CDN does not overwrite LDS defaults. LDS defaults are not affected by the CDN settings.

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.

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

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.

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.

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.

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

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.

A prerequisite for creating a user that has a Partner Community license is to enable the account as a partner account. To do this, you need to have the ‘’Enable as Partner’’ action on the Account page layout. This will allow you to convert an existing account or create a new account as a partner account.

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.

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.

This option allows CK to use Google as an external identity provider and enable customers to log in to the site using their Google credentials. CK can also access customers’ basic profile data, such as name, email, and picture, by specifying the scopes and attributes in the authentication provider settings. CK can also use the authentication provider to configure single sign-on (SSO) and just-in-time (JIT) provisioning for the site.

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.

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.

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.

To complete self-registration in NTO’s Experience site without creating a placeholder account, NTO needs to take two steps:

Ensure that the Accountfield is empty in the registration section. This will allow NTO to create individual customers without associating them with an account.

Contact Sales customer Support to enable Person Accounts. Person Accounts are a feature that allows NTO to store information about individual customers in a single record, instead of using separate account and contact records. NTO needs to contact Salesforce Customer Support to enable Person Accounts in its org.

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.

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.

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.

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

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

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.

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.