Experience-Cloud-Consultant Salesforce Certified Experience Cloud Consultant (EX-Con-101) Free Practice Exam Questions (2025 Updated)

To create a do-it-yourself site for its existing and prospective customers, UC should focus on two Experience Cloud features:

Guest user and public access settings. These settings allow you to control what unauthenticated users can see and do on your site, such as viewing articles, manuals, and FAQs, or asking and answering questions.

Content Delivery Network. This is a feature that allows you to improve the performance of your site by caching static resources, such as images, JavaScript, and CSS files. This can enhance the user experience and reduce the load on your server.

This template allows CK to use out-of-the-box components that dynamically update the CMS content on its Experience Cloud site. Build Your Own (LWR) is a template that uses Lightning Web Components (LWC) to create fast and responsive pages. It also supports Salesforce CMS Connect, which allows CK to display CMS content from any CMS source on its site.

To implement thenew style guide and unify branding across all of its Experience sites, UC should create a custom theme and apply it to all sites. A theme is a collection of branding assets and style settings that define the look and feel of your site. You can create a custom theme that matches your style guide and apply it to multiple sites using the Theme Management feature in Experience Builder.

One thing that NTO should consider when building the HR help desk app is that the app can centralize knowledge and self service in to one experience site. This means that NTO can use Experience Cloud to create a site that provides access to Knowledge articles, Cases, Chatter, and other features that can help its employees find answers, request assistance, and collaborate with HR staff. NTO can use Employee Cloud, which is a solution that allows NTO to create employee experience sites using Experience Cloud.

To make an external user an Experience Site Moderator, two of the several moderation permissions available to assign are Access Experience Management and Manage Experiences. Access Experience Management allows an external user to access Experience Workspaces and Builder from an ExperienceCloud site. Manage Experiences allows an external user to create, edit, and delete experiences, as well as manage settings and content for existing experiences.

To share records with partners who will work on low-severity B2C customer issues, DR should use sharing rules. Sharing rules allow you to extend sharing access to users in public groups, roles, or territories. You can use sharing rules to share records owned by internal users with partners based on criteria such as record type, field value, or ownership.

Page variations allow you to create different versions of a page for different audiences. You can use the flexible page layout to customize the components and layout of each page variation. You can also target each page variation to a specific audience based on criteria such as location, profile, or record type.

Financial Services Community permission set license is a license type that allows users to accessFinancial Services Cloud objects and features, such as policies, claims, referrals, and goals. Insurance Agent Portal Lightning template is a template that is designed for insurance agents who need to manage their leads, opportunities, policies, claims, and referrals. These two features are available for DR to implement a solution involving insurance agent persona.

To enable the installers to collaborate with their co-workers and UMS staff, UMS needs to enable Portal User Visibility. This is a user visibility setting that allows portal users to see other portal users who have thesame role or a role below them in the role hierarchy. This also allows portal users tosee internal users who are above them in the role hierarchy. Portal User Visibility can be enabled in the Sharing Settings page in Setup.

To meet the requirements for both personas, GCC should create a portal for external researchers and give internal staff access to the main org. This will allow GCC to provide different features and permissions for each persona, as well as enable collaboration between them in a private Chatter group. For example, GCC can create a portal for external researchers using the Partner Central template, where they can view and update financial data,access reports and dashboards, and join Chatter groups. GCC can also give internal staff access to the main org using standard user licenses, where they can manage portfolio data, create workflows and processes, and join Chatter groups.

The requirement when creating portal users through Just-In-Time (JIT) provisioning is A. JIT provisioning is a feature that allows you to create portal users on demand when they log in using an external identity provider, such as Facebook or Google. To use JIT provisioning, you need to have a FederationIdentifier field on the user object, which is a unique identifier that links the portal user with the external identity provider. The FederationIdentifier field must matchthe value of the NameID element in the SAML assertion sent by the identity provider.

UMS can accomplish three goals with Experience Cloud moderation functionality:

Track Flagging and moderation activity within the Experience site. Moderation functionality allows UMS to view reports and dashboards that show theflagging and moderation activity on its site, such as the number of flagged items, the number of moderated items, and the flagging reasons.

Allow members to flag posts comments files, and messages that are inappropriate or spam. Moderation functionality allows UMS to enable members to flag content that violates the site’s guidelines or policies. Members can choose a flagging reason from a predefined list or enter their own reason.

Designer specific users as moderators so that they can closely monitor the size. Moderation functionality allows UMS to assign specific users as moderators who have permission to manage content on its site. Moderators can review flagged items, delete or edit inappropriate content, ban or warn abusive users, or escalate issues to administrators.

Two reasons for the import failure are A andD. To import Customer Portal users to the Experience Cloud, you need to have a portal role record and a contact record for each user. A portal role record is a record that defines the role of a portal user in the portal hierarchy. A contact record is a record that contains the personal information of a portal user, such as name, email, phone, etc. If these records are missing, the import will fail.

Customer Community Plus licenses have a limit of 2 million users per org, which could be a potential issue for UC if they have a large global customer base that exceeds this limit. The other options are not limitations of the Customer Servicetemplate or the Customer Community Plus license.

The Customer Account Portal template is designed for creating a site for existing customers who need to access their account information, such ascontracts, billing, and support. The template includes features such as login, registration, profile management, case management, and commerce integration. The template also supports Knowledge articles, manuals, and FAQs.

To set up Lead Sharing or Lead Distribution for partners, two steps are to enable “Allow External Lead Sharing” in Digital Experience settings and create Assignment Rules for Lead Distribution. Enabling “Allow External Lead Sharing” allows partners to access leads that are shared with them through sharing rules or manual sharing. Creating Assignment Rules for Lead Distribution allows leads to be automatically assigned to queues or users based on criteria that you define.

Reputation is a feature that allows you to reward community members for their contributions and engagement. When you enable reputation for your community, some things happen automatically, such as:

Inactive and active members are assigned default reputation points. Inactive members get zero points, while active members get 10 points.

Default point system and set of reputation levels become available. You can use the default point system or customize it to suit your needs. You can also use the default reputation levels or create your own.

Partner lead routing allows UMS to assign leads to partners based on predefined criteria, such as location, product, or industry. This helps UMS distribute leads more efficiently andincrease partner engagement. Automated quoting capabilities allow partners to generate quotes for customers using UMS’s pricing and discount rules. This helps partners close deals faster and more accurately.

When you package your Experience Cloud site, some components and settings are included as dependencies,while others are not. For example:

Custom list views for custom objects are not included as dependencies. You need to manually add them to your package or recreate them in the target org.

Custom list views for standard objects are not included as dependencies. You need to manually add them to your package or recreate them in the target org.