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

The requirement is best implemented with Products Required and Skill Requirements. A first-time fix depends on sending a technician who has both the required expertise and the expected parts. Skill Requirements filter or rank qualified resources, while Products Required communicate the material expected for the job.

Good Work Order design also preserves the distinction between planned work and execution results. Products Required, requirements, and task structure should be established before service; Products Consumed, actual times, signatures, and completion statuses then record what actually happened in the field.

The alternatives address different parts of the Field Service model. Products Consumed records what was actually used after execution; estimated duration and SLA information do not ensure that the technician has the required competence and inventory.

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; Products Required; Skill Requirements; first-time fix.

Earliest Start Permitted and Due Date is the appropriate Field Service design. These fields define the internal scheduling window that represents when the appointment may begin and the latest time by which it should be completed. They are the Service Appointment fields most directly aligned with SLA constraints.

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. Scheduled Start/End are scheduling outcomes, Actual Start/End record execution, and Arrival Windows are customer-facing arrival expectations rather than the core SLA boundaries.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Service Appointment constraints; Earliest Start Permitted; Due Date.

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.

For this scenario, Salesforce Field Service should use Asset Relationships visible through Primary Assets and Related Assets. Asset Relationship records capture replacement, upgrade, and related lifecycle links between specific Assets. The relationships are viewed on the Asset through the Primary Assets and Related Assets related lists.

Asset relationships and hierarchy fields provide different views of the installed base. Parent and Root Asset fields model structural hierarchy, while Asset Relationship records can model replacement, upgrade, or other lifecycle relationships. Field History Tracking complements those relationships by auditing changes to selected Asset fields over time.

The alternatives address different parts of the Field Service model. Field History Tracking only audits field changes and Product Requests manage inventory demand; neither models the relationship between an old Asset and its replacement.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Assets — Asset Relationships; Primary Assets; Related Assets.

Service Territories sized to fewer than about 50 resources is the appropriate Field Service design. Scheduling and optimization quality improves when territories are kept within practical resource and appointment volumes. Splitting 140 resources into three territories yields roughly 46–47 resources per territory and approximately 800 appointments per day if demand is balanced.

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. Two territories would leave about 70 resources in each, while polygons inside one very large territory do not reduce the number of resources the scheduling engine must consider.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Service Territory design; optimization scalability; dispatcher performance.

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 one Service Resource with the relevant permission-set licenses. One employee should be represented once as a Service Resource. Access to technician and dispatcher capabilities is then provided through the appropriate licenses and permission sets rather than by duplicating the person in the resource model.

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. Skills do not grant application access, and Resource Type is not a multi-value role mechanism for simultaneously defining separate dispatcher and technician identities.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Permissions and Sharing — Service Resources; Dispatcher permissions; Resource permissions.

The requirement is best implemented with Drip Feed dispatch. Drip Feed controls how many future Service Appointments are released to each technician. Setting the quantity to the required number keeps the technician queue small and automatically dispatches the next eligible appointment as current work is completed, canceled, or cannot be completed.

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. Manual dispatch creates avoidable administrative work, while ordinary auto-dispatch does not by itself provide the same controlled queue depth and protection from frequent schedule changes.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Drip Feed; automated dispatch; mobile appointment visibility.

The correct configuration is Gantt Palettes. Palettes color-code Service Appointments according to selected field values, including numeric and currency values. A revenue field can therefore be mapped to a palette so dispatchers immediately see high-value appointments on the Gantt.

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. Field Sets control which data is displayed, Map Report Layers add geographic overlays, and Gantt Actions perform operations rather than continuously color-coding appointment value.

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 Palettes; appointment visualization.

For this scenario, Salesforce Field Service should use Products and Price Books. The consumed part is a Product, and pricing is supplied through Price Book Entries so the Product Consumed record can carry list price, unit price, discounts, and billing context.

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. Assets identify installed customer equipment, while Opportunity Line Items belong to the sales process and custom objects are unnecessary for standard Field Service part pricing.

The standard inventory model also keeps planned demand, stock position, movement, actual consumption, and pricing available for reporting without duplicating the same information in custom records.

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