Pass the Salesforce Consultant Experience-Cloud-Consultant Questions and answers with ExamsMirror

Criteria-Based Audiences are a feature that allows you to display different content to different audiences based on criteria such as profile, location, domain, or user. However, there are some considerations when using Criteria-Based Audiences, such as:

Components in the template header and footer sections cannot be assigned to an audience. These sections are shared across all pages in your site and can’t be customized fordifferent audiences.

Salesforce must be contacted if you need to use the domain criteria in sandbox or Developer Edition orgs. Domain criteria allow you to target audiences based on the domain name they use to access your site. However, this feature is not enabled by default in sandbox or Developer Edition orgs.

Record Type criteria cannot be assigned to a component. Record Type criteria are only available for page variations and navigation menu items.

To simplify topics but keep articles that have been assigned to the topics, you need to merge similar topics in Content Management. This will allow you to combine two or more topics into one and update the articles that have been assigned to the merged topics.

Explanation: To solve these requirements, the administrator should create branding sets, audience targeting, and navigation menu targeting. Branding sets are collections of branding elements, such as colors, fonts, images, and logos, that you can apply to yourExperience Cloud site. Audience targeting is a feature that allows you to display pages and components to certain users based on their assigned audience. Navigation menu targeting is a feature that allows you to display different navigation menu items todifferent users based on their assigned audience. By using these features, the administrator can create different branded experiences for each partner, control the access to the Leads inbox component and the Leads tab, and customize the navigation menu foreach partner.

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.

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 fix the issue of Experience Cloud users not being ableto view Contacts and Accounts, you should configure sharing rules on each object to give Read Only access to Experience Cloud users.Sharing rules allow you to extend sharing access to users in public groups, roles, or territories. You can use sharing rules to grant Read Only access to Contacts and Accounts owned by internal users to Experience Cloud users.

To create a new partner user for an existing site, you need to first create a contact record for the partner user, then click “Manage External User” on the contact detail page, and then click “Enable Partner User”. This will allow you to provide user details and save the user record.

Explanation: To find out how current and popular a topic is, site users can go to the topic’s detail page. The topic’s detail page shows information such as the number of followers, the number of posts, and the last activity date of the topic. Site users can alsosee the related topics and subtopics, as well as filter the content by type or time range.

A robots.txt file is a text file that tells web crawlers which pages or files the crawler can or can’t request from your site. This is used mainly to avoid overloading your site with requests; it is not a mechanism for keeping a web page out of Google. You can create a custom robots.txt file for your Experience Cloud site to control how search engines index your site.

To make your Experience Cloud site visible to search engines, you also need to make sure that your site is public and activated. A public site allows anyone on the internet to access your site without logging in. An activated site is live and ready for visitors.

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.