The correct configuration is Service Report Language on the Work Order. The Work Order-level language field controls the language used for the Service Report generated for that work and its related appointments or line items. This lets the technician produce customer-facing documentation in the appropriate language.

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. Changing the organization or technician user language is too broad and does not scale to customers who require different report languages.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Mobility — Service Report Language; Work Orders; multilingual reports.

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 Field History Tracking on Assets. Field History Tracking records changes to selected Asset fields with timestamps, user information, and prior/new values where supported. Enabling it on lifecycle fields such as Status and location-related attributes gives managers an audit trail for a specific installed component.

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. A Work Order related list shows service activity but not every field change, while custom tracking fields duplicate native auditing capability.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Assets — Assets; Field History Tracking; lifecycle audit.

The requirement is best implemented with a Capacity-Based Service Resource for the Contractor Manager. Capacity-based scheduling models an external provider as a pool of contracted work capacity rather than as named individual technicians. The Contractor Manager can represent the weekly 100-hour capacity and update the work after completion.

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. A Service Crew assumes known resources working together, while creating individual contractor technicians would add detail the stated operating model does not require.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Resources — Capacity-Based Service Resources; contractors; capacity scheduling.

For this scenario, Salesforce Field Service should use Service Resources, Resource Absences, and Work Orders through User Territory sharing. With private OWD and User Territory sharing enabled, territory users receive access to the operational records necessary to dispatch and manage work in the territories they cover, including resources, their absences, and relevant work records.

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. Accounts may require separate parent-record sharing considerations, while Work Types are configuration templates rather than territory-specific operational records.

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

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.

the Crew Management tool is the appropriate Field Service design. Crew Management lets the dispatcher add an appropriately skilled Service Resource to the existing crew for the required timeframe, correcting the crew ' s skill composition without replacing the appointment.

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. Creating another appointment or editing the appointment to add an independent resource bypasses the crew membership model; changing the Work Type changes requirements, not the active crew composition.

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

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.

The requirement is best implemented with High optimization runtime when priorities are similar and candidate counts are large. A longer runtime gives the optimizer more time to evaluate combinations. When many appointments have the same priority and each appointment has many qualifying resources, the search space expands and a higher runtime can improve schedule quality.

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. A blank Scheduling Policy is a configuration issue rather than a reason to spend more optimization time, and disabling travel/break calculations changes the model rather than increasing optimization complexity in the way described.

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 runtime; candidate volume; appointment priority.