Certified Experience Cloud Consultant — Free Practice Questions
10 free sample questions from a bank of 115, with the correct answers and explanations. No signup required — start practising right now.
1Bloomington Caregivers (BC) wants to streamline back-end processes and workflows for its employees. BC recently learned about Lightning Bolt solutions for employees at a world tour event.
Where should BC look for potential Lightning Bolt solutions?
Salesforce Connect
Salesforce AppExchange
Salesforce Accelerator Directory
Salesforce Accelerator Catalog
Answer: B
The short version
B — AppExchange is the home for Lightning Bolt solutions. Bloomington Caregivers should search AppExchange for installable employee Bolt solutions.
Key concepts in this question
Lightning Bolt solutions: Packaged Experience Cloud assets that bundle a template plus pages, components, business logic, and sample data for a specific use case.
AppExchange marketplace: The Salesforce curated storefront where partners and Salesforce publish installable Bolt solutions, components, Lightning apps, and consulting offers with reviews and packaging.
Employee community distinction: Bolt solutions exist for customer, partner, and employee experiences,.
Accelerator confusion: Accelerator is a Salesforce services engagement model, not a storefront, so directory or catalog wording points to billable expert help rather than reusable product.
Why B is correct
Salesforce documentation defines a Lightning Bolt as a distributable Experience Cloud solution that an author shares or sells through AppExchange, and that a subscriber installs to get a turnkey site plus automation. That makes AppExchange the documented discovery and delivery channel. For BC this means faster evaluation, trial in sandbox, and reuse of proven employee workflows instead of custom development.
Why the others are wrong
A. Salesforce Connect exposes external OData data inside Salesforce and has no catalog of site templates.
C. There is no product called Salesforce Accelerator Directory for Bolt discovery, and Accelerator refers to expert-led engagements.
D. There is no product called Salesforce Accelerator Catalog that distributes Bolt solutions, so it cannot satisfy the requirement.
Certified-Experience-Cloud-Consultant exam tip
When you see Lightning Bolt plus where to find or share, choose AppExchange, and when you see Accelerator plus directory or catalog, eliminate it as a services distractor.
2Northern 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?
Manually share cases.
Create a Sharing Set for the Account.
Move users who need case access to a higher level in the Role Hierarchy.
Configure an External Account Hierarchy.
Answer: D
The short version
D — External Account Hierarchy gives the parent reseller View access to child cases. It models parent to child account relationships for external users.
Key concepts in this question
External Account Hierarchy: An Experience Cloud sharing construct that mirrors parent-child business accounts for partner and customer users and extends record visibility upward.
Partner Community case access: Cases owned by child partner accounts often must be visible to the parent distributor while remaining hidden from unrelated partners.
Sharing Sets contrast: Sharing Sets grant portal users access based on lookup to their own account or contact, but do not create a multi-level parent to child rollup.
Role Hierarchy limits: Moving external users higher in roles is coarse, affects many objects,.
Why D is correct
External Account Hierarchy is built for exactly this reseller family scenario, where a parent company oversees several child companies and needs View access to cases created below it. Once enabled and the hierarchy is defined on accounts, the parent account partner users inherit visibility to child records according to sharing configuration. The requirement says best fit, which is the declarative hierarchy feature.
Why the others are wrong
A. Manually sharing each case is operationally unsustainable and fails as new child cases arrive daily.
B. A Sharing Set links a user to records tied to their own account, but does not roll child company cases up to the parent company.
C. Moving users higher in the Role Hierarchy is blunt, hard to govern, and does not establish the account family relationship.
Certified-Experience-Cloud-Consultant exam tip
Parent sees child partner records equals External Account Hierarchy, while user sees own account records equals Sharing Set, so map the noun hierarchy to D.
3Universal Containers (UC) has a B2C customer department that uses person accounts to track and manage all B2C customers. UC has set up a B2C site using Salesforce Experience Cloud. The VP of B2C business wants to enable self-registration on the portal so customers can create their own user accounts.
What should the Experience Cloud consultant at UC recommend so that the new users self-registering on the B2C site are captured as person accounts in Salesforce?
Create a custom self-registration page and Apex handler that creates a person account for each user self-registering on the portal.
Use the standard self-registration configuration under Experience Workspace and leave the default Account field empty.
Use the standard self-registration configuration under Experience Workspace that assigns users to a default business account, and then build a trigger on Account to create person accounts for each user.
Restrict the Account record type access to Person Account record type only for the Site Guest User, so any account created is by default a person account.
Answer: B
The short version
B — Leave the default Account empty so self-registration creates a person account. With B2C person accounts, a blank Account field tells Experience Cloud to generate an individual person account.
Key concepts in this question
Person accounts: A single record that behaves as both account and contact for B2C, required when each consumer is an individual rather than part of a company.
Standard self-registration: The Experience Workspace login and registration configuration that creates user, contact, and account records without custom Apex when set correctly.
Default Account behavior: Populating a default business account forces every self-registered user under one company, which breaks B2C identity and reporting.
Guest user and handler contrast: Custom Apex handlers and triggers add maintenance and risk,.
Why B is correct
Salesforce guidance for person-account B2C sites states that leaving the default Account field empty during standard self-registration setup causes new registrants to be captured as person accounts. Options that assign a business account or add triggers create extra cleanup and data-model debt. The VP wants native B2C capture, so the blank-account standard path is the recommended design.
Why the others are wrong
A. A custom page plus Apex handler can work but adds code, testing, and upkeep when standard config already handles person accounts.
C. Assigning a default business account then converting with a trigger creates duplicate work and risks data inconsistency.
D. Restricting guest user record types does not control the self-registration account creation logic and is not the documented pattern.
Certified-Experience-Cloud-Consultant exam tip
Person account self-registration equals blank default Account, while B2B shared access equals populated default Account, so check that field first.
4Which component can be embedded into an Experience Cloud site to start conversations with customers using the channels they prefer?
Channel Menu
Service Your Way
Service Console
Chat
Answer: A
The short version
A — Embed Channel Menu to start conversations on preferred channels. It unifies chat, messaging, and voice entry behind one menu that respects customer channel choice.
Key concepts in this question
Channel Menu component: An embeddable Experience Cloud element that presents available service channels in a single launcher.
Omnichannel entry: Customers choose chat, messaging, or phone handoff rather than being forced into one modality.
Chat-only limit: Standalone Chat handles live messaging but does not orchestrate multi-channel choice.
Console contrast: Service Console is the agent workspace, not the customer-facing channel picker.
Why A is correct
Channel Menu is documented as the component that lets sites offer conversations across channels customers prefer, with a single embed that routes to chat, messaging, or other endpoints. That matches the requirement to start conversations using preferred channels. Service Your Way and Console describe other patterns or workspaces, while Chat alone is only one branch of the menu. A delivers unified discovery and handoff.
Why the others are wrong
B. Service Your Way is not the embeddable multi-channel conversation starter for Experience sites.
C. Service Console serves agents behind the scenes rather than customer channel selection.
D. Chat alone covers only one channel and misses the menu-driven choice experience.
Certified-Experience-Cloud-Consultant exam tip
Preferred channels plus embed equals Channel Menu, so choose A over single Chat.
5Cloud Kicks (CK) advises its diverse set of clients on how to use Experience Cloud. With new regulations taking effect, many of CK’s clients want an easy and cost effective way to set up a site and gather their customers’ communication preferences.
How should CK help compile these preferences?
Use the standard Preferences Chatbot to gather the preferences.
Create a Lightning Bolt solution that already includes all the preferences.
Build a Service Console to gather the preferences.
Create a Lightning Bolt solution with a template and a login flow to gather the preferences.
Answer: D
The short version
D — A Bolt solution plus template and login flow collects preferences cheaply. Cloud Kicks can launch a reusable site quickly and capture consent as part of entry, which fits new regulations without custom builds for each client.
Key concepts in this question
Lightning Bolt solution: Reusable package of template, pages, components, and logic that lets a consultancy clone a proven site across many clients.
Login flow: A guided Visual Flow invoked at login that can present preference checkboxes, store consent, and enforce completion before site access.
Communication preferences: Regulated consent data such as channel opt-ins that must be collected consistently, timestamped, and easy to update.
Cost and speed pressure: CK advises many clients, so cloning a Bolt is far cheaper than bespoke sites, Service Console builds, or chatbot-only collection.
Why D is correct
The combination is decisive because the template solves fast site creation while the login flow solves guaranteed collection at a natural checkpoint. Bolt reuse lowers build and maintenance cost across CK client base, and the flow ensures every login presents current preference options and writes them to the correct fields. The question asks for easy and cost effective setup plus compilation, which only D delivers together.
Why the others are wrong
A. A standard preferences chatbot assumes conversation entry and does not provision regulated sites across clients.
B. A Bolt that already includes all preferences is static and cannot adapt per client or capture consent at login without a flow.
C. Service Console is an agent workspace for case handling, not a customer-facing preference capture site.
Certified-Experience-Cloud-Consultant exam tip
When the stem stresses many clients plus fast plus cheap sites, think Bolt reuse, and when it stresses capture at entry, add login flow.
6Which three considerations should be made when using Criteria-Based Audiences? (Choose three.)
Components in the template header and footer sections cannot be assigned to an audience.
Up to 2,000 audiences can be created.
Domain criteria are not available in sandbox or Developer Edition orgs.
Salesforce must be contacted if you need to use the domain criteria in sandbox or Developer Edition orgs.
Record Type criteria cannot be assigned to a component.
Answer: A, C, E
The short version
ACE — Header and footer are excluded, domain criteria fail in sandbox, and record type cannot target a component. These three platform limits define what criteria-based audiences can and cannot personalize.
Key concepts in this question
Criteria-based audiences: Rule-driven segments using profile, location, domain, or record context to show pages, components, and branding sets to matching users.
Header and footer restriction: Template chrome regions are global and therefore not eligible for component-level audience assignment.
Domain criteria availability: Domain-based rules depend on custom URL and domain configuration that is not available the same way in sandbox or Developer Edition.
Record Type component limit: Record Type criteria behave differently from simpler user criteria and cannot be attached directly to an individual component.
Why ACE is correct
Salesforce considerations documentation explicitly calls out that components in header and footer cannot be audience-assigned, that domain criteria are unavailable in sandbox or Developer Edition contexts, and that Record Type criteria cannot be assigned to a component. Together these three bound a consultant design, forcing personalization into body regions, non-domain criteria in lower environments, and page-level use for record scoping. Options B and D misstate audience scale and support escalation, so only ACE matches documented limits. Exam questions test these exact exceptions.
Why the others are wrong
B. The platform does not cap audiences at 2,000 in the way described, so it is not a listed consideration.
D. Contacting Salesforce is not the documented workaround for sandbox domain criteria, and domain handling differs by environment setup.
Certified-Experience-Cloud-Consultant exam tip
Memorize the trio of no header-footer, no sandbox domain, no record-type on component, and you will spot ACE instantly.
7Northern Trail Outfitters implemented a chatbot on its Experience Cloud site.
Which three KPIs could be used to help understand the chatbot’s impact on customer service? (Choose three.)
Number of lead records created
Average Handle Time compared to Bot Session Time
Case deflection
CSAT (Customer Satisfaction score)
Case Type by Issue
Answer: B, C, D
The short version
BCD — Handle time versus bot time, deflection, and CSAT prove chatbot value. Together they show efficiency gain, workload avoided, and experience quality rather than sales or ticket mix trivia.
Key concepts in this question
Average Handle Time versus Bot Session Time: Compares human effort before and after automation to quantify time saved per conversation.
Case deflection: Measures sessions fully resolved or redirected by the bot without human handoff, directly tying the bot to fewer created cases.
CSAT: Customer satisfaction score that guards against fast but unhelpful bots by confirming the experience still delights.
Vanity versus impact metrics: Lead counts and case-type breakdowns describe other funnels and do not isolate the bot effect on service.
Why BCD is correct
A service leader needs to know whether the bot reduces work, avoids cases, and keeps customers happy, which is exactly the BCD trio. Handle-time comparison isolates efficiency, deflection quantifies avoided agent workload, and CSAT validates quality so speed does not mask frustration. Lead creation belongs to marketing, and case type by issue describes demand mix rather than bot performance. The settled trio is the standard chatbot impact dashboard for Experience Cloud service use.
Why the others are wrong
A. Lead records created measures pipeline generation, not service efficiency or bot containment.
E. Case type by issue helps workforce planning but does not show whether the chatbot itself moved the needle.
Certified-Experience-Cloud-Consultant exam tip
For chatbot KPIs pick time saved plus cases avoided plus happy customers, and reject sales or taxonomy metrics.
8Ursa Major Solar (UMS) wants to streamline back-end processes and workflows for its employees. UMS recently learned about Lightning Bolt solutions for employees at a world tour event.
Where should UMS look for potential Lightning Bolt solutions?
Salesforce Connect
Salesforce Accelerator Catalog
Salesforce Accelerator Directory
Salesforce AppExchange
Answer: D
The short version
UMS should look on Salesforce AppExchange for Lightning Bolt solutions because Bolt solutions are packaged industry templates distributed through AppExchange, not through Accelerator Catalog or Connect, so D is the only place to browse and install them.
Key concepts in this question
Lightning Bolt solutions bundle an Experience Builder template plus themes, pages, flows and apps for a specific industry use case. AppExchange is the Salesforce marketplace for apps, components, templates and Bolt solutions. Accelerator Catalog is not the distribution channel for Bolts. Salesforce Connect is an integration feature for external data, unrelated to finding templates.
Why D is correct
D is correct because Salesforce publishes Lightning Bolt Solutions as an AppExchange solution type with its own listing category. The AppExchange Bolt page describes Bolts as industry solution templates built by partners to get to market faster, containing process flows, apps and components integrated with Customer 360. The documented creation path is to export a customized site, package it and optionally upload it to AppExchange to share or sell, which proves AppExchange is the discovery point.
Why the others are wrong
A is wrong because Salesforce Connect exposes external data via OData, it does not list Bolt templates. B is wrong because there is no bankable Accelerator Catalog for Bolts, the banked answer confuses services accelerators with product distribution. C is wrong because Accelerator Directory is not a Salesforce marketplace for Bolt packages. Only AppExchange provides searchable Bolt listings, reviews, packaging and install flows that UMS needs.
Certified-Experience-Cloud-Consultant exam tip
When you see Lightning Bolt in an Experience Cloud question, immediately think AppExchange distribution. Eliminate Connect, which is always about data integration, and eliminate any Accelerator wording.
9No More Homelessness (NMH) is about to create a public site for volunteers where they will be able to sign up for volunteering opportunities at local events. Each registration will result in a record being created for a custom EventRegistration object.
Which three considerations should NMH keep in mind for records created by guest users? (Choose three.)
When possible, one should create and assign queues as owners of records created by guest users.
Queues cannot be assigned as owners of records created by guest users.
Default owner does not need Read/Write access to view the records created by guest users.
Any active user in an org can be assigned as the default owner of records created by guest users.
Setting the default owner for records created by guests is an option in Experience Cloud sites.
Answer: A, D, E
The short version
ADE — Use queues as owners when possible, any active user with access as default owner, and the site default-owner option. That trio keeps guest-created EventRegistration records owned, visible, and supported.
Key concepts in this question
Guest record ownership: Records created by guests need a stable owner because guests cannot own them directly.
Queue ownership: Assigning queues spreads follow-up across volunteers and prevents single-user bottlenecks.
Default owner rule: An active user with object access must backstop records so they remain accessible and actionable.
Site setting: Experience Cloud exposes a default-owner option that operationalizes the pattern per site.
Why ADE is correct
Best practice for guest-created custom objects is to prefer queues for pooled ownership, allow any eligible active user as default owner when queues do not fit, and configure the site-level default owner so no record goes ownerless. That covers scalability, availability, and governance for NMH volunteer signups. Claims that queues are forbidden or that owners need no access misunderstand the model. ADE captures the complete ownership design.
Why the others are wrong
B. Queues can be assigned as owners of guest-created records, so a ban claim is false.
C. The default owner does need appropriate Read-Write access to view and manage those records.
Certified-Experience-Cloud-Consultant exam tip
Guest records equals queues preferred plus default owner configured, so lock A, D, and E.
10Universal Containers (UC) maintains multiple customer-facing sites, but only one profile for all customer users. No customer has access to more than one site.
Which step should the UC system administrator take to grant customers access to the appropriate site?
Create and assign a permission set to the users and site.
Enable the Customer Identity profile or permission set.
Add user to the All Customer Portal Users public group.
Assign the profile to the site membership.
Answer: A
The short version
UC has one profile shared across many sites but each customer must see only one site, so the admin must use permission sets for site membership. Adding the shared profile to each site would grant everyone access everywhere, while distinct permission sets isolate each audience cleanly.
Key concepts in this question
Experience Cloud site membership is controlled in Administration plus Members by adding profiles or permission sets. All users with an added profile or permission set become members. Profiles are coarse and shared here, so they cannot differentiate. Permission sets allow a subset of one profile to join a specific site without cloning profiles, enforcing a membership policy per site.
Why A is correct
A is correct because creating and assigning a site-specific permission set, then adding that permission set to only the appropriate site membership, grants access to exactly the intended customers. Salesforce Help explicitly recommends permission sets for this flexibility, stating they let you grant site access to a subset of users from the same profile without cloning the profile. New users assigned the set automatically gain access, which scales across multiple customer sites.
Why the others are wrong
B is wrong because Customer Identity is not a site membership control, it relates to identity features and does not scope which site a user can open. C is wrong because All Customer Portal Users is a general group, not a per-site membership gate, and would not prevent cross-site access. D is wrong in this scenario because assigning the single shared profile to site membership would make every customer a member of that site, violating the rule that no customer accesses more than one site.
Certified-Experience-Cloud-Consultant exam tip
For one profile plus many sites questions, choose permission sets every time. Remember the pattern, one permission set per site, add each set to.