Pass the Salesforce Field Service Lightning program FS-Con-101 Questions and answers with ExamsMirror

For this scenario, Salesforce Field Service should use separate Work Orders for separate Price Books. A Work Order uses one Price Book. Work Order Line Items under that Work Order can only select products represented by Price Book Entries in the parent Work Order ' s Price Book. If required components exist only in different Price Books, separate Work Orders preserve standard pricing behavior.

Field Service inventory distinguishes the product catalog from stock at a location and from inventory movement or consumption. Products define what the item is, Product Items represent how much of that Product is at a specific Location, Products Required describe planned needs, and Products Consumed record what was actually used during execution.

The alternatives address different parts of the Field Service model. Overriding a price cannot make an unavailable product eligible for selection, and Work Types do not provide an independent Price Book for each line item.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Work Order pricing; Price Books; Work Order Line Items.

For this scenario, Salesforce Field Service should use the standard Asset Install Date. An Asset represents the customer-installed product instance, and its standard Install Date records when that instance was installed. Reporting on this field directly answers how many products were installed during a selected period.

This distinction is important for reporting and maintenance because the organization often needs to know not merely what type of product was sold, but which serialized or installed unit changed status, location, parentage, or replacement state and which service work was performed against it.

The alternatives address different parts of the Field Service model. Field History Tracking audits changes rather than providing the primary installation date, Work Orders represent service activity, and a custom field on Products Consumed would duplicate a standard Asset capability.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Assets — Assets; Install Date; installed-base reporting.

For this scenario, Salesforce Field Service should use member-specific Operating Hours. A Service Territory Member can use Operating Hours that differ from the territory defaults. Because the member is one hour behind the territory, shifting the member ' s start and end times forward by one hour aligns effective availability without changing the entire territory.

For resource design, the consultant should model the real operational constraint at the correct layer: skills for expertise, capacity for outsourced workload, crew membership for coordinated teams, Operating Hours and absences for availability, and permission sets for user capabilities. Mixing these concepts leads to inaccurate scheduling behavior and unnecessary customization.

The alternatives address different parts of the Field Service model. Changing the territory affects every member, while changing the user time zone misrepresents the user ' s actual locale and is not the scheduling control intended for this requirement.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Resources — Service Territory Members; Operating Hours; time-zone scheduling.

the Candidates/Get Candidates action is the appropriate Field Service design. Get Candidates evaluates qualified resources and time slots under the active Scheduling Policy and exposes the relative effect of Service Objectives on the candidate options. This is the appropriate place to inspect objective scoring.

Salesforce Field Service treats the Service Appointment as the primary unit of scheduling. Scheduling Policies combine Work Rules, which determine whether a resource or time slot is valid, with Service Objectives, which score valid alternatives against business priorities. The selected configuration therefore has to operate at the scheduling layer rather than merely changing descriptive fields on the parent Work Order.

The alternatives address different parts of the Field Service model. Bulk dispatch and the general Dispatcher Console focus on operational scheduling, while Book Appointment emphasizes bookable slots rather than explaining candidate objective scores.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Get Candidates; Service Objective scores; Scheduling Policies.

The correct configuration is the correct Field Service Mobile action placement and supported action type. Actions can appear in Salesforce Mobile but not Field Service Mobile when they are not placed in the required publisher-action section or when an unsupported legacy Lightning Component action type is used. Field Service Mobile has its own supported action model.

When comparing Salesforce Mobile with Field Service Mobile, the latter should be treated as an operational field-work client rather than a generic CRM client. Its offline capabilities, appointment-centric experience, signature/report functions, geolocation controls, and technician-specific actions are the features that should drive the configuration decision.

The alternatives address different parts of the Field Service model. Mobile navigation settings do not substitute for the page-layout action configuration, and the mobile client does not automatically surface every action that appears elsewhere in Salesforce.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Mobility — Field Service Mobile actions; page layouts; supported quick-action types.

For this scenario, Salesforce Field Service should use a Resource Absence plus Fix Overlaps. Recording the sickness as a Resource Absence accurately removes the technician ' s availability. Fix Overlaps can then identify appointments that conflict with the absence and attempt to reschedule them to suitable resources under scheduling rules.

In scheduling design, it is important to distinguish eligibility from preference. Work Rules filter candidates that do not satisfy hard constraints such as territory, availability, skills, or boolean conditions, while Service Objectives rank the remaining options. Dispatcher Console actions then use that policy logic to place, move, or dispatch appointments in a controlled way.

The alternatives address different parts of the Field Service model. Changing the global policy to High Intensity does not model the absence, and manually dragging or calling customers creates avoidable administrative work before the scheduling engine is given a chance to resolve the disruption.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Resource Absence; Fix Overlaps; disruption management.

The correct configuration is a customer-specific Price Book containing all relevant products. A Work Order uses one Price Book, so the customer-specific book should contain both negotiated-price products and ordinary products that may appear on the same Work Order. This preserves standard Product selection and pricing on Work Order Line Items.

The Field Service data model separates the service requirement from its individual tasks and visits. A Work Order represents the overall job, Work Order Line Items represent component-level or task-level work, and Service Appointments represent the scheduled field visits used to execute that work. Choosing the correct level preserves accurate history, pricing, inventory, and scheduling.

The alternatives address different parts of the Field Service model. A book containing only discounted items would make other required products unavailable through the normal pricing model, and a global book would not represent customer-specific negotiated prices.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Work Order pricing; customer Price Books; Price Book Entries.

For this scenario, Salesforce Field Service should use a Maintenance Plan. Maintenance Plans are the native Field Service mechanism for recurring preventive work. They can associate Assets, Work Types, frequencies, generation timeframes, and Work Order/Service Appointment generation so service is created before predictable failures or at regular intervals.

For preventive maintenance, the objective is to create service before predictable failure while preserving accurate Asset-level history. Using the standard maintenance framework also allows recurring work to participate naturally in scheduling, inventory planning, service reporting, and SLA processes.

The alternatives address different parts of the Field Service model. Work Types describe how a job is performed but do not create a recurrence calendar; Path and custom process automation are not substitutes for the native maintenance framework.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Maintenance Plans — Maintenance Plans; recurring maintenance; Maintenance Assets.

For this scenario, Salesforce Field Service should use different Service Resource Skill Levels. The contractors differ in repair expertise, so the Repair skill should be assigned with different proficiency levels. Skill Requirements can then express the level needed for the Work Type and scheduling can distinguish their qualifications.

Salesforce favors reusable resource metadata over one-off record manipulation. When resource qualifications and availability are modeled correctly, the same information can support candidate selection, optimization, dispatching, reporting, and mobile execution without duplicating logic on individual jobs.

The alternatives address different parts of the Field Service model. Capacity represents workload volume, Preferred Resource expresses a preference rather than expertise, and excluding the less experienced contractor would unnecessarily prevent all assignment.

This keeps the workforce model reusable across scheduling, dispatching, mobile execution, and reporting and avoids encoding resource logic in individual work records.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Resources — Service Resource Skills; Skill Levels; Skill Requirements.