Free Salesforce FS-Con-101 Practice Exam with Questions & Answers

a new Service Appointment on the original Work Order or a new Work Order plus Service Appointment is the appropriate Field Service design. Each physical return visit should be represented separately so the first visit remains part of the historical record. Continuing the same job can use another appointment on the existing Work Order; separately managed follow-up work can use a new Work Order and appointment.

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. Rescheduling the original appointment would overwrite the timing representation of the first visit and reduce the accuracy of visit-history reporting.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Return visits; multiple Service Appointments; service history.

For this scenario, Salesforce Field Service should use one Product Item with serialized units in the related list. The locks are serialized inventory because every physical unit has a unique identifier. The Product Item represents the stock at the technician ' s van Location, and the Serialized Products related list stores each individual serial number.

Inventory design should also preserve pricing and traceability. Price Books and Price Book Entries supply commercial pricing, while serialized inventory gives unit-level identity when individual items must be tracked. Product Requests and Product Transfers manage replenishment and movement rather than the underlying job structure.

The alternatives address different parts of the Field Service model. A quantity-only Product Item would lose individual traceability, and serial numbers in Notes are unstructured and cannot participate properly in serialized-inventory transactions.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Serialized Products; Product Items; van stock; serial-number tracking.

Appointment List and Color Palettes is the appropriate Field Service design. The Appointment List exposes rule-violating appointments for operational review, while Color Palettes visually distinguish appointments on the Gantt based on selected criteria. Together they let dispatchers identify exceptions quickly without opening each record.

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. The Gantt and Gantt Map are broad presentation surfaces; the question asks for the features used specifically to visualize and distinguish rule violations.

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; Appointment List; Color Palettes; rule violations.

The requirement is best implemented with 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.

Field Service Mobile is designed for technicians working in changing connectivity conditions. Standard page layouts, quick actions, flows, Service Reports, Knowledge, and supported mobile extensions should be used before introducing custom Visualforce or bespoke components because the native features participate in synchronization, offline behavior, and the Field Service security model.

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.

The requirement is best implemented with Product Item. A Product Item represents a specific Product at a specific inventory Location and records quantity on hand. It is therefore the correct object for understanding distribution of an expensive part across warehouses, technician vans, and other inventory locations as stock is reused and replenished.

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. Assets represent installed customer equipment, Maintenance Plans create recurring work, and Entitlements govern service eligibility rather than stock distribution.

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

For this scenario, Salesforce Field Service should use Territory and Resources filters. Filtering by Territory isolates the geographic operating area and its local scheduling context, while filtering by Resources narrows the Gantt to the technicians the dispatcher is actively managing.

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. Hours changes the visible time range but does not isolate the multi-time-zone workforce, and Skills filtering serves qualification searches rather than general console simplification.

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 — Dispatcher Console filters; Territory; Resources.

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.

For this scenario, Salesforce Field Service should use Page Layouts. Field Service Mobile uses assigned layouts to determine which Work Order and Service Appointment fields and related information technicians see. Appropriate profile/record-type layout assignments therefore provide the standard way to simplify the mobile record view.

Field Service Mobile is designed for technicians working in changing connectivity conditions. Standard page layouts, quick actions, flows, Service Reports, Knowledge, and supported mobile extensions should be used before introducing custom Visualforce or bespoke components because the native features participate in synchronization, offline behavior, and the Field Service security model.

The alternatives address different parts of the Field Service model. Field Sets apply to specific configurable surfaces, Visualforce is custom development, and Mini-Page Layouts do not drive the normal Field Service Mobile record experience.

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; Page Layouts; technician record views.

For this scenario, Salesforce Field Service should use custom Asset reports using Parent Asset and Root Asset. Parent Asset and Root Asset expose the hierarchical position of an installed component. Custom reporting can reference these fields to analyze Assets while preserving hierarchy context.

An Asset represents a customer-specific installed instance of a Product, which is why lifecycle, service history, hierarchy, installation dates, replacements, and component relationships should be modeled on Assets rather than on generic Product records. Work Orders can then reference the exact installed equipment being serviced.

The alternatives address different parts of the Field Service model. The interactive View Asset Hierarchy action is useful for navigation but is not the requested reporting solution, and standard Asset reports do not expose all hierarchy fields in the same way.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Assets — Asset hierarchy reporting; Parent Asset; Root Asset.

The requirement is best implemented with a Work Order Quick Action that launches a Flow. A single Flow can collect the technician ' s required information once and update the Work Order, related Service Appointment, and Case in one guided mobile interaction.

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. Multiple actions would force duplicate entry, Process Builder is not the mobile interaction layer, and a custom component adds code where a standard Flow action is sufficient.

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; Flow; cross-record updates.