Salesforce Experience-Cloud-Consultant - Salesforce Certified Experience Cloud Consultant (EX-Con-101)

The sharing setting that would allow users to collaborate with their peers who work for the same partner firm, but not with any users outside of their firm, is Portal User Visibility. Portal User Visibility is a setting that allows portal users (such as Customer Community or Partner Community users) to see other portal users who have the same role or a role below them in the portal role hierarchy. This setting enables portal users to share information and collaborate with their peers within their own firm, but not with other firms.

Customer Community Plus and External Apps are two license types that have single SKUs that would support the requirement for UC customers. Customer Community Plus licenses allow users to access standard CRM objects, such ascases and accounts, and custom objects. They also support commerce solutions and custom case management. External Apps licenses allow users to access up to 10 custom objects per app and unlimited standard CRM objects. They also support commerce solutionsand custom case management.

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.

Salesforce Content Delivery Network (CDN) is a feature that allows you to improve the performance of your site by caching static resources, such as images, JavaScript, and CSS files. However, changing the Salesforce CDN has some implications, such as:

Changing the Salesforce CDN impacts definitions of all Lightning Web Components used in public pages. You need to redeploy your components after changing the CDN to ensure that they work properly.

Changing the Salesforce CDN does not affect SAML SSO settings for all custom URLs in that domain. SAML SSO settings are independent of the CDN settings.

Changing the Salesforce CDN does not impact the AppExchange packages in the org that use Documents object. Documents object is not affected by the CDN settings.

Changing the Salesforce CDN does not overwrite LDS defaults. LDS defaults are not affected by the CDN settings.

To dynamically populate the site with blog posts as new ones are added, CK should use a Grid component with CMS Collections. A Grid component is a componentthat displays content in a grid layout with rows and columns. A CMS Collection is a collection of content items that are created and managed in Salesforce CMS. CK can use a Grid component and select a CMS Collection as the content source. This will allow CK to showcase blog posts written by AW Computing thought leaders on its site and automatically update them as new ones are added.

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.

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.

When you package your Experience Cloud site, some components and settings are included as dependencies,while others are not. For example:

Custom list views for custom objects are not included as dependencies. You need to manually add them to your package or recreate them in the target org.

Custom list views for standard objects are not included as dependencies. You need to manually add them to your package or recreate them in the target org.

Two Community licenses that allow records to be shared with a criteria-based sharing rule are Partner Community and Customer Community Plus. Theselicense types allow users to access custom objects and a subset of standard CRM objects, such as accounts, contacts, cases, and dashboards. These license types also support advanced sharing features, such as role hierarchy, sharing rules, manual sharing, and Apex sharing.

When building an HR help desk app using Experience Cloud, you need to consider some points, such as:

HR user profile is not only available in Employee Cloud with Employee permission set license. HR user profile is a standard profile that can be used with any user license type that supports Experience Cloud access.

In order to protect employee privacy, the HR help desk app does not need to be created in a different org than the main org. You can use sharing settings and permissions to control who can access what data in your org.

In order to leverage organizational structure, the HR help app must be created in the main org. This will allow you to use role hierarchy and public groups to share data based on your org structure.

HR user profile is not only available in Enterprise and Performance Editions with HR permission set license. HR user profile is available in any edition that supports Experience Cloud.