Salesforce FS-Con-101 Practice Test Questions Answers

The requirement is best implemented with Field Service Admin Permissions. These dispatchers are not only scheduling work; they are creating territories, defining Scheduling Policies, and controlling configuration settings. Those are administrative capabilities and require Field Service Admin Permissions in addition to dispatcher access.

When a requirement concerns a lifecycle action such as status change, a license concern, or territory visibility, the configuration should be placed in the corresponding security layer rather than simulated through record ownership changes or broad administrative access.

The alternatives address different parts of the Field Service model. Mobile and Scheduling licenses support different personas and do not grant the configuration authority described in the scenario.

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 — Field Service Admin and Dispatcher permissions; configuration access.

The requirement is best implemented with one Work Order Line Item per Asset and one Service Appointment per Work Order. This combination preserves an individual record for every installed Asset while consolidating the quarterly inspection into one field visit. Asset-specific line items provide compliance detail; the single parent appointment represents the one required onsite attendance.

Maintenance Plans are the native Field Service framework for recurring preventive service. They combine Assets, Work Types, recurrence, generation timeframes, and Work Order or Service Appointment generation so that future work can be created in a controlled and repeatable way.

The alternatives address different parts of the Field Service model. One Work Order per Asset or one Service Appointment per line item would fragment the inspection into multiple jobs or visits and conflict with the requirement for a single visit.

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; Work Order generation; Service Appointment generation.

the appointment owner and members of the relevant User Territory is the appropriate Field Service design. With private sharing, Field Service uses managed sharing and territory public groups. Once a Service Appointment is canceled, assigned-resource access is no longer the primary path; the owner and users with the appropriate User Territory access retain visibility.

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. Service Territory membership and Assigned Resources serve different scheduling and access functions; the cancelled state changes which automatic sharing paths remain applicable.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Permissions and Sharing — Private OWD; User Territories; Service Appointment sharing.

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.

The correct configuration is Work Order Line Items, each with its own Service Appointment. Each task must retain its own completion, inventory, pricing, and scheduling information. A Work Order Line Item provides the task record, and a child Service Appointment allows that task to be scheduled to the same or a different technician as required.

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. Custom objects are unnecessary, and using Service Appointments as the parent of task records reverses the standard Field Service data model.

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 Line Items; child Service Appointments; task scheduling.