Pass the Salesforce Salesforce Consultant Experience-Cloud-Consultant Questions and answers with CertsForce

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

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.

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: Youcan 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 capture the new users self-registering on the B2C site as person accounts in Salesforce, UC should create a custom self-registration page and Apex handler that creates a person account for each user. A custom self-registration page allows UC to customize the look and feel, fields, and logic of the self-registration process. An Apex handler is a class that implements the Auth.RegistrationHandler interface and defines the logic for creating a user and an account. UC can use an Apex handler to createa person account for each user based on the information they provide on the self-registration page.

To allow UC’s customers to log into CK’s site, an Experience Cloud consultant should recommend establishing SSO between the two Experience Cloud sites by using one org as an identity provider and the other org as a service provider. SSO is a feature that allows users to authenticate withone system and access multiple systems without entering their credentials again. To use SSO between two Experience Cloud sites, you need to use one org as an identity provider (IdP), which is the system that verifies the user’s identity and issues a security token. You also need to use the other org as a service provider (SP), which is the system that accepts the security token and grants access to its resources.

Three things that BC should keep in mind about unauthenticated or guest user access are A, B, and D. Unauthenticated or guest useraccess is a feature that allows users to access your Experience Cloud site without logging in or registering. Unauthenticated or guest users have limited access and visibility to data in your Salesforce org, and they have some restrictions, such as:

Guestuser external organization-wide defaults are always set to Private. This means that guest users cannot access any records that are owned by external users (such as Customer Community or Partner Community users) unless they are explicitly shared with them.

Guest user can’t access records via manual sharing. This means that guest users cannot access any records that are shared with them by using the Sharing button on the record detail page.

Guest user can’t be members of public groups or queues. This means that guest users cannot access any records that are shared with them by using public groups or queues as criteria.

The order in which the community manager should perform activation steps is A. To activate a site in Experience Cloud, you need to complete several steps, such as adding profiles and permission sets, enabling contacts as community users, setting welcome emails, and setting the site to active. The order of these steps is important, because some steps depend on others. For example, you need to add profiles and permission sets before you can enable contacts as community users, and you need to set welcome emails before you can set the site to active.

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.

UMS can accomplish three goals with Experience Cloud moderation functionality:

Track Flagging and moderation activity within the Experience site. Moderation functionality allows UMS to view reports and dashboards that show theflagging and moderation activity on its site, such as the number of flagged items, the number of moderated items, and the flagging reasons.

Allow members to flag posts comments files, and messages that are inappropriate or spam. Moderation functionality allows UMS to enable members to flag content that violates the site’s guidelines or policies. Members can choose a flagging reason from a predefined list or enter their own reason.

Designer specific users as moderators so that they can closely monitor the size. Moderation functionality allows UMS to assign specific users as moderators who have permission to manage content on its site. Moderators can review flagged items, delete or edit inappropriate content, ban or warn abusive users, or escalate issues to administrators.