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

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.

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

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 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 enable the installers to collaborate with their co-workers and UMS staff, UMS needs to enable Portal User Visibility. This is a user visibility setting that allows portal users to see other portal users who have thesame role or a role below them in the role hierarchy. This also allows portal users tosee internal users who are above them in the role hierarchy. Portal User Visibility can be enabled in the Sharing Settings page in Setup.

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

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.

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.

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.

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.

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

The requirement when creating portal users through Just-In-Time (JIT) provisioning is A. JIT provisioning is a feature that allows you to create portal users on demand when they log in using an external identity provider, such as Facebook or Google. To use JIT provisioning, you need to have a FederationIdentifier field on the user object, which is a unique identifier that links the portal user with the external identity provider. The FederationIdentifier field must matchthe value of the NameID element in the SAML assertion sent by the identity provider.

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.

Three fields that are required for creating Experience Cloud users using Data Loader are A, B, and E. Data Loader is a tool that allows you to import or export large amounts of data in or out of your Salesforce org. To create Experience Cloud users using Data Loader, you need to have some required fields in your CSV file, such as:

Profile Id: This field specifies the profile that determines what users can see and do on your Experience Cloud site.

First Name: This field specifies the first name of the user.

Currency: This field specifies the currency that applies to the user’s data.

Other required fields include Last Name, Alias, Email, Username, CommunityNickname, Contact Id (or Account Id), and IsActive.

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.

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.

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.

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.

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.

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.

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.

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.

These two options allow the article to be visible to internal Salesforce users, unauthenticated visitors to the site, and third-party authenticated users. Visible in Public Knowledge Base enables the article to be accessed by guest users without logging in, while Visible to Employee enablesthe article to be accessed by internal users with the appropriate permissions4

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

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.

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.

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 reason for this issue is that the preconfigured Insights reports need to be modified to meet GDPR requirements. Insights is a feature that allowsyou to measure and analyze the adoption and engagement of your Experience Cloud sites using preconfigured reports and dashboards. However, some of these reports may not comply with GDPR, which is a regulation that protects the privacy and data rights of individuals in the European Union. To use Insights for the Experience Cloud site for Europe, the Community manager needs to modify the preconfigured reports to meet GDPR requirements, such as anonymizing user data, obtaining user consent, and deleting user data upon request.

To grant Experience Builder access to two colleagues who will be responsible for creating and managing new microsites, the system administrator should grant Publisher and Builder roles. Publisher and Builder aretwo Experience Builder roles that define what users can do on the site.Publisher is a role that allows users to add contributors, publish changes, and activate or deactivate sites. Builder is a role that allows users to create and customize sites, but not publish them.

This option allows NTO to manage its B2B accounts with multiple levels of hierarchy and grant record access based on the account relationship. External Account Hierarchy is a feature that enables this functionality for Customer Community Plus users. With this feature, users can view and edit records associated with their own account andany child accounts in the hierarchy3

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.

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.

Experience Tracker is a component that informs support agents working in the Service Console what actions a customer has taken on an Experience site. Experience Tracker shows information such as page views, searches, downloads, and case interactions that the customer has performed on the site. This helps agents understand the customer’s context and provide better service.

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.

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.

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.

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

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.

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

CDN can help performance by caching public resources, such as images, JavaScript, and CSS files. This can enhance the user experience and reduce the load on CK’s server. CDN stands for Content Delivery Network, which is a feature that allows CK to improve the performance of its site by caching static resources on servers that are closer to CK’s site visitors.

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

Salesforce AppExchange is a marketplace where customers can find and install pre-built solutions for various industries and use cases. Lightning Bolt solutions are industry-specific templates that include themes, components, pages, and business logic. They are built by Salesforce partners and can be customized to fit specific needs3

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

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

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.

Sharingsets allow you to grant access to records that have a lookup relationship to the same account or contact that the community user has. You can use sharing sets to share opportunities with partner community users who belong to the same account as the opportunity owner.

Criteria-based sharing rules allow you to share records based on field values. You can use criteria-based sharing rules to share opportunities with partner community users who meet certain criteria, such as region, industry, or status.