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

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.

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.

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

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.

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.

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.

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 functionality allows UMS to create a case from aquestion that has not received a response or has received an unsatisfactory response. UMS can enable this functionality from Experience Builder settings and specify the criteria for escalating a question, such as the number of days without a reply or the number of downvotes. UMS can also assign a queue or an owner for the escalated cases and notify them by email.

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.

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.