Free Salesforce FS-Con-101 Practice Exam with Questions & Answers | Set: 3

The correct configuration is Territory Timezone in the Dispatcher Console. Displaying the Gantt in Territory Timezone lets dispatchers interpret appointments according to the local time where the work is being performed, which is essential when one dispatcher manages multiple time zones.

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 dispatcher ' s user time zone works for only one locale at a time, and a formula field does not change the time scale used by the scheduling interface.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Dispatcher Console; Gantt timezone; Territory Timezone.

a parent Work Order with Asset-specific Work Order Line Items is the appropriate Field Service design. Work Order Line Items are the standard way to represent individual components, Assets, or tasks under one service engagement. Each line item can carry its own Asset, status, Work Type, products, skills, pricing, and appointment when needed.

Reusable configuration should be preferred over duplicating records or custom objects. Work Types can standardize duration, required skills, required products, and Knowledge, while the Work Order hierarchy and Work Order Line Item hierarchy are available when genuinely separate but related work must be represented.

The alternatives address different parts of the Field Service model. Separate parent Work Orders are only necessary when the work must have independent job lifecycles; Products Consumed records materials used, not the component-level work structure.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Work Orders; Work Order Line Items; Asset-level service tracking.

For this scenario, Salesforce Field Service should use Service Territory and Scheduling Policy. The Service Territory defines the population of resources and appointments being optimized, while the Scheduling Policy supplies the Work Rules and Service Objectives used to evaluate and rank scheduling alternatives.

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. Work Types affect job requirements but are not required optimization-job objects, and polygons help with geography but do not replace the optimization scope or policy.

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

a Product Request related to the Work Order is the appropriate Field Service design. When damaged van stock must be replaced for an upcoming job, the Product Request should be tied to the Work Order (or a line item where appropriate) so inventory personnel can see the job dependency and fulfill the required part.

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 are templates, Service Reports document completed work, and Service Appointments represent the visit rather than the primary transaction for requesting job inventory.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Product Requests; Work Orders; van-stock replenishment.

The requirement is best implemented with a Product Request with Product Request Line Items. A Product Request represents the overall inventory demand and each Product Request Line Item specifies an individual product and quantity. This is the standard workflow when technician stock must be replenished from another Location.

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. Shipments and Product Transfers may be used later in fulfillment, but they do not replace the initial request record that expresses the demand.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Product Requests; Product Request Line Items; inventory replenishment.

The correct configuration is Service Territory Member. The Service Territory Member record links a Service Resource to the territory in which the resource works. That relationship is fundamental to territory-based scheduling and sharing calculations for appointments assigned to the resource.

Field Service access combines Salesforce object permissions with Field Service permission-set licenses and managed sharing. The correct design applies least privilege: technicians, agents, dispatchers, contractors, and administrators should receive only the capabilities required for their operational persona.

The alternatives address different parts of the Field Service model. User Territory links users such as dispatchers to territory access groups; it serves a different persona and sharing purpose than the resource-territory membership relationship.

This approach follows least-privilege design and keeps access changes maintainable as resources, territories, assignments, or user responsibilities change.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Permissions and Sharing — Service Territory Members; resource-territory sharing.

The correct configuration is an Excluded Resource preference on the Account. An Account-level Excluded Resource preference records that the customer should not receive that technician on future work. The Scheduling Policy ' s Excluded Resources rule can then prevent the technician from being considered.

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. Simply removing Preferred status would stop favoring the technician but would not prohibit assignment, and moving territories would affect unrelated customers.

The recommended choice also keeps the decision inside the native scheduling framework, so future optimization and dispatcher actions evaluate the same constraints consistently instead of relying on manual workarounds.

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; Excluded Resources; Account-level preferences.

For this scenario, Salesforce Field Service should use Skills, Skill Requirements, and Service Resource Skills. Skills define capabilities, Skill Requirements state what the work needs, and Service Resource Skills record what each technician possesses and at what proficiency level. Together they provide the complete data model required for skill-based scheduling.

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. Work Types can standardize the requirements but do not replace the underlying Skill and Service Resource Skill records. Routing rules and Work Order statuses do not represent expertise.

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

For this scenario, Salesforce Field Service should use a custom Work Order Status plus a Validation Rule. The custom status provides a clear lifecycle state such as Awaiting Customer Signature, while the Validation Rule prevents transition to a final closed state until the signed Service Report condition is satisfied.

Reusable configuration should be preferred over duplicating records or custom objects. Work Types can standardize duration, required skills, required products, and Knowledge, while the Work Order hierarchy and Work Order Line Item hierarchy are available when genuinely separate but related work must be represented.

The alternatives address different parts of the Field Service model. An approval process is unnecessary for a deterministic signature prerequisite, and escalation rules do not govern whether a Work Order may be closed.

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 lifecycle; Validation Rules; Service Report signature.

The correct configuration is the Work Order Line Items related list on the Work Order page layout. Exposing the standard related list gives technicians direct task-level visibility through the native Work Order mobile experience and keeps the solution aligned with the standard Field Service data model.

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. Visualforce, custom Lightning components, or report-chart links add complexity when the requirement can be satisfied by the standard page-layout relationship.

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; Work Order page layouts; Work Order Line Items.