Based on the web search results, some of the responsibilities of a functional consultant on a CSB implementation are:
Work with the customer to develop a job distribution strategy. This involves understanding the customer's business goals, target audience, and recruitment channels, and helping them to optimize their job postings and campaigns across various platforms, such as job boards, social media, and search engines12.
Ensure that the job data supports the customer's recruiting strategy. This involves analyzing the job requisitions, job descriptions, and job classifications, and ensuring that they are consistent, accurate, and compliant with the customer's requirements and standards. It also involves configuring the CSB site to display the job data in a user-friendly and accessible way, using features such as search filters, job alerts, and job recommendations3 .
Upsell additional solutions to the customer is not a responsibility of a functional consultant on a CSB implementation. This is more likely to be a role of a sales or account manager, who would identify the customer's needs and offer them additional products or services that could enhance their experience or solve their problems.
Build the customer's CSB site using custom plugins is not a responsibility of a functional consultant on a CSB implementation. This is more likely to be a role of a technical consultant or a developer, who would create and implement custom code or plugins to extend the functionality or appearance of the CSB site, according to the customer's specifications or requests.

The search component allows customers to configure picklist searches that can be used as filters by candidates. The picklist search is dynamically populated with values from the career site's active jobs, which means that only relevant values will be displayed. The picklist search gives customers access to 18 fields that they can add as search filters, such as job category, location, job level, etc. The picklist search does not support the use of foundation/generic objects, which means that customers cannot use custom fields or objects as filters. The picklist search is not automatically populated with all picklist values configured in Picklist Center, which means that customers have to map the picklist values to the corresponding fields in the job requisition template. Reference: Career Site Builder Pages and Components, Career Site Builder Global Settings and Global Styles, HR832 - SAP SuccessFactors Recruiting: Candidate Experience Administration

A standard XML feed is a predefined format of job data that can be used to distribute jobs to external job boards or aggregators. The following are associated with a standard XML feed:
One standard XML feed is included in the statement of work for a standard recruiting implementation. This means that the customer can request one standard XML feed as part of the implementation project, without any additional cost or effort. The standard XML feed will include the default fields and attributes that are supported by Career Site Builder.
The leading practice is to push the delivery of XML feeds using the FTP Scheduler in Command Center. This means that the customer can configure the frequency and timing of the XML feed delivery, and use the FTP Scheduler tool to automate the process of sending the XML feed file to the destination server. This ensures that the job data is updated regularly and consistently across the external sources. Reference: SAP SuccessFactors Recruiting: Candidate Experience Administration, Unit 5: Job Delivery, Lesson: Job Delivery, Slide 13-14.

In SAP SuccessFactors Recruiting: Candidate Experience, when an accessibility checker identifies Redundant Title Text alerts, it indicates that the title attribute text is identical to the link or alternative text. This redundancy can be corrected by renaming the link using different texts for the Title and Text fields to ensure that they are not identical, enhancing website accessibility. Reference: SAP SuccessFactors Recruiting: Candidate Experience documents available at SAP Training)

Some leading practices to create locales in Career Site Builder are:
If the customer requires only one language and it is NOT en_US, you can change the default locale. This will save you time and effort as you do not need to create a new locale and duplicate the pages and components. You can simply edit the default locale and change the language and other settings as needed1.
Follow the same layout for the localized pages as the default locale. This will ensure consistency and usability across different languages and regions. You can use the same page templates and components for the locales, and only change the text and images as required2.
The other options are not leading practices for creating locales in Career Site Builder:
Using Google Translate to translate text for locales is not recommended as it may result in inaccurate or inappropriate translations. You should use a professional translation service or a native speaker to ensure the quality and accuracy of the text3.
Creating the Home page for the locale instead of duplicating it from the default locale is not a leading practice as it will create extra work and maintenance. You can use the Duplicate Page feature to copy the Home page from the default locale and then edit the text and images as needed for the locale4.