Option C is correct because when Mobile Apply is enabled for Career Site Builder, the application template is consolidated onto a single page for candidates to complete. The application template contains the fields and questions that the candidates need to fill out when applying for a job. The Mobile Apply feature simplifies the application process by reducing the number of pages and clicks that the candidates have to go through on their mobile devices1.
Option D is correct because when Mobile Apply is enabled for Career Site Builder, the candidate profile template is consolidated onto a single page for candidates to complete. The candidate profile template contains the fields and questions that the candidates need to fill out when creating or updating their profile on the career site. The Mobile Apply feature also simplifies the profile creation and update process by reducing the number of pages and clicks that the candidates have to go through on their mobile devices1.
Option A is incorrect because when Mobile Apply is enabled for Career Site Builder, the people profile templates are not consolidated onto a single page for candidates to complete. The people profile templates are used to define the fields and sections that appear on the people profile page in the SAP SuccessFactors platform. The people profile page is not part of the career site or the Mobile Apply feature2.
Option B is incorrect because when Mobile Apply is enabled for Career Site Builder, the offer approval template is not consolidated onto a single page for candidates to complete. The offer approval template is used to define the fields and sections that appear on the offer approval page in the SAP SuccessFactors platform. The offer approval page is not part of the career site or the Mobile Apply feature3.
Reference:
1: SAP Certified Application Associate – SAP SuccessFactors Recruiting: Candidate Experience 1H/2023 | SAP Training Certification
2: Get certified in SAP SuccessFactors Recruiting: Candidate Experience 1H/2023 | SAP Learning
3: HR832 – SAP SuccessFactors Recruiting: Candidate Experience Administration | SAP Training
4: People Profile | SAP Help Portal
5: Offer Approval | SAP Help Portal

Fields defined on the job requisition and mapped to Career Site Builder can be used for the following purposes:
Display on search results: Customers can configure which fields they want to show on the search results page, such as job title, location, job category, etc. This helps candidates to quickly scan and filter the available jobs based on their preferences and criteria.
Add to data capture forms: Customers can add fields to the data capture forms that candidates fill out when they apply for a job or join a talent pool. This allows customers to collect relevant information from candidates, such as contact details, resume, cover letter, etc.
Display on the job layout: Customers can customize the layout and content of the job details page, where candidates can view the full description and requirements of a job. Customers can choose which fields they want to display on the job layout, such as job summary, responsibilities, qualifications, benefits, etc.

A multi-location job posting in CSB allows you to post a job that can be filled in more than one location. To enable this feature, you need to do the following:
Configure the standard Location Foundation Object field on the job requisition template and make it multi-selectable. This field will store the list of locations where the job can be filled.
Enable the Google Map integration in CSB and configure the map settings. The Google Map on the CSB site will show all the locations where the job can be filled based on the values in the Location Foundation Object field.
Configure the standard Location field in CSB to display the primary location value only. The primary location value is the first value in the Location Foundation Object field. The street address is not displayed in this field.
Optionally, you can also configure a custom field to display the full list of locations where the job can be filled.
Reference:
SAP SuccessFactors Recruiting: Candidate Experience Administration, Unit 5: Job Delivery, Lesson: Multi-Location Job Posting SAP Certified Application Associate – SAP SuccessFactors Recruiting: Candidate Experience 2H/2023, Topic Area: Job Delivery <= 10%

Marketing brands and talent pool status sets are two of the Recruiting features that use generic objects. Generic objects are custom objects that can be created and configured in the Metadata Framework (MDF) to extend the functionality and the flexibility of the SAP SuccessFactors solutions. Generic objects can have their own fields, associations, rules, validations, and UI configurations. Some of the benefits of using generic objects are:
They can be easily created and maintained by the administrators without coding or provisioning.
They can be integrated with other SAP SuccessFactors modules and features, such as Role-Based Permissions, Reporting, and Intelligent Services.
They can be updated and deployed without affecting the system performance or availability.
Marketing brands and talent pool status sets are examples of generic objects that are used in the Recruiting module to enhance the candidate experience and the recruiter efficiency. Marketing brands are generic objects that define the branding and the messaging of the customer’s organization to attract and engage the candidates. Marketing brands can have different attributes, such as the brand name, the brand logo, the brand description, the brand color, the brand font, and the brand email signature. Marketing brands can be associated with other generic objects, such as job requisitions, email campaigns, and landing pages, to create a consistent and personalized candidate experience. Talent pool status sets are generic objects that define the stages and the actions of the candidate relationship management (CRM) process. Talent pool status sets can have different attributes, such as the status set name, the status set description, the status set type, and the status set values. Talent pool status sets can be associated with other generic objects, such as talent pools, talent pool candidates, and email templates, to manage and track the candidate pipeline and the communication.
The other two options are incorrect because:
Recruiting teams are not generic objects, but rather standard objects that are predefined and configured in the Recruiting Management system. Recruiting teams are objects that define the roles and the responsibilities of the users who are involved in the recruiting process, such as the hiring manager, the recruiter, the interviewer, and the coordinator. Recruiting teams can be associated with other standard objects, such as job requisitions, job applications, and offer approvals, to assign and control the access and the actions of the users.
Activity tracking is not a generic object, but rather a standard feature that is enabled and configured in the Provisioning system. Activity tracking is a feature that records and displays the activities and the interactions of the candidates and the recruiters throughout the recruiting process, such as the candidate views, the candidate applies, the recruiter emails, and the recruiter notes. Activity tracking can be integrated with other standard features, such as Reporting, Intelligent Services, and Email Notifications, to analyze and improve the candidate experience and the recruiter efficiency.
Reference:
SAP SuccessFactors Recruiting: Candidate Experience 2H/2023
SAP Certified Application Associate – SAP SuccessFactors Recruiting: Candidate Experience 2H/2023
[THR84 – SAP SuccessFactors Recruiting: Candidate Experience Academy]
[THR84 – Unit 3: Candidate Relationship Management]
[THR84 – Unit 4: Career Site Builder Global Settings and Global Styles]

You can create links to hard-to-fill jobs on the Home page by using the following methods:
Within the Featured Jobs component: This component allows you to display a list of jobs that you want to highlight on the Home page. You can select the jobs manually or use rules to filter them based on criteria such as location, function, or industry1. This way, you can showcase the hard-to-fill jobs to the candidates and encourage them to apply.
Within the Top Job Searches link in the footer: This link allows you to display a list of popular or trending job searches on the Home page. You can configure the link to show the top job searches based on the number of clicks, views, or applications2. This way, you can attract the candidates to the hard-to-fill jobs that are in high demand.
Reference:
SAP SuccessFactors Recruiting: Candidate Experience Administration, Unit 4: Career Site Builder Pages and Components, Lesson: Creating and Configuring Components, Slide 13 SAP SuccessFactors Recruiting: Candidate Experience Academy, Unit 4: Career Site Builder Pages and Components, Lesson: Creating and Configuring Components, Slide 14 SAP SuccessFactors Recruiting: Candidate Experience 2H/2023, Topic Areas: Career Site Builder Pages and Components <= 10%

Recruiter Sync is a process that synchronizes the user data from SAP SuccessFactors Recruiting Management to Career Site Builder. If users do not appear in Career Site Builder after running Recruiter Sync, you can troubleshoot this issue by checking the following:
Check the Export Automated Process Logs from Command Center. This will show you the status and details of the Recruiter Sync process, such as the start time, end time, number of records processed, and any errors or warnings. You can also download the log file for further analysis.
Check that each user has a unique email address. This is a requirement for Recruiter Sync to work properly. If there are duplicate email addresses in the user data, the process will fail and the users will not be synced to Career Site Builder. You can use the User Data File report from Command Center to identify and resolve any duplicate email addresses. Reference: SAP SuccessFactors Recruiting: Candidate Experience Administration, Unit 1: Candidate Experience Overview and Project Kickoff, Lesson: Recruiter Sync, Slide 5-6.

In Command Center, the following filters are available when you search for a site:
Career Site URL: This filter allows you to search for a site by its URL, which is the web address that candidates use to access the site1.
Recruiting Management Data Center: This filter allows you to search for a site by its data center, which is the physical location where the site’s data is stored and processed2.
Recruiting Management Company ID: This filter allows you to search for a site by its company ID, which is the unique identifier that SAP assigns to each customer instance3.
The other options are not valid filters for searching for a site in Command Center:
Single Sign-On Security Key: This is not a filter, but a setting that enables single sign-on (SSO) for a site, which is a feature that allows candidates to log in to the site using their existing credentials from another system4.
Manage API Credentials: This is not a filter, but a setting that allows you to manage the API credentials for a site, which are the keys that enable the site to communicate with external systems using application programming interfaces (APIs).

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.

To consolidate qualified candidates who were not hired for critical positions in a central location, you can use the following features:
Talent pools: These are groups of candidates that share common characteristics, such as skills, interests, or qualifications. You can create talent pools and add qualified candidates who were not hired to the appropriate talent pools, to maintain a relationship with them and engage them for future opportunities. You can also use the Candidate Relationship Management feature to send targeted email campaigns, invitations, or surveys to the candidates in your talent pools.
Talent Pipeline: This is a feature that allows you to track the progress of candidates through different stages of the recruiting process, such as sourced, contacted, screened, interviewed, or offered. You can create a specific applicant status on the Talent Pipeline, such as “Silver Medalist” or “Backup”, and move qualified candidates who were not hired there, to keep them visible and accessible for the recruiters. You can also use the Talent Pipeline to view the candidate profile, history, and notes, and to perform actions such as sending emails, scheduling interviews, or changing statuses.
Creating a Content page on the career site or a field on the application view of the Candidate Workbench are not recommended ways to consolidate qualified candidates who were not hired. A Content page on the career site is a page that displays custom content, such as company culture, benefits, testimonials, or events. It is not a suitable place to store or manage candidate data, as it is public and not integrated with the Recruiting Management module. A field on the application view of the Candidate Workbench is a field that displays additional information about the candidate, such as resume, cover letter, or ratings. It is not a convenient way to group or filter candidates, as it is not searchable or sortable, and it does not allow bulk actions or communications. Reference:
SAP SuccessFactors Recruiting: Candidate Experience 2H/2023
SAP SuccessFactors Recruiting: Candidate Experience Academy
HR832 – SAP SuccessFactors Recruiting: Candidate Experience Administration HR840 – SAP SuccessFactors Recruiting: Recruiter Experience Administration

If a candidate tries to access a branded page that has not been built, the system will automatically redirect them to the page for the default brand. This is because the default brand is used as a fallback option when a specific brand is not available or configured. The default brand should have all the pages that are required for the candidate experience, such as the home page, the job search page, the job details page, etc. Reference: SAP SuccessFactors Recruiting: Candidate Experience Administration, Unit 4: Career Site Builder Global Settings and Global Styles, Lesson: Configuring Brands, Slide 9.

The Cookie Consent Manager is a feature that allows candidates to view and modify their cookie preferences on the Career Site Builder site. The Cookie Consent Manager can be accessed by clicking on a link in the header or footer of the site, which the consultant must configure in the Career Site Builder settings. The link can be customized with different text, icon, and style options. Once the candidate clicks on the link, they can see the list of cookies that are used on the site, and choose to enable or disable them based on their preferences. The candidate can also view the cookie policy and the privacy statement from the Cookie Consent Manager. The candidate’s cookie preferences are stored in their browser and applied on subsequent visits to the site, unless they clear their browser cache or change their preferences again. Reference:
https://training.sap.com/course/hr832-sap-successfactors-recruiting-candidate-experience-administration-classroom-094-g-en/
https://learning.sap.com/learning-journeys/configure-sap-successfactors-recruiting-recruiter-experience

A standard Recruiting statement of work (SOW) is a document that defines the scope, deliverables, and timeline of a Recruiting implementation project. It also specifies the roles and responsibilities of the project team, the assumptions and dependencies, and the acceptance criteria. According to the Recruiting Implementation Handbook, a standard Recruiting SOW includes the following tasks:
Enable Mobile Apply: This task involves enabling the Mobile Apply feature, which allows candidates to apply for jobs using their mobile devices. The Mobile Apply feature supports various application methods, such as uploading a resume, using a LinkedIn profile, or filling out an application form.
Configure one job layout: This task involves configuring the appearance and content of the job posting page, which displays the details of a job requisition. The job layout can be customized using Career Site Builder, which provides various components and widgets to enhance the job posting page.
Configure one standard XML feed: This task involves configuring the XML feed, which is a file that contains the data of the job requisitions. The XML feed can be used to post jobs to external job boards, such as Indeed or Monster, or to internal career sites.
The following tasks are not included in a standard Recruiting SOW:
Enable LinkedIn integration: This task involves enabling the LinkedIn integration, which allows candidates to use their LinkedIn profile to apply for jobs, and recruiters to source candidates from LinkedIn. The LinkedIn integration requires additional configuration and licensing, and is considered as an optional or custom task.
Configure 20 Category or Content pages: This task involves configuring the Category or Content pages, which are the pages that display the information or content related to the career site, such as the company culture, benefits, or events. The Category or Content pages can be created and managed using Career Site Builder, which provides various components and widgets to enhance the pages. However, the standard Recruiting SOW only includes the configuration of up to 10 Category or Content pages, not 20.
Reference:
Recruiting Implementation Handbook: This document provides an overview of the Recruiting implementation process, including the project phases, tasks, deliverables, and best practices. It also provides the sample SOWs for standard and custom Recruiting projects.

Select images that have a strong focal point. This helps to capture the attention of the visitors and convey the message of the site. Images with a strong focal point also look better on different devices and screen sizes1.
Do NOT use embedded text on images. Embedded text is the text that is part of the image file, not the HTML code. Embedded text is not accessible to screen readers, search engines, or translation tools. It also reduces the quality and clarity of the image, especially on high-resolution screens2.
Unique alt text should be populated for all images in all languages. Alt text is the text that describes the content and function of an image, and it is displayed when the image cannot be loaded or is accessed by screen readers. Alt text helps to improve the accessibility, SEO, and user experience of the site. It should be unique for each image and language, and it should be concise and relevant3.
Reference:
1: SAP SuccessFactors Recruiting: Candidate Experience Administration, Unit 4: Career Site Design and Accessibility, Lesson: Image Best Practices
2: SAP SuccessFactors Recruiting: Candidate Experience Administration, Unit 4: Career Site Design and Accessibility, Lesson: Image Best Practices
3: SAP SuccessFactors Recruiting: Candidate Experience Administration, Unit 4: Career Site Design and Accessibility, Lesson: Image Best Practices

According to the SAP SuccessFactors Recruiting: Candidate Experience Administration course1, the actions you need to take to facilitate reporting on which candidates arrived at the CSB site from the corporate site are:
Deliver source-coded backlinks so that your customer can replace all links from their externally-hosted sites to their CSB site. This means that you need to add a source parameter to the URL of each link that points to the CSB site, such as ?source=corporate. This will allow the CSB site to track the source of the traffic and report it in the Advanced Analytics dashboard1.
Submit the Referral Engine Task support ticket after moving your customer’s CSB site to production. This is a mandatory step that enables the Referral Engine feature, which is a tool that allows you to create and manage referral campaigns for your CSB site. The Referral Engine also provides reporting on the referral sources and conversions of the candidates who applied through the CSB site1.
Adding a campaign code to all XML job feeds that you create for your customer is not an action you need to take to facilitate reporting on which candidates arrived at the CSB site from the corporate site. This is because the campaign code is used to track the performance of the job postings on external platforms, such as job boards or social media, and not on the corporate site. The campaign code is also optional and not required for the XML job feeds to work23.
Recommending that your customer opt-in for the Organic Network is not an action you need to take to facilitate reporting on which candidates arrived at the CSB site from the corporate site. This is because the Organic Network is a feature that allows your customer to leverage the existing traffic on their CSB site to promote their jobs to other relevant candidates, and not to track the traffic from their corporate site. The Organic Network is also optional and not required for the CSB site to function4.