EX-Con-101 — Salesforce Certified Experience Cloud Consultant

Full question text, answer options, and explanations for this practice set — a spoiler-free alternative is the interactive quiz above for scored, shuffled practice.

1. 1. Salesforce Experience Cloud is used to build:

   • A. Internal employee dashboards only
   • B. Portals, websites, and communities for customers, partners, and employees that connect to Salesforce data(correct)
   • C. Mobile applications for Salesforce field technicians only
   • D. Integration middleware connecting Salesforce to external systems

   Explanation: Salesforce Experience Cloud (formerly Community Cloud) is a platform for creating portals, websites, help centers, and branded digital experiences for external audiences — customers, partners, employees, and any other stakeholders — that connect directly to Salesforce data. These experiences can be built with low-code tools (Experience Builder) and can leverage the full Salesforce sharing and security model.

2. 2. Which Experience Cloud template is most appropriate for building a B2B partner portal for deal registration and lead management?

   • A. Customer Account Portal template
   • B. Partner Central template(correct)
   • C. Help Center template
   • D. Build Your Own (Aura) template

   Explanation: The Partner Central template in Experience Cloud is specifically designed for partner relationship management use cases including deal registration, lead distribution and management, marketing development funds, and partner learning. The Customer Account Portal is designed for B2C self-service. Help Center is for knowledge and case deflection.

3. 3. An Experience Cloud administrator wants to customize the navigation menu in Experience Builder. Where is this configured?

   • A. Setup > Navigation Menus
   • B. Experience Builder > Navigation menu component properties(correct)
   • C. The Navigation Menu object in the CMS workspace
   • D. App Manager > Navigation Items for the Experience Cloud app

   Explanation: In Experience Builder, navigation menus are managed directly through the Navigation Menu component on the page. Administrators can add, reorder, and configure menu items (pages, URLs, objects, topic catalogs) from within the builder. There is no separate Navigation Menu setup menu for Experience Cloud.

4. 4. A Salesforce admin wants to display a list of their open Cases in an Experience Cloud customer portal so customers can track their own cases. What is the recommended component to use?

   • A. Record Detail component to show one Case at a time
   • B. Related List component showing Cases under the Customer Account
   • C. Record List component (or Case List component) filtered by the logged-in user's Cases(correct)
   • D. Custom Lightning Web Component with Apex query for Cases

   Explanation: Experience Builder includes a Record List component (and object-specific list components) that can display lists of records with configurable filters. In a customer portal, the list is automatically scoped to the logged-in user's records (cases, orders, etc.) using the community sharing model. This is the standard declarative approach without requiring custom development.

5. 5. A company wants to publish product articles and FAQs in their Experience Cloud Help Center. Which two Salesforce features power content publishing in Experience Cloud? (Choose 2)

   • A. Salesforce Knowledge articles published for the Experience Cloud audience(correct)
   • B. Salesforce CMS (Content Management System) for structured digital content(correct)
   • C. Chatter posts published to a community group
   • D. Custom Visualforce pages hosted in the community

   Explanation: Experience Cloud supports two complementary content systems: Salesforce Knowledge (for structured articles, FAQs, and how-to content with versioning and channel publishing to communities) and Salesforce CMS (for digital content like banners, images, rich text, and structured content types). Together they power the content experience in Experience Cloud sites. Chatter posts are social content, not published articles. Visualforce pages can exist in communities but are not content management tools.

6. 6. An Experience Cloud site uses Salesforce Knowledge for a help center. A content manager wants to ensure that only articles tagged with the 'Product FAQ' data category are shown to customers. How is this configured?

   • A. Filter the Knowledge Article List component by Data Category in Experience Builder(correct)
   • B. Use Data Category Visibility settings to control article exposure per audience profile
   • C. Create a custom permission set that grants access to the 'Product FAQ' category
   • D. Enable the Data Category filter in the customer's Profile settings

   Explanation: In Experience Builder, the Knowledge Article List component can be configured with a filter by Data Category, ensuring that only articles in the specified category (e.g., 'Product FAQ') are displayed to experience site visitors. Data Category Visibility is used to restrict which categories individual users can see based on their profile/role, which is a different (access control) use case.

7. 7. A company wants their Experience Cloud site to have a custom domain (e.g., portal.company.com) instead of the default Salesforce-generated URL. What must be configured?

   • A. Purchase a Salesforce-branded domain through AppExchange
   • B. Configure a custom domain in Setup > My Domain, then add a custom subdomain in Experience Cloud site settings
   • C. Set the custom domain in the Experience Cloud site's Administration > Advanced settings(correct)
   • D. Use Site.com to redirect the default URL to the custom domain

   Explanation: Custom domains for Experience Cloud sites are configured in the site's Administration > Advanced settings within Setup. The company must own the domain and configure a CNAME DNS record pointing to Salesforce. The My Domain feature sets the Salesforce org's primary subdomain (used internally), but the Experience Cloud site's own custom domain is set separately in the site's administration.

8. 8. An Experience Cloud consultant wants to use Audience-Targeting to show different page variations to different user groups. Which two conditions can be used to define an Audience? (Choose 2)

   • A. User profile (e.g., show content to users with the 'Customer Community' profile)(correct)
   • B. Geographic location (city/country) of the visitor based on IP(correct)
   • C. The user's Opportunity stage in Salesforce
   • D. Domain from which the user navigated (referring URL)

   Explanation: Experience Cloud Audience criteria include user profile/permission set attributes (role, profile, permission set) and geographic attributes (country, city based on IP address). These allow showing different components or page variations to different user segments. Opportunity stage and referring URL are not native Audience criteria in Experience Builder.

9. 9. What is the difference between a Customer Community license and a Customer Community Plus license?

   • A. Customer Community Plus supports role hierarchy and sharing rules; Customer Community does not(correct)
   • B. Customer Community allows more API calls per day than Customer Community Plus
   • C. Customer Community Plus is for external partners; Customer Community is for internal employees
   • D. Customer Community supports Apex triggers; Customer Community Plus does not

   Explanation: The key distinction between Customer Community and Customer Community Plus licenses is data sharing model support. Customer Community Plus gives external users access to the full Salesforce sharing model including Role Hierarchy and Sharing Rules, enabling more granular data visibility control. Customer Community licenses use only Account-based sharing (users see records tied to their Account). Customer Community Plus is more expensive but required for complex sharing scenarios.

10. 10. By default, when an external user is created in an Experience Cloud site, they can see records owned by members of their Account. This is an example of which sharing mechanism?

    • A. Role Hierarchy sharing
    • B. Account-based sharing (portal user sharing)(correct)
    • C. Criteria-based Sharing Rules
    • D. Owner-based Sharing Rules

    Explanation: Experience Cloud external users (Customer Community users) use Account-based sharing by default: they can see records that are related to (owned by members of) their Account or that have been explicitly shared with them. This is sometimes called 'portal user sharing' or 'high-volume portal sharing.' This differs from role hierarchy sharing, which requires Customer Community Plus licenses.

11. 11. An Experience Cloud admin needs to allow guest (unauthenticated) users to see certain publicly available Knowledge articles and submit a support case. Which two configurations are required? (Choose 2)

    • A. Enable 'Allow guest users to access public API' in Experience Cloud site settings
    • B. Set the OWD for Knowledge Articles to 'Public Read Only' so guest users can view articles(correct)
    • C. Grant the Guest User Profile access to the relevant Knowledge Article record types and Case object (Create permission)(correct)
    • D. Assign a Customer Community license to all guest users

    Explanation: For guest users to view Knowledge articles, the OWD for Knowledge must allow public read access. The Guest User Profile must have read access to the Knowledge Article Types being surfaced. For Case submission, the Guest User Profile needs Create permission on the Case object. Guest users are not assigned licenses — they access sites anonymously without Salesforce user accounts.

12. 12. A company wants certain Experience Cloud portal users (Customer Community) to be able to see all Cases under their Account, including cases created by other contacts at the same company. How is this achieved?

    • A. Set Case OWD to Public Read Only
    • B. Use Super User Access — enable the 'Portal Super User' permission on the contact's user profile(correct)
    • C. Create a Sharing Rule to share Cases with the Customer Community profile
    • D. Change the Customer Community users to Customer Community Plus licenses

    Explanation: Super User Access in Experience Cloud allows designated portal users to see all records owned by other portal users in the same Account, without giving them a Customer Community Plus license. When the 'Portal Super User' flag is enabled on a Contact's record (which flows to their user account), that user gains visibility into all portal users' records at the same Account. This is the correct mechanism for intra-company record visibility with standard Customer Community licenses.

13. 13. An Experience Cloud partner user with a Partner Community license needs to edit Opportunity records owned by other partner users at the same partner Account. What must be configured?

    • A. Enable Role Hierarchy for partner users and configure their role to have edit access above direct reports(correct)
    • B. Set Opportunity OWD to Public Read/Write
    • C. Create a Sharing Rule sharing Opportunities with the Partner Community Profile
    • D. Grant the 'Modify All' permission on Opportunities in the Partner Community Profile

    Explanation: Partner Community (External) users support a Role Hierarchy. To allow a partner user to edit Opportunities owned by peer users at the same Account, they need a higher role in the partner portal role hierarchy that gives them access up through the hierarchy. OWD of Public Read/Write would expose all partner Opportunities across all partner accounts. Sharing Rules and 'Modify All' are overly broad solutions.

14. 14. An admin needs to control which tabs and objects appear for external Experience Cloud users. Which two mechanisms control object-level access for external users? (Choose 2)

    • A. The external user's Profile, which controls CRUD permissions on objects(correct)
    • B. Permission Sets assigned to the external user to grant additional object access beyond the Profile(correct)
    • C. Experience Builder's navigation menu, which determines which tabs are visible
    • D. The Experience Cloud site's Workspaces > Preferences page

    Explanation: Object-level access for external Experience Cloud users is controlled by the same Profile + Permission Set model as internal users. The Profile sets baseline CRUD permissions; Permission Sets can grant additional access. The Experience Builder navigation menu controls which pages/tabs appear in the site UI, but it does not control underlying data access — an object hidden from navigation is still accessible if the user has object permissions and a direct URL.

15. 15. A company wants to allow its customers to log in to an Experience Cloud portal using their Facebook or Google account. Which Salesforce feature enables this?

    • A. Social Sign-On via Auth. Providers configured in Setup and enabled on the Experience Cloud login page(correct)
    • B. Salesforce Identity Connect for Active Directory
    • C. A custom Lightning component with OAuth login buttons
    • D. External Identity Provider configured via SAML for consumer social logins

    Explanation: Salesforce Auth. Providers (configured in Setup > Auth. Providers) support OAuth-based social login with providers like Facebook, Google, Twitter, LinkedIn, and others. Once configured, these social login buttons can be added to the Experience Cloud site's login page in Experience Builder. This is the native, declarative approach for consumer social sign-on. SAML is for enterprise SSO, not consumer social login.

16. 16. A company needs to auto-create Experience Cloud user accounts for new Contacts who are flagged as portal users. What is the standard way to provision external users at scale?

    • A. Manually create user records for each Contact in Setup > Users
    • B. Use the 'Enable Customer User' action on the Contact record or automate it via a Flow that calls the Site.createExternalUser() method(correct)
    • C. Import users via Data Loader into the User object with an ExternalCommunityId field
    • D. Experience Cloud creates user accounts automatically when a Contact record is created

    Explanation: External users are provisioned from Contact records using the 'Enable Customer User' (or 'Enable Partner User') button on the Contact, which converts the Contact into an Experience Cloud external user. For automation at scale, a Flow or Apex can call the Site.createExternalUser() Apex method to programmatically create the external user account when a Contact meets specific criteria. Experience Cloud does not automatically create user accounts for all new Contacts.

17. 17. A company wants employees to log in to an Experience Cloud site using their corporate Active Directory credentials. Which Salesforce feature enables this?

    • A. Auth. Provider with Facebook configuration
    • B. SAML-based Single Sign-On (SSO) with Active Directory as the Identity Provider(correct)
    • C. Named Credentials for Active Directory authentication
    • D. Salesforce Identity Connect for Experience Cloud users

    Explanation: SAML (Security Assertion Markup Language) SSO allows an enterprise Identity Provider (IdP) like Active Directory Federation Services (ADFS) or Azure AD to authenticate users, and Salesforce acts as the Service Provider (SP) consuming the SAML assertion. Experience Cloud sites support SAML SSO so employees can log in with their corporate credentials without a separate Salesforce password. Salesforce Identity Connect is for syncing AD users to Salesforce internal users, not Experience Cloud external users.

18. 18. What is the purpose of the 'Self-Registration' feature in Salesforce Experience Cloud?

    • A. It allows Salesforce admins to register themselves for Trailhead courses
    • B. It allows new visitors to an Experience Cloud site to create their own user accounts without admin involvement(correct)
    • C. It automatically registers all Contacts in Salesforce as Experience Cloud users
    • D. It allows users to register new custom objects in the Experience Cloud site

    Explanation: Self-Registration in Experience Cloud allows new external visitors to create their own portal accounts by filling in a registration form. When enabled, Salesforce creates a Contact and User record automatically based on the submitted information. Administrators can customize the self-registration Apex handler to apply business logic (e.g., link to existing Accounts, set profiles). This reduces admin overhead for provisioning high-volume consumer portals.

19. 19. A company's security policy requires that external Experience Cloud users complete MFA (multi-factor authentication) when logging in. Which two methods can be used to enforce MFA for Experience Cloud users? (Choose 2)

    • A. Enable MFA in the Experience Cloud site's login settings and have users set up Salesforce Authenticator(correct)
    • B. Configure the external Identity Provider (SAML SSO) to require MFA on the IdP side before issuing SAML assertions(correct)
    • C. Require users to answer three security questions upon every login
    • D. Set a session security level requirement using Permission Set configuration

    Explanation: MFA for Experience Cloud users can be enforced in two ways: (1) Native Salesforce MFA where users register a verification method (Salesforce Authenticator, TOTP app) and MFA is required at login, configured in the site's identity settings; (2) SAML SSO where the corporate Identity Provider handles MFA before issuing a SAML assertion to Salesforce, so MFA happens at the IdP. Security questions are not MFA. Session security levels control Apex/Visualforce access, not the MFA enrollment process.

20. 20. A company uses Salesforce Experience Cloud as an Identity Provider (IdP) to authenticate users into a third-party application. Which Salesforce feature enables this?

    • A. Salesforce as Service Provider (SP) consuming a third-party SAML assertion
    • B. Salesforce as Identity Provider (IdP) using SAML or OpenID Connect to issue identity tokens to connected apps(correct)
    • C. Auth. Providers to relay authentication from Salesforce to the third-party app
    • D. Named Credentials with OAuth to authenticate from Salesforce into the third-party app

    Explanation: Salesforce can act as a SAML Identity Provider (IdP), issuing SAML assertions to third-party applications (Service Providers) when users are already authenticated in Salesforce. Connected Apps configured in Salesforce can use SAML SSO or OpenID Connect to allow Salesforce-authenticated users to access external apps without re-authenticating. Named Credentials are for Salesforce making outbound callouts, not for Salesforce authenticating users into external apps.

21. 21. Which built-in tool in Experience Cloud allows administrators to track page views, members, searches, and popular content within a community?

    • A. Salesforce Reports and Dashboards filtering on the ExperienceId field
    • B. Community Workspaces > Analytics (formerly Insights)(correct)
    • C. Google Analytics configured as an external tracking tool
    • D. Event Monitoring logs filtered by community user IDs

    Explanation: Experience Cloud Workspaces includes an Analytics section (formerly called Insights) that provides out-of-box dashboards showing page views, member activity, search terms, popular content, and community engagement metrics. This native analytics capability does not require additional setup beyond enabling the feature. Google Analytics can also be integrated for additional web analytics but is not the built-in tool.

22. 22. An Experience Cloud admin wants to drive member engagement in a customer community. Which two features encourage participation? (Choose 2)

    • A. Gamification with Reputation levels and points for actions like posting, answering questions, and receiving likes(correct)
    • B. Automatic case closure for any case without community member response within 48 hours
    • C. Featured topics and pinned posts to surface important content in community feeds(correct)
    • D. Restricting the community to view-only access to prevent off-topic posts

    Explanation: Reputation levels and points (gamification) incentivize members to contribute by rewarding engagement with badges, titles, and points for actions like answering questions and receiving endorsements. Featured topics and pinned posts curate the community experience, making it easier for members to find relevant discussions and encouraging participation in priority topics. Restricting to view-only eliminates engagement. Auto-closing cases discourages customers from seeking help.

23. 23. A company wants to measure the 'case deflection rate' of their Experience Cloud Help Center — the percentage of customers who found answers through self-service instead of opening a Case. Which data points are used to calculate this metric?

    • A. Number of Knowledge article views vs. number of Cases created in the same period(correct)
    • B. Number of community logins vs. number of Cases escalated to Tier 2
    • C. Average Case resolution time before and after community launch
    • D. Community member satisfaction score (CSAT) survey results

    Explanation: Case deflection rate measures self-service effectiveness by comparing the volume of knowledge article views (self-service attempts) to Cases created (failed self-service, requiring human support). A high deflection rate means customers are finding answers without opening Cases. This is tracked using Experience Cloud Analytics (article views) and Salesforce Reports (Case creation volume). CSAT measures satisfaction, not deflection. Resolution time and escalation rates measure support efficiency, not deflection.

24. 24. A developer makes changes to an Experience Cloud site in a Sandbox org. How are those changes deployed to Production?

    • A. Experience Cloud site configurations are automatically synced between Sandbox and Production
    • B. Use a Change Set to deploy the ExperienceBundle metadata (site pages, components, configurations) from Sandbox to Production(correct)
    • C. Manually recreate all Experience Builder changes directly in Production
    • D. Export the site as a ZIP file and import into Production through Setup

    Explanation: Experience Cloud site configurations (pages, components, branding, navigation) are stored as ExperienceBundle metadata that can be deployed using Change Sets, Salesforce DX (sfdx force:source:deploy), or Metadata API. Using a Change Set to deploy the ExperienceBundle from Sandbox to Production is the standard configuration management approach. There is no automatic sync between environments.

25. 25. An Experience Cloud consultant is troubleshooting performance issues on a community page with slow load times. Which two approaches can improve page performance? (Choose 2)

    • A. Enable CDN (Content Delivery Network) for the Experience Cloud site to cache static assets geographically closer to users(correct)
    • B. Reduce the number of components on the page and optimize Apex queries backing data-heavy components(correct)
    • C. Increase the Experience Cloud site's session timeout to reduce re-authentication overhead
    • D. Disable HTTPS to reduce encryption overhead

    Explanation: CDN integration for Experience Cloud sites caches static assets (images, CSS, JavaScript) at edge nodes worldwide, reducing latency for users geographically distant from Salesforce data centers. Reducing components and optimizing Apex queries reduces server-side processing time and the number of SOQL queries executed per page load. Session timeout has no impact on page performance. Disabling HTTPS is a critical security vulnerability and not an option in Salesforce.