Salesforce Certified Experience Cloud Consultant Free Sample Questions

External Account Hierarchies are specifically designed for this use case. When enabled, they create a role hierarchy for external users based on their parent accounts, allowing users in higher roles (or the same role) within the same account hierarchy to access records owned by users below them. This meets the requirement without custom sharing rules or sets, which are less suitable for role-based record access among partners.

Even if languages are enabled in the Translation Workbench, they must also be explicitly added to the specific Experience Cloud site's settings in Experience Builder to be active for that site.

Custom text values, such as those in the Navigation Menu, must be translated in the Translation Workbench. The component type would be 'Navigation Menu Item' and each label needs a Spanish translation entry.

The CMS Collection component is the correct choice for displaying a dynamic, curated list of content from a Salesforce CMS workspace. It allows marketers to create collections of content (e.g., 'Featured Partner Resources') in the CMS, which are then automatically rendered by the component on the site page. This meets the requirement for dynamic updates without administrator intervention.

This is true. The 'Execute Registration As' user acts as a system context user to create the new external user, their contact, and potentially their account. This process requires broader permissions than an Experience Cloud user typically has. Therefore, this context user must be an internal user with a full Salesforce license and the necessary permissions to create these records.

This is the most efficient and declarative solution. The consultant can create two audiences, one for 'North America' (e.g., User.Country = 'USA' or 'Canada') and one for 'Europe'. Then, they can place both header components on the page and use the component visibility settings in Experience Builder to assign each one to the appropriate audience. This avoids code and the overhead of managing separate sites.

Salesforce provides a Content Delivery Network (CDN) specifically for Digital Experiences. Enabling the CDN caches static content like images, CSS, and JavaScript files at geographically distributed edge locations. This significantly speeds up content delivery to users by serving it from a location closer to them, which directly addresses the issue of slow-loading, high-resolution images.

The Customer Community license is the correct choice. It is specifically intended for large-scale, B2C use cases like knowledge bases and case management. Its member-based licensing model is more cost-effective for millions of users compared to the role-based model of the Customer Community Plus license.

This is a standard, configurable action in the reputation points settings.

Sharing a post is a default action that can be assigned points to encourage content dissemination.

Endorsing a user for their expertise on a specific topic is a key gamification feature that can be configured to award points.

The theme, branding, and layout are core parts of the site's look and feel and are included in the Bolt package.

Any custom components used on the site's pages are packaged with the Bolt solution to ensure functionality.

Flows are a key part of the declarative automation and business logic of a site and are included to ensure the packaged solution works as intended.

To enable SAML-based single sign-on where Salesforce is the Service Provider (SP) and a third-party is the Identity Provider (IdP), the consultant must configure 'Single Sign-On Settings' in Setup. This involves creating a new SAML configuration, exchanging metadata with the IdP, and then enabling this SSO option on the Experience Cloud site's login page.