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 match the value of the NameID element in the SAML assertion sent by the identity provider.

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.

This user 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 Partner Relationship Management (PRM) is a solution that helps you manage your partner lifecycle, from recruitment to enablement to co-selling. Some of the ways that Salesforce PRM can help DF are:

• Automating partner onboarding process. You can use Salesforce PRM to create guided onboarding flows that automate tasks, approvals, and notifications for your partners.
• Providing reports and dashboards access to partners. You can use Salesforce PRM to share reports and dashboards with your partners that show their performance, pipeline, and revenue.
• Preventing channel conflict. You can use Salesforce PRM to assign leads and opportunities to your partners based on rules and criteria that ensure fair distribution and avoid duplication.

Salesforce Partner Relationship Management (PRM) is a solution that helps you manage your partner lifecycle, from recruitment to enablement to co-selling. Salesforce PRM comes with some standard features that you can leverage without any code customization, such as:

• Case Escalation: You can enable your partners to escalate cases to you when they need your help or expertise.
• AI-Powered Knowledge Base: You can provide your partners with relevant and personalized knowledge articles powered by Einstein Article Recommendations.
• Chat: You can enable your partners to chat with you or other partners in real time using Embedded Service Chat or Salesforce Chat Snap-ins.

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

Partner Super User access is a feature that allows you to grant access to records owned by other partner users who have the same role or a role below them in the role hierarchy. You can apply Partner Super User access to three objects: Opportunities, Accounts, and Custom Objects.

Partner Central is a template that is designed for creating a site that supports channel sales, lead distribution, and deal registration. The template includes features such as partner recruitment, onboarding, training, co-selling, lead management, opportunity management, and deal registration.

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.

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.

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 template is 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 complete self-registration in NTO’s Experience site without creating a placeholder account, NTO needs to take two steps:

• Ensure that the Account field 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.

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.

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

Two ways that Salesforce PRM can help DF accelerate channel sales are B and C. Salesforce PRM is a solution that allows you to manage your partner relationships and empower them to sell your products and services. By using Salesforce PRM, DF can automate partner tiering in Channel sales hierarchy, which allows them to assign different tiers and benefits to their partners based on their performance and potential. DF can also automate partner lead routing, which allows them to distribute leads to their partners based on criteria such as location, product, or skill. These features can help DF increase partner engagement and loyalty, optimize lead conversion, and grow channel revenue.

Two considerations for creating partner users and granting access are B and C. Partner users are external 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 create partner users and grant access, you need to assign them a license type and a profile. Two license types that are suitable for partner users are Partner Community and Customer Community Plus. These license types allow partner users to access standard CRM objects, such as accounts, contacts, leads, opportunities, and cases, as well as custom objects and tabs. They also allow partner users to use roles and sharing rules to share records with other users.

Three topic types that can be used in an Aura site are:

• Standard Topic. This is a topic 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 selected by 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.

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

Three KPIs that could be used to measure the chatbot’s impact on customer service are B, C, and D. CSAT is a metric that measures how satisfied customers are with their chatbot experience on a scale of 1 to 5 stars. Case deflection is a metric that measures how many cases are avoided or resolved by the chatbot without escalating to an agent. Average Handle Time is a metric that measures how long it takes an agent to handle a case from start to finish. Bot Session Time is a metric that measures how long it takes a chatbot to handle a conversation from start to finish. By comparing these metrics, you can evaluate the chatbot’s performance and efficiency in providing customer service.

To implement the new style guide and unify branding across all of its Experience sites, UC should create a custom theme and apply it to all sites. A theme is a collection of branding assets and style settings that define the look and feel of your site. You can create a custom theme that matches your style guide and apply it to multiple sites using the Theme Management feature in Experience Builder.

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.

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.

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 or block content based on keywords, phrases, or patterns. Rate rules 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 number of rules for 5 sites is 15 moderation rules and 20 rate rules, which exceed the org limit.

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

This value is used to map the user’s identity from the external identity 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 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 the topics assigned to content and filter content by topics.

Three visibility options available in Experience Cloud are Audience, None, and Default. Visibility options allow you 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.

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.

Three actions that are performed automatically when a site 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 user record 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 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 create a new partner user for an existing site, you need to first create a contact record for the partner user, then click “Manage External User” on the contact detail page, and then click “Enable Partner User”. This will allow you to provide user details and save the user record.

This option allows UMS to configure its search results to include cases, quotes, contracts, and Knowledge articles. The Global 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 give guest users access to a custom object, CK can use guest user organization-wide defaults (OWD). OWD are a feature that allows you to set the default level of access that guest users have to records of a custom object. You can use OWD to grant Read Only or Read/Write access to guest users for a custom object. For example, CK can use OWD to give guest users Read Only access to the VolunteeringEvent object.

To give customers the ability to add authorized users to view 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 customers in their own account. UMS can use Delegated External User Administration, which is a feature that allows UMS to assign specific users as delegated administrators who can manage external users in their own accounts.

To move a site from one production org to another production org that is not directly connected, UC should use Lightning Bolt Export and Installation. Lightning Bolt is a feature that allows UC to export a site as a package that contains the site template, theme, pages, components, and content. UC can then install the package in another org using the AppExchange or a URL link.

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

This option allows UC to control the access to the partner application form and ensure that only qualified partners can apply. Token-based referral links are unique and expire after a certain time, which adds an extra layer of security. Creating an app for the internal team also allows UC to track the performance of the referral program and reward the existing partners accordingly1

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

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.

Two options that make it possible to have a vertical navigation menu in the customer portal are B and D. A navigation menu is a component that allows users to navigate through different pages and sections of your Experience Cloud site. By default, the navigation menu is horizontal, but you can change it to vertical by using different options. One option is to download an app from AppExchange, which is a marketplace where you can find and install apps, components, and solutions for your Experience Cloud site. Another option is to write custom code, which allows you to create your own custom components and layouts for your Experience Cloud site.

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.

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.

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

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.

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 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 your Experience 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 to different 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 for each partner.

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. A permission 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 create a 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 contact support agents if needed. The Help Center template also supports multiple languages, mobile devices, and branding customization.

Three key features of Metadata API are A, B, and C. Metadata API is an API that allows you to retrieve, 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, because it allows you to handle fine-grained customizations and dependencies.

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

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 also see the related topics and subtopics, as well as filter the content by type or time range.

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.