Experience-Cloud-Consultant Practice Test

Salesforce Spring 25 Release -
Updated On 18-Sep-2025

185 Questions

Universal Containers (CU) has been using Salesforce to manage its sales and service processes. UC also an Experience Cloudsite to interact with its customers. UC has now acquired Cloud Kicks (CK) Retail to grow its business, CK also uses Salesforce and a selfservice site built on the experience Cloud to allow its customers to log support requests. UC now wants its customersto be able to use CK’s self-service site so they can have a more integrated experience. What should an Experience Cloud consultant recommend so that UC’s can log in to CK;s site?

A. Create separate user account for UC customer in CK’s Experience Cloud site, since SSO cannot be established between two Experience Cloud sites.

B. Use a third-party identity provider to establish SSO between the two Experience Cloud sites, since Salesforce can only be used as a service provider.

C. Establish SSO between the two Experience Cloud sites by using one org as an identity provider and the other org as a service.

D. Create custom Apex handlers using login method from site class to sign in users from one community to the other.

C.   Establish SSO between the two Experience Cloud sites by using one org as an identity provider and the other org as a service.

Explanation:

To allow UC’s customers to log into CK’s site, an Experience Cloud consultant should recommend establishing SSO between the two Experience Cloud sites by using one org as an identity provider and the other org as a service provider. SSO is a feature that allows users to authenticate with one system and access multiple systems without entering their credentials again. To use SSO between two Experience Cloud sites, you need to use one org as an identity provider (IdP), which is the system that verifies the user’s identity and issues a security token. You also need to use the other org as a service provider (SP), which is the system that accepts the security token and grants access to its resources.

What are two Salesforce recommendations for setting up partner roles in large orgs? Choose 2 answers

A. Create partner roles in the same branch in your Role Hierarchy

B. Create partner roles in a separate branch in your RoleHierarchy.

C. Grant partner users access to the partner account using a Sharing Rule,

D. Reduce the number of roles to one to improve system performance.

B.   Create partner roles in a separate branch in your RoleHierarchy.
C.   Grant partner users access to the partner account using a Sharing Rule,

Explanation:

Two Salesforce recommendations for setting up partner roles in large orgs are B and C. Partner roles are roles that are assigned to partner users who access your Experience Cloud site through a partner account. A partner account is an account that has the Is Partner checkbox enabled. To set up partner roles, you should create the min a separate branch in your Role Hierarchy, which allows you to isolate partner data from internal data and control partner visibility and access. You should also grant partner users access to the partner account using a Sharing Rule, which allows you to share records owned by internal users with partner users based on criteria that you define.

Universal Containers (UC) has a customer portal so that customers can manage their shipping. UC has several sharing rules in place and leverages theExternal Account Hierarchy to assist with data access. One of UC's large customers, Cloud Kicks, has recently acquired Northern Trail Outfitters. Sales wants to merge these two accounts, but they are getting an error. What could be the cause of the error?

A. Accounts with active Experience Cloud users cannot be merged with another account.

B. The user trying to merge the accounts does not have the Merge Portal Roles permission.

C. The user trying to merge the accounts does not have the System Administrator profile.

D. Accounts used in an External Account Hierarchy cannot be merged with another account.

D.   Accounts used in an External Account Hierarchy cannot be merged with another account.

Explanation:

The cause of the error is that accounts used in an External Account Hierarchy cannot be merged with another account. An External Account Hierarchy is a feature that allows you to create a hierarchy of partner accounts and contacts that mirrors the structure of your partner’s organization. This helps you manage data access and visibility for your partners. However, accounts that are part of an ExternalAccount Hierarchy cannot be merged with other accounts, because this would disrupt the hierarchy and the sharing settings.

A consultant for Cloud Kicks (CK) is asked to build a site for CK customers. As part of this site, a custom object will be used to manage customer subscriptions. These subscriptions will need to leverage advanced sharing rules to ensure that only appropriate customers can see these subscriptions. Which two user license types should be granted to customers to support this sharing requirement? (Choose2 answers)

A. Partner Community User

B. Customer Community Login User

C. Customer Community User

D. Customer Community Plus Login User

A.   Partner Community User
D.   Customer Community Plus Login User

Explanation:

To support the sharing requirement of using advanced sharing rules for the custom object, CK should grant two user license types to customers: Partner Community User and Customer Community Plus Login User. These license types allow customers 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.

A consultant needs to leverage ExperienceBundle for a deployment but is unable to view it. What is the most likely cause for this issue?

A. The experience has not yet been published.

B. A change set containing the Network needs to be deployed.

C. The "Enable ExperienceBundle Metadata API" setting needs to be checked.

D. A custom Experience template needs to be created.

C.   The "Enable ExperienceBundle Metadata API" setting needs to be checked.

Explanation:

The ExperienceBundle Metadata API allows you to retrieve, deploy, create, update, or delete an Experience Cloud site’s metadata definition in a single API call. To use this API, you need to enable the “Enable ExperienceBundle Metadata API” setting in the Experience Cloud site’s administration settings.

Experience-Cloud-Consultant Exam Questions - Home
Page 2 out of 37 Pages