To use standard profiles in an experience, the step that is required is to enable the “Allow using standard external profiles forself-registration, user creation, and login” option in Setup. A profile is a collection of settings and permissions that determine what users can see and do in Experience Cloud. Standard profiles are predefined profiles that come with Salesforce and cannotbe edited or deleted. To use standard profiles for external users in an experience, you need to enable the “Allow using standard external profiles for self-registration, user creation, and login” option in Setup, which gives you access to use standard profiles such as Customer Community User or Partner Community User.

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.

Site User Visibility allows users within the same site to see each other, regardless of their role or sharing group membership. This is useful forcollaboration between independent researchers and NTO staff on their research-related submissions.

To troubleshoot the problem of the site taking a long time to load, the system administrator should use Salesforce Community Page Optimizer. This is a tool that analyzes the performance of an Experience Cloud site and provides recommendations for improving the page load time. The tool checks for issues such as component density, image size, caching settings, and network latency.

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.

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

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.

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.

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.

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.