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

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.

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 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 fix the issue of Experience Cloud users not being ableto view Contacts and Accounts, you should configure sharing rules on each object to give Read Only access to Experience Cloud users.Sharing rules allow you to extend sharing access to users in public groups, roles, or territories. You can use sharing rules to grant Read Only access to Contacts and Accounts owned by internal users to Experience Cloud users.

This option allows UMS to approve the first post of any new member who has joined within 7 days or less. UMS can create a moderation rule that applies to posts and comments, and specify the member criteria as “Joined Date is within last 7 days”. UMS can alsochoose the action as “Require Approval” and assign a moderator group to review and approve the posts.

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.

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.

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.

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