Free Salesforce Experience-Cloud-Consultant Practice Exam with Questions & Answers | Set: 3

The order in which the community manager should perform activation steps is A. To activate a site in Experience Cloud, you need to complete several steps, such as adding profiles and permission sets, enabling contacts as community users, setting welcome emails, and setting the site to active. The order of these steps is important, because some steps depend on others. For example, you need to add profiles and permission sets before you can enable contacts as community users, and you need to set welcome emails before you can set the site to active.

Explanation: This option allows UC to control the access to the partner application form and ensure that only qualified partners can apply. Token-based referral links are unique and expire after a certain time, which adds an extra layer of security. Creating an app for the internal team also allows UC to track the performance of the referral program and reward the existing partners accordingly1

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.

To optimize the public knowledge base, a consultant should recommend to bulk-import the top performing articles to Salesforce and select the public knowledge base channel. This will allow NTO to import only the most relevant and useful articles from the external system and make them available to public users on its site. The public knowledge base channel is a feature that allows NTO to share articles with unauthenticated users on its site.

This functionality allows UMS to create a case from aquestion that has not received a response or has received an unsatisfactory response. UMS can enable this functionality from Experience Builder settings and specify the criteria for escalating a question, such as the number of days without a reply or the number of downvotes. UMS can also assign a queue or an owner for the escalated cases and notify them by email.

To limit the fields available in the customer portal, the administrator should use Field-Level Security to remove access to the unwanted fields. Field-LevelSecurity 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 internal information fields for the customer portal profile or permission set.

To capture information upfront on the Experience site, the administrator should create a pre-chat form to fill out before initiating Chat. A pre-chat form is a form that appears before a chat session starts and asks customers to provide some information, such as their name, email, phone number, or issue description. This helps agents to identify the customer and prepare for the chat session.

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 capture the new users self-registering on the B2C site as person accounts in Salesforce, UC should create a custom self-registration page and Apex handler that creates a person account for each user. A custom self-registration page allows UC to customize the look and feel, fields, and logic of the self-registration process. An Apex handler is a class that implements the Auth.RegistrationHandler interface and defines the logic for creating a user and an account. UC can use an Apex handler to create a person account for each user based on the information they provide on the self-registration page.

To add a background image to arecord list of products in its digital experience, an administrator should build a custom Lightning component. A Lightning component is a reusable unit of user interface that you can create and customize using code. A custom Lightning component allows youto add your own functionality and design to your Experience Cloud site. To add a background image to a record list of products, an administrator should build a custom Lightning component that uses the SLDS Background Image utility class and the lightning-record-list base component.