• Home
• Salesforce Exams
• Certified Experience Cloud Consultant

Certified Experience Cloud Consultant Salesforce Practice Test Questions and Exam Dumps

Question 1
Bloomington Caregivers (BC) wants to improve its internal workflows and has recently heard about Lightning Bolt solutions. 

Where should BC go to find available Lightning Bolt solutions?

A. Salesforce Connect
B. Salesforce AppExchange
C. Salesforce Accelerator Directory
D. Salesforce Accelerator Catalog

Correct Answer: B

Explanation:

When an organization such as Bloomington Caregivers (BC) is looking to streamline internal workflows and has learned about Lightning Bolt solutions, the best place to explore and obtain these packaged solutions is the Salesforce AppExchange.

Lightning Bolt solutions are pre-built templates that include customizable apps, components, and communities tailored to specific industries or business use cases. These solutions are built on the Salesforce Lightning framework and are designed to accelerate the deployment of portals, customer service solutions, and partner communities by offering reusable templates.

Let’s break down the relevance of each option to clarify why Option B is correct:

Option A: Salesforce Connect
This is a tool used to integrate external data sources into the Salesforce platform in real time using standard protocols like OData. While powerful for accessing data across systems, it does not provide Lightning Bolt solutions or packaged workflow tools. It's a connectivity service, not a marketplace or solution directory.

Option B: Salesforce AppExchange
This is the official Salesforce marketplace where businesses can find third-party applications, Lightning Components, and Lightning Bolt solutions. AppExchange allows organizations to browse, evaluate, and install pre-built solutions to meet a variety of needs including employee workflows, customer service portals, and partner collaboration tools. Since Lightning Bolt solutions are distributed through AppExchange, this is precisely where BC should look.

Option C: Salesforce Accelerator Directory
This doesn’t refer to a publicly available resource for customers to explore solutions. Salesforce Accelerators are typically consulting or advisory services offered by Salesforce Customer Success or Professional Services teams to help customers achieve specific goals. It is not a repository for packaged solutions like Lightning Bolts.

Option D: Salesforce Accelerator Catalog
Similar to Option C, this is generally a service-oriented resource listing various advisory and enablement services, not pre-packaged product or solution templates. It may help guide implementation but does not contain Lightning Bolt solutions for installation.

In conclusion, since Lightning Bolt solutions are shared and distributed through Salesforce’s own AppExchange marketplace, this is where organizations like Bloomington Caregivers can find, compare, and adopt ready-made tools tailored to their needs. The other options either serve different purposes (integration, advisory services) or are not related to Lightning Bolt distribution.

Question 2
Universal Containers (UC) collaborates with a wide network of retailers and wants them to register deals and help close sales. 

Which user license is the most suitable for enabling this type of collaboration?

A. Partner Community Plus
B. Commerce Portal
C. Partner Community
D. Platform Portal

Correct Answer: C

Explanation:

Universal Containers is looking to enable deal registration and sales collaboration with its retail partners. This scenario clearly requires partner relationship management (PRM) functionality, which includes features like lead and opportunity management, campaign sharing, and deal registration. These features are specifically designed for users who participate in selling activities on behalf of a Salesforce customer, and they are made available through the Partner Community license.

Let’s explore the details and differences between the options:

Option A: Partner Community Plus
This license offers advanced access to data and reports, supporting larger-scale collaboration use cases. However, this option is often more expensive and targeted at partners who need access to more objects, roles, and sharing capabilities. While it could technically support UC's use case, it might be more powerful (and costly) than necessary if UC just needs basic deal registration and sales tracking.

Option B: Commerce Portal
This license is designed for buyers and sellers who need to access eCommerce capabilities. It’s not suited for managing deals or sales opportunities. It supports simple B2B or B2C purchasing scenarios, not channel sales or partner management. Therefore, it’s not appropriate for UC's stated needs.

Option C: Partner Community
This is the ideal license for enabling partner users—such as resellers, distributors, and in this case, retailers—to register leads, manage opportunities, and collaborate on deals. It includes access to standard CRM objects like Leads, Opportunities, Accounts, and Contacts, and allows retailers to function as external sales reps in UC's Salesforce org. It's designed for exactly this kind of partner relationship.

Option D: Platform Portal
This license offers access to custom objects and limited standard objects, but it does not support access to CRM objects like Leads and Opportunities, which are essential for deal registration and sales. This license is appropriate for custom application users who don’t require full CRM functionality—so it doesn’t fit UC's requirements.

In conclusion, since UC’s goal is to have retailers register deals and help drive sales, the Partner Community license is best suited to meet those needs. It’s cost-effective, purpose-built for this type of collaboration, and fully supports the CRM capabilities required.

Question 3
Ursa Major Solar wants to place three Record Detail components on a portal page to show Account, Case, and Opportunity details for the logged-in user. However, the page isn't displaying as expected. 

What is the most likely cause of the issue?

A. The Record Detail component populates the recordID associated with the object for the page template, so this component will not work for this use case.
B. The Record Detail component will only show record details for the Case object.
C. The Record Detail component populates the recordID associated with the object for the page template, so this component will only work on the Home page template.
D. The Record Detail component is a custom component and was not configured correctly.

Correct Answer: A

Explanation:

The Record Detail component in Salesforce Experience Cloud is designed to dynamically show the details of a single record based on the context provided by the page’s template. The key to using this component effectively is understanding how it uses the recordId—a special property that determines which record's data is displayed.

In Ursa Major Solar’s case, the team wants to show details from three separate objects—Account, Case, and Opportunity—on a single page. They’ve placed three Record Detail components, expecting each to independently display a different object’s data for the currently logged-in user. However, this assumption is not supported by the standard behavior of the Record Detail component.

By default, the Record Detail component automatically binds to the recordId provided by the template’s route context. This means that all instances of the component on a single page will reference the same recordId, which comes from the page’s routing or configuration (e.g., a Case detail page provides a caseId). As a result, placing three of them on a page without separately specifying different recordIds (via custom logic or other means) leads to incorrect or repeated data displays.

Here’s a closer look at the options:

Option A: This is correct. It explains that the Record Detail component relies on the recordId determined by the page's template context, and since only one recordId is supported per template context, using multiple Record Detail components to show different objects on the same page won’t work by default. This is a known limitation unless custom development or component overrides are introduced.

Option B: Incorrect. The Record Detail component is not restricted to the Case object. It is a generic component that works for any object, standard or custom, as long as the correct recordId is passed to it.

Option C: Incorrect. The issue is not tied to the Home page template. The limitation comes from how recordId is derived from the current page context, regardless of the page type. This means the problem isn’t exclusive to the Home template but is a general behavior of Experience Cloud routing and record binding.

Option D: Incorrect. While misconfigured custom components can cause display issues, the Record Detail component is a standard Salesforce component, not a custom one. There's no mention in the question of using custom-built functionality. Also, if configuration was the issue, the problem would not specifically prevent multiple object details from being shown—it would just result in broken or missing data.

Question 4
Universal Containers (UC) plans to build a self-service site for both current and potential customers, offering resources like articles, manuals, FAQs, and user forums. 

Which two Experience Cloud features should UC prioritize while building the site? (Choose two.)

A. Content Delivery Network (CDN)
B. Guest user and public access settings
C. Public Site Connect
D. Document Library Model (DLM)

Correct Answers: B, D

Explanation:

Universal Containers is aiming to develop a do-it-yourself, self-service site that is accessible to both existing customers and prospective users. The site’s core functionalities will include informational content (like manuals, blogs, and FAQs) and interactive features like Q&A between users. Given these requirements, the Experience Cloud setup must support public access, community interaction, and content management.

Let’s break down each option and why B and D are correct.

Option A: Content Delivery Network (CDN)
A CDN enhances website performance by caching content and delivering it quickly from servers closest to the user. While this is beneficial for performance, it is not a foundational feature when starting to build an Experience Cloud site. CDN is more of an optimization tool that can be introduced later once the core structure and access models are in place. Therefore, although helpful, it is not a primary concern at the beginning of site development.

Option B: Guest user and public access settings
This is absolutely essential. Since UC wants the site to be accessible to prospective customers (who may not have Salesforce accounts), public access must be enabled. Configuring guest user permissions ensures that unauthenticated users can view content like FAQs, blogs, and manuals, and possibly even interact through Q&A if permissions allow. This setup directly supports self-service functionality and is one of the first things to establish when building such a site.

Option C: Public Site Connect
This is not a standard Salesforce Experience Cloud feature and appears to be a distractor or fictional option. It does not represent a native capability of Experience Cloud. There’s no documented feature by this name within the Salesforce platform, making it irrelevant in this context.

Option D: Document Library Model (DLM)
This is important for managing the storage and organization of documents and files such as user manuals, guides, or downloadable resources. It allows you to efficiently handle document metadata, version control, and sharing rules—all crucial when publishing materials to a wide audience on a self-service portal. For UC, which wants to offer articles, manuals, and similar resources, a strong document management approach is critical from the start.

In summary, UC should initially focus on configuring public/guest access so the site is usable by unauthenticated users and on organizing content using a proper document library framework. Performance enhancements like CDNs can come after the foundational elements are in place.

Question 5
Northern Trail Outfitters (NTO) wants to manage large B2B customer accounts, each with multiple departments as child accounts. Opportunities will exist at the department level, and users from the parent account should have visibility into these. NTO uses Customer Community Plus licenses. 

What is the best way to manage these accounts in its Partner Community?

A. Since NTO has person accounts, it cannot use the External Account Hierarchy and will need to use groups and sharing rules to grant the required record access.
B. Use the Business Accounts and Contacts with Sharing Sets to grant additional record access as needed.
C. Extend the Standard Role Hierarchy setting departments as child accounts.
D. Enable the External Account Hierarchy setting departments as child accounts.

Correct Answer: D

Explanation:

Northern Trail Outfitters is dealing with a common B2B scenario where parent-child account relationships represent organizational hierarchies, such as departments under a main company. In Experience Cloud (Partner Communities), record visibility and access delegation are critical when structuring such relationships. Since NTO is already using Customer Community Plus licenses, it has access to advanced sharing features like role hierarchy and External Account Hierarchy.

Let’s evaluate the options in detail:

Option A:
This option falsely claims that having person accounts prevents use of External Account Hierarchy. While person accounts are a different record type designed for B2C models, NTO is using business accounts for its B2B customers. The existence of person accounts in the same org does not preclude the use of External Account Hierarchy with business accounts. Therefore, this is incorrect.

Option B:
This approach suggests using Sharing Sets, which are available with Customer Community and Customer Community Plus licenses. While Sharing Sets can grant access to records based on the user’s account or contact, they are generally better suited for simple access scenarios—not for hierarchical structures like parent-child accounts. Sharing Sets do not offer the granular, scalable sharing needed across related accounts and opportunities, making this option insufficient for the use case.

Option C:
Standard Role Hierarchy is often used internally to grant access from subordinates up to managers, but it does not natively reflect account hierarchies. Additionally, while partner users can be placed into roles, role hierarchy alone doesn’t automatically grant visibility from one account's opportunities to another unless sharing rules are defined. In a complex structure like parent-child accounts with related opportunities, the External Account Hierarchy is the more appropriate tool. Thus, this option is not optimal.

Option D:
This is the correct approach. Salesforce introduced the External Account Hierarchy feature specifically to support visibility across a hierarchy of related accounts in Experience Cloud. This feature allows partner users associated with a parent account to automatically see records (like Opportunities) owned by users in child accounts, provided proper sharing settings are enabled. It works seamlessly with Customer Community Plus and Partner Community licenses, which support the feature. NTO’s need to support visibility from parent accounts into child-level opportunities matches this model perfectly.

Question 6
Cloud Kicks (CK) is preparing to launch a public-facing site that will feature both static and dynamic digital content. CK intends to utilize a Content Delivery Network (CDN). 

What is a true statement about how CDN supports Experience Cloud?

A. CDN can help consistency by attaching content timestamps as key-value pairs to both static and dynamic content.
B. CDN can help availability by allowing remote cloning for dynamic resources.
C. CDN can help reliability by allowing local cloning for static resources.
D. CDN can help performance by caching public resources.

Correct Answer: D

Explanation:

Cloud Kicks (CK) is planning to create a public site hosted on Salesforce Experience Cloud, and they’re interested in enhancing site performance using a Content Delivery Network (CDN). A CDN is a globally distributed network of servers that cache content closer to users geographically. Its main advantage lies in improving performance and scalability by caching and serving static resources quickly, which is particularly valuable for public sites with global or high-volume traffic.

Let’s evaluate each option in detail:

Option A: CDN can help consistency by attaching content timestamps as key-value pairs to both static and dynamic content.
This statement is not accurate in the context of what CDNs are designed to do. CDNs don’t typically deal with content consistency by attaching timestamps as key-value pairs. Instead, caching behaviors are governed by HTTP headers such as Cache-Control, ETag, and Last-Modified. While timestamps can be used for cache invalidation, this isn't a defining or primary feature of CDNs, and the explanation provided is misleading.

Option B: CDN can help availability by allowing remote cloning for dynamic resources.
CDNs are not designed to clone or replicate dynamic resources. Dynamic resources (like real-time database queries or user-specific data) are usually not cached, as they change frequently and must reflect live data. CDNs do not improve availability through remote cloning of dynamic content; they primarily focus on distributing and caching static assets such as images, scripts, and style sheets.

Option C: CDN can help reliability by allowing local cloning for static resources.
This statement is vague and misleading. While CDNs do replicate static content to edge servers for faster delivery, the term “local cloning” is not a standard or recognized CDN function. The purpose of caching static resources is performance improvement, not primarily reliability. Reliability in content delivery may be an indirect benefit, but it’s not achieved through "cloning" as described here.

Option D: CDN can help performance by caching public resources.
This is the correct and most accurate description of a CDN’s role. CDNs are built to cache static, publicly accessible resources at geographically distributed edge locations, significantly reducing load times for end users. In the context of Salesforce Experience Cloud, this can result in faster loading of images, stylesheets, JavaScript files, and other static assets, which improves the user experience, particularly for a public site like the one Cloud Kicks is launching.

In conclusion, when deploying a public site using Experience Cloud, performance optimization through resource caching is the key benefit CDNs provide. Caching reduces latency, decreases server load, and improves page response times — all of which are critical for public websites expecting varied and potentially heavy traffic.

Question 7
Dreamscape Flowers has launched three Experience Cloud sites for different regions: North America, Europe, and Asia Pacific. Community managers are using the Salesforce Communities Management package for insights. However, the European Community manager reports that the preconfigured Insights reports are not usable for their site. 

What is the most likely reason for this issue?

A. The Community manager for Europe does not have System Administrator privileges.
B. The preconfigured Insights reports need to be modified to meet GDPR requirements.
C. The Experience Cloud site for Europe has more than a million users.
D. The Experience Cloud site for Europe is not using Chatter which is needed to use the preconfigured Insights reports.

Correct Answer: D

Explanation:

Salesforce provides preconfigured Insights reports as part of the Communities Management package (formerly called Salesforce Communities Management), which helps community managers track metrics related to user adoption, engagement, content performance, and more. These reports rely on certain platform features and activity data—one of which is Chatter, Salesforce’s collaboration tool.

Let’s break down the key options:

Option A: The Community manager for Europe does not have System Administrator privileges.
While administrative privileges can impact access to report folders or report creation, they are not required to view preconfigured Insights reports if the Community Manager has been given appropriate sharing or access rights. The Community Management package is designed to work for community managers, not just administrators. So, lacking sysadmin rights alone would not prevent the reports from being used.

Option B: The preconfigured Insights reports need to be modified to meet GDPR requirements.
Although GDPR may affect what user data can be displayed or stored, Salesforce provides GDPR-compliant tooling and anonymization features. However, the inability to use preconfigured reports isn’t typically tied to compliance issues. Salesforce doesn't block the use of these reports in EU regions by default. Moreover, modifying reports for GDPR would relate to content restrictions, not complete inaccessibility.

Option C: The Experience Cloud site for Europe has more than a million users.
Even though performance and scalability issues might emerge with very large communities, Salesforce Experience Cloud supports communities at scale, especially with proper configuration. There is no hard limit of one million users that would prevent the Insights reports from functioning. This option is speculative and not grounded in a known platform limitation related to the Communities Management package.

Option D: The Experience Cloud site for Europe is not using Chatter which is needed to use the preconfigured Insights reports.
This is the correct answer. Many of the preconfigured reports that come with the Communities Management package depend on Chatter activity—likes, posts, questions, comments, and follows—to generate data. If Chatter is disabled for a particular Experience Cloud site, the necessary data sources for these reports simply won’t exist. As a result, the reports would either show no data or wouldn’t function as intended.

This aligns with Salesforce documentation and known behaviors: Chatter must be enabled for Insights reports that track engagement, collaboration, and interaction within the community. If the European site has Chatter turned off—perhaps due to regional preferences, compliance, or performance reasons—then the data pipeline supporting the preconfigured reports would be broken.

Therefore, the inability to use the preconfigured Insights reports on the Europe site is due to the lack of Chatter usage, which is essential for these reports to function.

Question 8
Which three permissions are included for a delegated administrator? (Choose three.)

A. Manage permissions sets for external users on their account.
B. Add external users to multiple accounts.
C. Generate new passwords for external users.
D. Manage object access for external users.
E. Create and edit external user records.

Correct Answers: C, D, E

Explanation:

In Salesforce, a delegated administrator is a user who is granted specific administrative privileges for a subset of users, roles, and profiles. Delegated administration is used to delegate routine user and data administration tasks—such as resetting passwords, unlocking users, assigning users to profiles or roles, and managing user accounts—without granting full system administrator rights.

Let’s evaluate each option based on what delegated administrators are allowed to do:

A. Manage permission sets for external users on their account.
This is not something delegated administrators can do. Managing permission sets—especially assigning them to users—is a more advanced privilege that typically requires system administrator access. Delegated administrators cannot assign permission sets, as that would involve broader access control than intended for their role. So this option is incorrect.

B. Add external users to multiple accounts.
This is also incorrect. In Salesforce, external users (such as portal or community users) are usually associated with a single account, and delegated administrators do not have permission to create or assign users across multiple accounts. Their scope is limited to managing users within the accounts they are assigned to administer.

C. Generate new passwords for external users.
This is correct. One of the primary capabilities of a delegated administrator is to reset passwords and unlock user accounts, including external users such as community members. This ensures that delegated admins can handle routine login issues without needing a full admin's involvement.

D. Manage object access for external users.
This is correct. Delegated administrators have the ability to manage object-level and field-level access for the users they manage. This includes configuring profiles and permissions relevant to external users within their designated scope. While they can't create custom profiles, they can assign existing ones and manage access settings.

E. Create and edit external user records.
This is correct. Delegated administrators can create and edit user accounts, including community users and other external user types, as long as the accounts fall within the scope of accounts and roles assigned to them. This is one of their fundamental capabilities, allowing decentralized user management across business units or partner organizations.

In summary:

• A is incorrect because delegated admins cannot manage permission sets.

• B is incorrect because delegated admins cannot assign external users to multiple accounts.

• C, D, and E are correct because these are all part of delegated admin capabilities focused on managing user accounts, access, and login support for external users.

Correct answers: C, D, E

Question 9
Ursa Major Solar (UMS) is automating its business processes using Salesforce. UMS wants its Platinum partners to be able to approve installation projects and deals. 

Which two approaches can help UMS achieve this goal? (Choose two.)

A. Assign external users Super User access on records and create a digital experience for those users.
B. Add external users directly to approval queues and create a digital experience for those users.
C. Assign external users as approvers on records and create a digital experience for those users.
D. Assign external users as the co-owners on records and create a digital experience for those users.

Correct Answers: A, C

Explanation:

In Salesforce Experience Cloud (formerly known as Communities), it is common to allow external users (like partners or customers) to engage in collaborative business processes such as deal approvals or project sign-offs. When Ursa Major Solar (UMS) wants Platinum partners to approve installation projects and deals, the main goal is to provide those users the right permissions, access, and interface for interacting with those records and participating in approval workflows.

Let’s examine the options:

A. Assign external users Super User access on records and create a digital experience for those users.
This is correct. The Super User feature in Experience Cloud allows a partner user to see and access more data, especially records owned by other users in their partner account. This is particularly useful in approval processes where users may need to access records they don’t directly own. When paired with a digital experience site (portal/community), this allows partners to view and take action on relevant records efficiently.

B. Add external users directly to approval queues and create a digital experience for those users.
This is incorrect. Salesforce approval queues do not support external users (like partner community users) in the same way internal queues do. Queues are generally used for record assignment (e.g., Cases, Leads), not for approval routing. Also, approval processes are based on users, roles, or public groups—not queues. Therefore, this approach would not work for enabling external users to approve records.

C. Assign external users as approvers on records and create a digital experience for those users.
This is correct. Salesforce approval processes can be configured to include external users as approvers if they have the correct permissions and access via a digital experience (Experience Cloud) site. This means a partner user can receive an approval request, log in through the portal, and approve or reject records such as projects and deals. The key is ensuring that approval steps are designed to include those community roles or specific partner users.

D. Assign external users as the co-owners on records and create a digital experience for those users.
This is incorrect because Salesforce does not have a co-owner field on standard objects like Opportunities or custom installation projects. While record sharing rules can grant access to other users, there is no concept of a formal co-owner that would inherently enable participation in approval workflows. Furthermore, record access alone doesn’t imply the user is an approver in an approval process.

Summary:

• A is valid because Super User access expands visibility for partners involved in approvals.

• C is valid because external users can be approvers when properly configured in approval steps.

• B is invalid since queues are not used for approval routing, especially not with external users.

• D is invalid because there’s no co-owner concept for Salesforce records or approval logic.

Correct answers: A, C

Question 10
Northern Trail Outfitters has a network of resellers who are Partner Community users. One of the resellers has requested that their parent company get View access to cases created by their child companies. 

Which functionality will meet the requirement best?

A. Manually share cases.
B. Create a Sharing Set for the Account.
C. Move users who need case access to a higher level in the Role Hierarchy.
D. Configure an External Account Hierarchy.

Correct Answer: D

Explanation:

The scenario describes a common use case in B2B Experience Cloud (formerly Partner Community): A parent company (reseller) wants to view cases created by their child companies (sub-resellers or subsidiaries). To fulfill this requirement efficiently and at scale, External Account Hierarchy (EAH) is the most appropriate and powerful tool.

Let’s examine the available choices:

A. Manually share cases.
This is not an ideal solution for several reasons. Manual sharing is time-consuming, error-prone, and does not scale when case volumes grow or as new child accounts are added. It requires someone to explicitly share each case record with users in the parent account, which goes against best practices for community scalability.

B. Create a Sharing Set for the Account.
Sharing Sets are indeed a way to give Experience Cloud users access to records based on their account, contact, or user field values. However, Sharing Sets do not support cross-account sharing out-of-the-box. In other words, a user can only access records related to their own account—not records from child accounts unless a custom solution is implemented. This makes Sharing Sets too limited for the hierarchical sharing model requested here.

C. Move users who need case access to a higher level in the Role Hierarchy.
While Salesforce Role Hierarchy does provide record access from child to parent in the internal user model, partner users in Experience Cloud do not behave exactly the same as internal users. Role hierarchy for partner users is more limited, and even if roles are structured hierarchically, this alone does not guarantee visibility across account relationships unless the hierarchy matches the account structure perfectly. It is a partial solution but lacks the clarity and robustness of EAH.

D. Configure an External Account Hierarchy.
This is the best and recommended solution. External Account Hierarchy is a feature designed specifically for Experience Cloud (Partner or Customer portals). It allows external users in a parent account to automatically gain access to records (such as cases) owned by users in child accounts, without manual sharing or complex customization. This fulfills the request exactly as asked—ensuring that the parent company can view cases from its child companies easily and dynamically as the hierarchy evolves.

To enable this, the administrator would:

• Define the parent-child relationship between the accounts using the External Account Hierarchy feature.

• Ensure that appropriate record types (like Cases) are enabled for hierarchical sharing.

• Confirm that partner users have appropriate community licenses (e.g., Partner Community or Partner Community Plus).

Summary: Option D stands out as the most scalable, maintainable, and purpose-built solution for the use case presented. The other options either require manual effort, don’t support cross-account visibility, or offer only partial functionality.

Correct answer: D