Salesforce Experience-Cloud-Consultant Dumps

To prevent usability issues, CK should provision and activate CDN in those regions where traffic is high. A CDN is a network of servers that delivers cached static content from websites to users based on the geographic location of the user. By provisioning and activating CDN in high-traffic regions, CK can improve the performance and availability of their public site for their users.

Content Management in Workspaces is where UMS can create the CMS collection before configuring the CMS Collection component in Experience Builder. Content Management allows UMS to create, manage, and publish content from Salesforce to its customer portal. UMS can create a CMS collection that contains a group of news articles from a workspace and then use the CMS Collection component to display the collection on its site.

The page view limit for an Experience site depends on the orgedition and the license type of the site users. For an Unlimited org, the page view limit is 5 million per month for guest users, and unlimited for authenticated users. A page view is counted when a user requests a page that is served by the site.

To grant access to each customer, the UC admin should select a permission set and a profile for a given experience. A permission set is a collection of settings and permissions that give users access to various tools and functions in Experience Cloud. A profile is a collection of settings and permissions that determine what users can see and do in Experience Cloud. By selecting a permission set and a profile for each experience, the UC admin can control the access level of each customer user.

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.

Data Category Visibility allows you to control which Knowledge articles are visible to which users based on data categories anduser roles, permission sets, or profiles. You can assign data category visibility at different levels, such as the org-wide default, the role hierarchy, or the permission set.

Salesforce Content Delivery Network (CDN) is a feature that allows you to improve the performance of your site by caching static resources, such as images, JavaScript, and CSS files. However, changing the Salesforce CDN has some implications, such as:

Changing the Salesforce CDN impacts definitions of all Lightning Web Components used in public pages. You need to redeploy your components after changing the CDN to ensure that they work properly.

Changing the Salesforce CDN does not affect SAML SSO settings for all custom URLs in that domain. SAML SSO settings are independent of the CDN settings.

Changing the Salesforce CDN does not impact the AppExchange packages in the org that use Documents object. Documents object is not affected by the CDN settings.

Changing the Salesforce CDN does not overwrite LDS defaults. LDS defaults are not affected by the CDN settings.

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.

Three things that BC should keep in mind about unauthenticated or guest user access are A, B, and D. Unauthenticated or guest useraccess is a feature that allows users to access your Experience Cloud site without logging in or registering. Unauthenticated or guest users have limited access and visibility to data in your Salesforce org, and they have some restrictions, such as:

Guestuser external organization-wide defaults are always set to Private. This means that guest users cannot access any records that are owned by external users (such as Customer Community or Partner Community users) unless they are explicitly shared with them.

Guest user can’t access records via manual sharing. This means that guest users cannot access any records that are shared with them by using the Sharing button on the record detail page.

Guest user can’t be members of public groups or queues. This means that guest users cannot access any records that are shared with them by using public groups or queues as criteria.

Two ways the consultant should associate the articles with topics are A and D. Topics are keywords or phrases that help users find and organize content in Experience Cloud sites. To associate articles with topics, you can select the appropriate topics on the Knowledge tab within Lightning Experience, which allows you to view and edit articles in a list or Kanban view. You can also manually add one or more topics to each article within Workspaces, which allows you to create and manage articles in a collaborative environment.

To move a site from one production org to another production org that is not directly connected, UC should use Lightning BoltExport and Installation. Lightning Bolt is a feature that allows UC to export a site as a package that contains the site template, theme, pages, components, and content. UC can then install the package in another org using the AppExchange or a URL link.

This license type allows users to access standard objects, such as accounts, contacts, and cases, in a self-service site. However, it does not allow users to access custom objects, such as purchases. UC would need to use a different license type, such as Customer Community Plus, that supports custom objects.

The reason for this issue is that 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. The Record Detail component is a component that displays the fields and values of a record on your Experience Cloud site. The recordID is a unique identifier that specifies which record to display. The Record Detail component uses the recordID associated with the object for the page template, which means that it can only display one record per object per page. For example, if you have a page template for Account, you can only display one Account record on that page using the Record Detail component. To display multiple records of different objects ona page, you need to use other components, such as Related List or Record List.

Partner Super User access is a feature that allows you to grant access to records owned by other partner users who havethe same role or a role below them in the role hierarchy. You can apply Partner Super User access to three objects: Opportunities, Accounts, and Custom Objects.

The administrator should create a digital experience for agents and share the URL with employees. A digital experience is a branded online destination that allows you to connect with your customers, partners, or employees. By creating a digital experience for agents, the administrator can provide them with a portal where they can view Knowledge articles and chat live with a support agent. By sharing the URL with employees, the administrator can allow them to access the digital experience as well.

To meet the requirement of distributing leads to partners, UMS needs to take at least three steps:

Create aLead Process for Lead Distribution. A lead process is a set of stages that a lead goes through from creation to conversion. UMS can create a lead process that defines how leads are distributed to partners based on criteria such as region, industry, or product.

Create a Lead Queue for Lead Distribution. A lead queue is a list of leads that are assigned to a group of users who share the workload. UMS can create a lead queue for its partners and assign leads to the queue based on the lead process.

Configure Lead creation Leadon low Distribution inside PRM Workspace. PRM Workspace is a feature that allows UMS to manage its partner relationships, such as recruiting, onboarding, training, and co-selling. UMS can configure lead creation and distribution settings inside PRM Workspace, such as enabling partners to create their own leads, setting up lead assignment rules, and defining lead notification preferences.

Three visibility options available in Experience Cloud are Audience, None, and Default. Visibility options allowyou to control who can see a page or a component on your Experience Cloud site. Audience is an option that allows you to display a page or a component only to users who belong to a specific audience. An audience is a group of users who share common attributes, such as profile, location, or language. None is an option that allows you to hide a page or a component from all users. Default is an option that allows you to display a page or a component to all users who have access to the site.

Two reasons causing this issue are C and D. To create a partner user for their Partner Community, the Salesforce administrator needs to have two requirements met: The account record associated with the contact record must be enabled as a partner, which means that it has the Is Partner checkbox checked. This indicates that the account is part of your partner network and can access your Partner Community site. The Salesforce administrator must be marked as a delegated administrator on the partner account, which means that they have limited administrative privileges to perform certainuser management tasks on behalf of an administrator. This allows them to create partner users from contact records without having full system administrator access.

Sharingsets allow you to grant access to records that have a lookup relationship to the same account or contact that the community user has. You can use sharing sets to share opportunities with partner community users who belong to the same account as the opportunity owner.

Criteria-based sharing rules allow you to share records based on field values. You can use criteria-based sharing rules to share opportunities with partner community users who meet certain criteria, such as region, industry, or status.

To ensure the changes make it accurately to production, the administrator should create a change set, upload it to production, and deploy the change set. A change set is a collection of metadata components that can be moved from oneorg to another. The administrator can use change sets to migrate point-and-click changes, such as custom objects, fields, layouts, and settings, from the sandbox to the production org. The administrator can create a change set in the sandbox, add the components that have been changed, upload it to the production org, and deploy it in the production org.

This option allows UMS to showcase the Home page in different ways for its employees andcustomers. Page variations are different versions of a page with different layouts, components, and content. UMS can create page variations for the Home page and useaudience targeting to display different variations to different audiences based on user attributes,such as profile or user type3

Two ways that Lightning Bolt can help DF accomplish this are A and B. Lightning Bolt is a framework that allows you to create and distribute industry-specific solutions that include prebuilt themes, templates, pages, components, and business logic. By using Lightning Bolt, DF can create a solution for its flower business that includes all the features and functionality they need for their communities. They can then distribute and reuse this solution for their subsidiaries or other customers who want to set up similar communities. This can help reduce implementation time and ensure consistency and quality across different communities.

To allow site users to tag site content with custom tags or member-created topics, you need to enable two permissions for site users in Setup:

Create Topics. This permission allows users to create new topics and assign them to content, such as posts,files, or articles. Users can also edit or delete the topics they created.

Member Can Access Topics. This permission allows users to access the topic management features on the site, such as viewing, following, or unfollowing topics. Users can also see thetopics assigned to content and filter content by topics.

Build Your Own (LWR) is a template that allows you to create a high-performance site using Lightning Web Components and other web standards. This template is suitable for Insightopia to create a site for itspartners that features multiple custom components that provide insights and trends along with near real-time updates.

Site User Visibility allows users within the same site to see each other, regardless of their role or sharing group membership. This is useful forcollaboration between independent researchers and NTO staff on their research-related submissions.

To ensure that the partner users are able to register, the site administrator should enable the Contacts under the Account as partner users. This will allow the site administrator to assign a username, password, and profile to each Contact and send them a welcome email with a link to activate their account and log in to the site.

Audience targeting allows you to display different content to different audiences based on criteria such as profile, location, domain, or user. However, there are some limitations of audience targeting, such as:

You can’t assign audiences to the components in the template header and footer sections. These sections are shared across all pages in your site and can’t be customizedfor different audiences.

You can’t assign record-based criteria to a component or branding set. Record-based criteria are only available for page variations and navigation menu items.

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 withone 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.

This option allows UC to give retail store managers access to the records owned by their peers and subordinates. Super User access isa feature that grants community users access to records that are owned by users who have the same role or a role below them in the role hierarchy. Super Useraccess can be enabled for partner users or customer users with Customer Community Plus or Partner Community licenses2

The reason for this issue is that the preconfigured Insights reports need to be modified to meet GDPR requirements. Insights is a feature that allowsyou to measure and analyze the adoption and engagement of your Experience Cloud sites using preconfigured reports and dashboards. However, some of these reports may not comply with GDPR, which is a regulation that protects the privacy and data rights of individuals in the European Union. To use Insights for the Experience Cloud site for Europe, the Community manager needs to modify the preconfigured reports to meet GDPR requirements, such as anonymizing user data, obtaining user consent, and deleting user data upon request.

To update brand colors across all of its sites, UMS should use the Site Builder tool. Site Builder is a tool that allows you to edit the look and feel of your Experience Cloud sitesusing a drag-and-drop interface. You can change the theme, layout, components, and branding of your sites without coding. Site Builder also supports Lightning templates, which are responsive and modern templates for Experience Cloud sites.

This permission allows the manager to create, edit, and delete all users in the org, including internal users. This permission overrides the sharing settings and role hierarchy that normally restrictaccess to user records. To limit the manager’s access to only community users, the manager should be given the Manage External Userspermission instead2

For records created by guest users, NMH should keep in mind that queues cannot be assigned as owners, setting the default owner is an option in Experience Cloud sites, and any active user in an org can be assigned as the default owner. A queue is a location where records can be routed to await processing by a group of users. However, queues cannot be assigned as owners of records created by guest users because guest users do not have access to queues. Setting the default owner for records created by guests is an option in Experience Cloud sites that allows NMH to specify who will own the records created by guest users on their public site. Any active user in an org can be assigned as the default owner of records created by guest users, as long as they have the appropriate permissions and access to the object.

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 realtors at DR with social workers at NMH, based on criteria such as record type, field value, or ownership.

Service Your Way is a component that allows customers to choose how they want to interact with a service agent or a chatbot from a list of available channels, such as phone, chat, SMS, WhatsApp, or Facebook Messenger. Service Your Way can be added to any page in Experience Builder and configured to show different channels based on user attributes or device type.

Two statements regarding data categories that are true are A and B. Data category visibility is controlled by roles, permission sets, or profiles. Child roles cannot see more data categories than their parent role, and if the parent role’s visibility changes, the child role’s category visibility is reset to match the parent’s. Customer Portal users and partner portal users inherit data category visibility settings of the role assigned to their account (owner) managers by default, unless they have a custom profile that overrides the role settings.

ExperienceBundle is a feature that allows you toretrieve, deploy, create, update, or delete an Experience Cloud site’s metadata definition in a single API call. Some of the key features of ExperienceBundle are:

ExperienceBundle enables creating experiences across orgs. You can use ExperienceBundle tomove your site’s metadata from one org to another, such as from sandbox to production.

ExperienceBundle provides editable community metadata in a human-readable format. You can use ExperienceBundle to edit your site’s metadata in JSON or XML format, whichmakes it easier to understand and modify.

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.

When building an HR help desk app using Experience Cloud, you need to consider some points, such as:

HR user profile is not only available in Employee Cloud with Employee permission set license. HR user profile is a standard profile that can be used with any user license type that supports Experience Cloud access.

In order to protect employee privacy, the HR help desk app does not need to be created in a different org than the main org. You can use sharing settings and permissions to control who can access what data in your org.

In order to leverage organizational structure, the HR help app must be created in the main org. This will allow you to use role hierarchy and public groups to share data based on your org structure.

HR user profile is not only available in Enterprise and Performance Editions with HR permission set license. HR user profile is available in any edition that supports Experience Cloud.

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.

To ensure that customers do not receive a welcome email when the site is once again active, the administrator should disable the Send welcome email checkbox for the site. This will prevent the site from sending an email to existing members when the site is activated. The administrator can disable the Send welcome email checkbox in the Administration section of Experience Builder.

To give guest users access to a custom object, CK can use guest user organization-wide defaults (OWD). OWD are a feature that allows you to set the default level of access that guest users have to records of a custom object. You can use OWD to grant Read Only or Read/Write access to guest users for a custom object. For example, CK can use OWD to give guest users Read Only access to the VolunteeringEvent object.

External Apps is a user license type that allows users to access up to 10 custom objects per app and unlimited standard CRM objects. This license type is suitable for the researchers who need to access at least 20 custom objects for the coffee company’s solution.

To limit the fields available in the customer portal, the administrator should use Field-Level Security to remove access to the unwanted fields. Field-Level Security is a feature that allows the administrator to control the visibility and editability of fields for different profiles and permission sets. The administrator can use Field-Level Security to hide or make read-only the technical codes and internalinformation fields for the customer portal profile or permission set.

A prerequisite for creating a user that has a Partner Community license is to enable the account as a partner account. To do this, you need to have the ‘’Enable as Partner’’ action on the Account page layout. This will allow you to convert an existing account or create a new account as a partner account.

Three items that are reportable by a site administrator throughGoogle Analytics for Experience Cloud sites are B, C, and E. Google Analytics is a tool that allows you to measure and analyze the traffic and behavior of your Experience Cloud site visitors. Google Analytics can report on various items, such as:

Search Activity: This item shows how users search for content on your site, such as the number of searches, the search terms used, the number of results returned, and the click-through rate.

User Login History Option: This item shows how users log in to your site,such as the number of logins, the login methods used, the login duration, and the login frequency.

Contact Support page Activity: This item shows how users interact with your contact support page, such as the number of visits, the bounce rate, the averagetime on page, and the conversion rate.

To grant Experience Builder access to two colleagues who will be responsible for creating and managing new microsites, the system administrator should grant Publisher and Builder roles. Publisher and Builder aretwo Experience Builder roles that define what users can do on the site.Publisher is a role that allows users to add contributors, publish changes, and activate or deactivate sites. Builder is a role that allows users to create and customize sites, but not publish them.

To complete self-registration in NTO’s Experience site without creating a placeholder account, NTO needs to take two steps:

Ensure that the Accountfield is empty in the registration section. This will allow NTO to create individual customers without associating them with an account.

Contact Sales customer Support to enable Person Accounts. Person Accounts are a feature that allows NTO to store information about individual customers in a single record, instead of using separate account and contact records. NTO needs to contact Salesforce Customer Support to enable Person Accounts in its org.

To prevent authenticated external users from searching for Quote and Contract objects but not Opportunity or Asset objects, you need to remove Opportunity and Asset from the object list in the Global Search Result component property editor and the Autocomplete object list in the Search component property editor. The Global Search Result component displays the search results for all objects that match the search term. The Autocomplete object list displays the suggested objects that match the search term as you type. You can customize these components by selecting or deselecting the objects that you want to include or exclude from the search.

To decrease its call volume using an Experience site, NTO can use standard out-of-the-box functionality such as:

Create an FAQ Knowledge article. A Knowledgearticle is a document that provides information or a solution to a common issue or question. NTO can create an FAQ Knowledge article that answers the most frequently asked questions by its customers and publish it on its site.

Deploy a chatbot to address common questions. A chatbot is an automated conversational agent that can interact with customers using natural language. NTO can deploy a chatbot on its site that can answer common questions, provide information, or escalate issues to agents.

Enable Chatter Questions to encourage peer-to-self-service. Chatter Questions is a feature that allows customers to post questions on your site and get answers from other customers or experts. NTO can enable Chatter Questions on its site to encourage peer-to-self-service and reduce the need for support calls.

When selecting a template for your sites and portals, you need to keep in mind some points, such as:

Insurance Agent Portal template becomes available once Financial Services Cloud is correctly set up in an org. This templateis designed for insurance agents who need to manage their leads, opportunities, policies, claims, and referrals.

Industry-specific templates as well as Lightning Bolt solutions are available today. Templates are preconfigured site designs that include pages, components, and settings. Lightning Bolt solutions are industry-specific solutions that include templates, themes, flows, apps, and components.

This option allows UMS to approve the first post of any new member who has joined within 7 days or less. UMS can create a moderation rule that applies to posts and comments, and specify the member criteria as “Joined Date is within last 7 days”. UMS can alsochoose the action as “Require Approval” and assign a moderator group to review and approve the posts.

The step that denotes the completion of anExperience Cloud site setup is activating the site. Activating the site is the final step that makes your Experience Cloud site live and accessible to your users and visitors. Before activating the site, you need to complete other steps such as creating pages, adding components, configuring settings, assigning permissions, and testing functionality. After activating the site, you can still make changes and updates as needed.

To troubleshoot the problem of the site taking a long time to load, the system administrator should use Salesforce Community Page Optimizer. This is a tool that analyzes the performance of an Experience Cloud site and provides recommendations for improving the page load time. The tool checks for issues such as component density, image size, caching settings, and network latency.

UC should create two separate digital experiences for its different customer segments and employees. This will allow UC to provide different features, content, and branding for each experience, as well as control the access and visibility of records. For example, UC can create a customer service site for B2C customers and employees, where they can view and create cases, access knowledge articles, and chat with agents. UC can also create a partner portal for B2B customers and employees, where they can view and update billing information, access contracts, and work on low-severity B2C customer issues.