Explanation:

Reasoning:
Unique Identification: Each door lock has a unique 20-digit code that must be tracked individually.
Standard Field Requirements: In Salesforce Field Service, if you need to enter a specific serial number on a Product Item record, the Quantity On Hand for that record must be 1. Because each lock has its own unique 20-digit code, tracking them as separate Product Items ensures that each unique serial number is associated with a single unit of inventory.
Serialized Inventory Management: While newer "Serialized Product" objects exist for high-volume serialization, the standard practice for tracking discrete, high-value unique units (like specialized door locks) in a technician's van is to create individual Product Item records where each record represents exactly one unique physical unit.

Why other options are incorrect:

Option A & B: Storing serial numbers in a related list or notes section does not leverage the standard inventory management engine, making it difficult to "consume" a specific lock during a service appointment or maintain accurate stock levels.
Option D: Simply entering a quantity (e.g., "5") on a single Product Item record would track the locks as bulk stock, which does not allow for the tracking of individual 20-digit codes required by the business.

Explanation:

A. Salesforce browser-based application
The browser-based (desktop) application is the most robust way to view a comprehensive list of records.
Full Visibility: Technicians can navigate to the Resource Absences tab or the related list on their Service Resource record to see every absence created for them in a list view format.
Filtering and Reporting: The desktop interface allows for advanced filtering and the ability to run reports on absences, which is ideal for viewing a full year's worth of data (like the 12 mandatory holidays) at once.

B. Salesforce Field Service mobile application
The Salesforce Field Service (SFS) mobile app is specifically tailored for the mobile workforce and includes dedicated features for managing absences.
Profile Tab: In the SFS mobile app, technicians can view and manage their absences directly from the Profile tab.
Optimized Experience: This app is designed to show technicians their schedule and availability, including absences, in a way that is "offline-first" and easy to navigate while in the field.

🔴 Incorrect Answers

C. Custom mobile application
While a company could build a custom app, it is not a recommended or standard solution when Salesforce provides two highly functional native applications. Developing and maintaining a custom app adds unnecessary cost and complexity.

D. Salesforce mobile application
The standard Salesforce mobile app (formerly known as Salesforce1) is designed for general CRM tasks (leads, opportunities, cases). While it can display standard objects, it lacks the specialized Field Service interface features—like the dedicated "Profile" view for absences—found in the Field Service-specific mobile app. Salesforce documentation explicitly notes that certain Field Service features, like the resource calendar for absences, are optimized for the SFS mobile app rather than the standard one.

📖 References
Salesforce Help: Create Service Resource Absences for Field Service
Salesforce Help: Resource Absence List in the Field Service Mobile App
Salesforce Help: Field Service Mobile App Features

Explanation:

In Salesforce, a single Work Order can only be associated with one Price Book at a time. This is a fundamental data model constraint: the Price Book field on the Work Order object determines pricing for all related line items. Since the required components span two different Price Books (Preferred and U.S.), the only scalable, compliant solution is to create two separate Work Orders—one linked to each Price Book—and assign the relevant Work Order Line Items accordingly. This ensures accurate pricing, invoicing, and reporting without manual overrides or data integrity risks. For example:

Work Order 1 (Preferred Price Book) → Line Items for components A, B
Work Order 2 (U.S. Price Book) → Line Items for components C, D

While this creates two records, it maintains pricing fidelity and leverages native Salesforce functionality.

Why the Other Options Are Incorrect

A: A single Work Order cannot use multiple Price Books—even if Work Types reference different books. The Work Order’s Price Book field overrides all child line items.

B: Work Types do not control Price Book assignment; they define skills, duration, and templates—but not pricing catalogs.

C: Manually overriding prices on line items is error-prone, bypasses discount rules, and breaks auditability. It also requires user intervention, increasing processing time and risk.

Salesforce’s architecture enforces one Price Book per transactional record (Opportunity, Work Order, etc.). Option D respects this rule while meeting business needs.

Reference:
Salesforce Help – “Price Books and Work Orders”

Explanation:

A Custom Gantt Filter is the standard and most effective way to filter Service Appointments within the Dispatcher Console (the Gantt). This feature allows users to define specific criteria—such as "Status = Emergency" or "Work Type = Emergency"—and save that view.

Crucially, Gantt Filters can be kept private, shared with specific Public Groups, or shared with individual users. By creating a filter for emergency work and sharing it only with the "Dispatchers" public group, the consultant ensures that only those users see that specific view on their Gantt.

🔴 Incorrect Answers
B. Custom Lightning Component
While a custom Lightning Component could technically be built to display data, it represents significant over-engineering. Salesforce Field Service provides out-of-the-box functionality (Gantt Filters) specifically designed for this purpose. Consultants should always prioritize "Clicks not Code" to ensure easier maintenance and upgrades.
C. Custom Report in a Private Report Folder
A report is a static or semi-real-time view of data, but it is not an operational tool for dispatchers. Dispatchers need to interact with work orders (drag and drop, schedule, dispatch) in real-time. Furthermore, a "Private" report folder would only be visible to the person who created it, not a group of dispatchers, unless shared via a shared folder—but even then, it doesn't solve the need for a "view" within the Dispatcher Console.
D. Custom List View
Standard Salesforce List Views are used on the Service Appointments tab, but they do not control the visibility of appointments on the Field Service Dispatcher Console (Gantt). While a dispatcher could use a list view, the prompt implies a "view" within their primary workspace (the Gantt), where custom filters are the native mechanism for visibility.

📖 References
Salesforce Help: Filter the Service Appointment List in the Dispatcher Console
Salesforce Help: Create and Share Custom Gantt Filters
Trailhead: Manage the Dispatcher Console

Explanation:

Why These Are Correct

A. Schedule Policy with Work Rules and Service Objectives: Routing depends heavily on scheduling policies. Work Rules define constraints (skills, availability, travel), while Service Objectives define optimization goals (minimize travel, maximize utilization). Configuring these correctly is essential for accurate routing.

B. Resource Availability Work Rule: This ensures routing considers technician availability, breaks, and travel time. Without this, routing could assign appointments during unavailable times.

C. Default Travel Speed: Travel speed impacts routing calculations. If no specific travel speed is defined for a resource, the system uses the default. This ensures routing calculations remain accurate.

Why the Other Options Are Incorrect

D. Straight line with Street Level Routing: This is incorrect because Street Level Routing uses actual road networks, not straight-line distances. Straight-line routing is only used when Street Level Routing is disabled.

E. Auto Schedule True: Auto-scheduling is about automatically creating appointments, not routing configuration.

Exam Tip
Routing questions often test knowledge of Work Rules, Service Objectives, and travel speed.

📖 References
Salesforce Help: Scheduling Policies
Trailhead: Field Service Scheduling