Explanation:

Ursa Major Solar values strong customer relationships and consistent service. The management's request to have technicians continue servicing the same customer when possible is a common business requirement aimed at building rapport and improving customer satisfaction through familiarity. Salesforce Field Service has a specific mechanism to influence resource assignment based on past interactions or customer preferences.

Why Option B is Correct:
Assign a Preferred status Resource Preference to the Account: Resource Preferences are a powerful tool in Salesforce Field Service that allow you to guide the scheduling engine's choices. You can set preferences at the Account level. By assigning a "Preferred" status to a specific Resource (technician) for a particular Account, you signal to the scheduling system that this technician should be prioritized for assignments to that customer. This directly addresses the requirement of having the same technician service the customer when possible.

Why Other Options Are Incorrect:

A. Designate a Skill-based resource to the Work Order: Skill-based routing ensures that a technician with the required skills for a job is assigned. While important for technical proficiency, it doesn't inherently favor assigning the same technician who has serviced the customer before. It focuses on technical capability rather than relationship continuity.

C. Configure an account preference on the Service Resource record: Resource preferences are set on the Account (or Work Order) to influence which resources are assigned to it. Setting preferences on the Service Resource record itself is not the standard way to link a technician back to a specific customer they've serviced before for preference.

D. Include the Required Resource work type in Scheduling Policies: Work Types define the type of service. While you can associate resources with Work Types, using "Required Resource" within a Work Type or Scheduling Policy is more about ensuring a specific resource is assigned if known beforehand, or that certain resource constraints are met. It doesn't automatically promote continuity for past customer service relationships without explicit preference settings.

References:
Salesforce Field Service Documentation: Look for "Resource Preferences" or "Manage Resource Assignments for Accounts."

Explanation:

In Salesforce Field Service Lightning, the Extended Match work rule assigns Service Resources based on related object records (via a junction or linking object).

This rule matches a field on the Service Appointment (or related object like Work Order) to a field on the Service Resource through an intermediate custom junction object.

Common scenarios include matching on complex criteria like postal code coverage areas, product expertise, or customer preferences stored on related records (e.g., a "Coverage" object linking ZIP codes to resources).

It extends beyond direct field matching, enabling indirect relationships for advanced assignment logic.

The other options do not support related object-based matching:

A. Resource Availability — Checks shift hours, absences, and capacity but not related records.

C. Required Resource — Enforces assignment to a specific named/preferred resource on the appointment (direct lookup, not via related objects).

D. Match Field — Matches direct fields on Service Appointment to fields on Service Resource (e.g., a custom Language field on both)—no junction/related object involved.

Reference:
Salesforce Help: Work Rule Type - Extended Match – "Use the Extended Match work rule type to schedule service appointments using custom criteria. It uses a junction, or linking, object to match a field on the Service Appointment object to a related field on the Service Resource object."

Common in Field Service Consultant exam questions testing advanced work rules for indirect/related record matching.

Explanation

Reshuffle (A):
Allows the dispatcher to re-optimize the schedule in real time when appointments are cancelled or rescheduled.
It reprioritizes existing appointments based on scheduling policies and work rules, ensuring technicians’ time is used efficiently.
Perfect for handling last-minute changes without running a full optimization job.

In-day Optimization (D):
Specifically designed for same-day adjustments.
It re-optimizes schedules throughout the day to account for cancellations, delays, or new emergency work.
Ensures technicians are reassigned to the most efficient routes and appointments as the day evolves.

Why not the others?

B. Group Nearby:
Useful for clustering appointments geographically, but it doesn’t help with last-minute cancellations or reschedules.

C. Resource Schedule Optimization:
This is a broader optimization job (often run overnight or periodically).
It’s not designed for real-time adjustments during the day, which is what UMS needs.

Best Practice
Use Reshuffle for quick, dispatcher-driven adjustments.
Use In-day Optimization for automated, continuous schedule updates throughout the day.

Together, they ensure technicians stay productive even when customers cancel or reschedule at the last minute.

Explanation:

This question focuses on the process for a technician to order parts from an inventory location to their current location.

A Product Request is the master object that represents the entire request to transfer inventory from one location (e.g., a central warehouse) to another (e.g., the technician's van or a local depot). It contains header-level information like the source and destination locations.

Product Request Line Items are the child records of the Product Request. Each line item specifies the exact product and the quantity being requested. A single Product Request can contain multiple line items for different products.

This two-step process (create the header record, then add line items) is the standard and supported way to request parts in Salesforce Field Service inventory management.

🔴 Option A is incorrect: A Shipment is created to represent the fulfillment of a transfer or order (like a Product Request) once it is being acted upon, not the initial request itself.

🔴 Option B is incorrect: Product Consumed is used to record parts that have been used on a Work Order, reducing on-hand inventory. It is not used to request new parts.

🔴 Option D is incorrect: A Work Order Line Item defines a product needed to complete a job. While it can be the reason for a parts request, it is not the mechanism for creating the request itself. The request process is handled through the dedicated Product Request objects.

🔗 Reference:
Salesforce Help: "Request Inventory Using the Mobile App"
Key Concept: The Product Request object is the formal way to request a transfer of inventory, and it contains Product Request Line Items for the specific products needed.

Explanation:

Universal Containers has 100 external contractors:
75 contractors need access to Work Orders, Assets, the Field Service mobile app, and Chatter.
These are field technicians performing work. For external users, they require the Field Service Contractor license (often a login-based or community-based license, such as Partner Community or Customer Community Plus with Field Service permissions). This provides access to the mobile app for viewing/updating work orders and service appointments, assets, and Chatter collaboration via communities.
The remaining 25 contractors are paid commissions on sales and need to schedule resources.
These act as dispatchers or managers who schedule field resources (assigning service appointments, managing crews, etc.). For external users needing scheduling capabilities (e.g., access to the Dispatcher Console or scheduling tools), they require the Field Service Contractor Plus license. This extends the standard Contractor license to include dispatcher-like functionality for external partners.

Option B recommends:
25 Contractor Plus licenses (for the scheduling group).
75 Contractor licenses (for the mobile/field access group).
This matches the differentiated needs while optimizing costs for external users (Contractor licenses are typically cheaper and login-based).

The other options do not align:
A suggests all 100 get the higher-tier Contractor Plus, which is overkill for the 75 who don't need scheduling.
C reverses the quantities, giving scheduling access to too many and insufficient mobile/dispatcher split.

Reference:
Salesforce official pricing and licensing for Field Service includes distinct Contractor (for technicians/mobile access) and Contractor Plus (for extended dispatcher/scheduling access for external users):
Help documentation on setting up contractors emphasizes community licenses with Field Service permissions, and Contractor Plus for advanced needs.