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

For this scenario, Salesforce Field Service should use the crew-specific scheduling behavior that ignores individual Preferred Resource scoring for active crew members. When a technician is an active member of a Service Crew, scheduling evaluates the crew as the schedulable unit rather than independently applying individual preferred-resource scoring to that member. This is an important design consideration when crew membership is used.

The Field Service resource model separates the person or workforce unit from the qualifications, territory memberships, capacity, absences, and crew relationships used by scheduling. A Service Resource can therefore be evaluated consistently by the scheduling engine without embedding workforce logic directly in Work Orders or Service Appointments.

The alternatives address different parts of the Field Service model. Capacity-based scheduling and recommended crew size are different concepts, and a resource may participate in different crews at different nonoverlapping times.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Resources — Service Crews; active Crew Members; resource preferences.

The correct configuration is a Preferred Resource preference on the Account plus the Preferred Resource Service Objective. The Account-level preference establishes an ongoing customer-technician preference that can influence future work, while the Scheduling Policy objective gives that preference weight when ranking otherwise valid candidates.

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. Making the technician Required on one appointment is a one-off hard constraint and does not create the reusable customer preference required for subsequent service calls.

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 Preferences; Preferred Resource objective; Account inheritance.

The correct configuration is automatic Price Book Entry population when consuming a Product Item under the Work Order price book. When the Work Order and the Product Item ' s Product use compatible Price Book context, the Product Consumed record can inherit or auto-populate the appropriate Price Book Entry, keeping inventory consumption aligned with service pricing.

Using the standard inventory objects keeps quantity, location, serial number, price, and service history aligned. Custom fields or improvised notes may capture text, but they do not participate in the native stock, fulfillment, consumption, and reporting processes that Field Service provides.

The alternatives address different parts of the Field Service model. Work Types do not combine consumed products across books, and Products Consumed are not added from a generic Price Book related list on the Work Order.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Products Consumed; Product Items; Price Book Entries.

The correct configuration is a Quick Action that creates a Service Appointment. The unfinished work remains part of the existing Work Order; only a new visit is required. A mobile Quick Action can create another Service Appointment against that Work Order so the follow-up can be scheduled and tracked independently.

Mobile configuration should reduce technician data entry and expose only the actions and information needed at the point of service. The strongest designs reuse the Work Order and Service Appointment data model, launch guided actions from the appropriate parent record, and keep customer-facing outputs such as signatures and Service Reports within the native Field Service workflow.

The alternatives address different parts of the Field Service model. Creating a new Work Order would fragment the original service requirement, while Visualforce, custom buttons, or macros add unnecessary customization when a standard mobile action satisfies the requirement.

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 Quick Actions; follow-up Service Appointments.

75 Contractor licenses and 25 Contractor Plus licenses is the appropriate Field Service design. The 75 field-only contractors need standard contractor capabilities for Work Orders, Assets, mobile work, and collaboration. The 25 contractors who also participate in sales and scheduling need the broader Contractor Plus capability set.

With private organization-wide defaults, Field Service can use automatic sharing, User Territories, territory public groups, and assignment relationships to expose the operational records needed by technicians and dispatchers. These sharing mechanisms are distinct from the permissions that control whether a user can configure Field Service or use a particular application capability.

The alternatives address different parts of the Field Service model. Giving Contractor Plus to all 100 users would over-license the field-only group, while basic Contractor access would not align with the expanded scheduling and sales responsibilities of the remaining 25.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Permissions and Sharing — Contractor and Contractor Plus licensing; external Field Service users.

The correct configuration is a Work Order creation action from the Entitlement. The agent has already established service eligibility through the Entitlement. Creating the Work Order from that context preserves the entitlement relationship and allows Work Order SLA and milestone processing to use the appropriate support agreement.

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 Case can also relate to a Work Order, but the decisive process point in this scenario is the validated Entitlement rather than a generic Contact or Opportunity.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Entitlements; Work Order creation; SLA context.

For this scenario, Salesforce Field Service should use Emergency scheduling. Emergency scheduling is designed to insert urgent work into an active day, identify an appropriate nearby technician, and dispatch the appointment even when normal schedules are already occupied.

Operationally, the goal is to preserve schedule integrity while minimizing manual intervention. Field Service should be allowed to use the standard scheduling engine wherever possible so that resource availability, travel, appointment constraints, priorities, and territory context remain consistent across manual and automated scheduling actions.

The alternatives address different parts of the Field Service model. Get Candidates is a general candidate-evaluation action, Appointment Booking is aimed at finding bookable slots, and Fill-In Schedule uses gaps for nonurgent work rather than interrupting the plan for an emergency.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Emergency scheduling; Dispatcher Console; urgent dispatch.

Skill Requirements, Articles, and Products Required is the appropriate Field Service design. Work Types are reusable job templates. They directly associate the skills required to perform the work, the Knowledge articles that guide technicians, and the products expected for execution.

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. Service Resources are selected later by scheduling, and Service Appointments may be generated from work using a Work Type but are not one of the three supporting objects identified by the question.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Work Types; Skill Requirements; Knowledge Articles; Products Required.

The correct configuration is adjusting the Scheduling Policy, Knowledge, and Dispatching. Reducing mean-time-to-service requires quicker and better assignment, faster technician execution, and timely release of work. Scheduling Policy adjustments can prioritize earlier service, Knowledge reduces diagnosis time, and effective dispatching gets the appointment to the technician promptly.

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. Customer Entitlements define service eligibility and SLA commitments but do not by themselves shorten the operational path from request to service completion.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Scheduling Policies; Knowledge; dispatching; service efficiency.

The requirement is best implemented with a monthly Maintenance Plan with a 12-month generation timeframe and automatic generation disabled. Frequency of one month models the twelve monthly checkups, while a 12-month generation timeframe represents the annual horizon. Because the customer calls to initiate each visit, automatic Work Order generation should remain disabled and work can be generated manually when appropriate.

The consultant should distinguish recurrence from job definition. A Work Type describes how a recurring job is performed, while the Maintenance Plan determines when and how future work is generated. Work Order and Service Appointment generation methods then determine whether Assets are consolidated into one visit or separated into multiple jobs.

The alternatives address different parts of the Field Service model. Automatically generating each month would remove the intended customer-driven control, while a one-month generation timeframe would not represent the planned annual set as efficiently.

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; Frequency; Generation Timeframe; Auto-generate Work Orders.