Reducing a carbon footprint in field service is primarily achieved by reducing the fuel consumption and distance driven by the fleet.

Option B is correct. The Minimize Travel Service Objective calculates the travel distance/time for each potential appointment slot. By giving this objective the highest weight in the Scheduling Policy, the optimization engine will aggressively prioritize schedules that have the shortest routes, even if it means sacrificing other metrics (like "ASAP" or "Preferred Resource"). Shorter routes directly equate to less driving and lower emissions.

Option A (Remove ASAP) might help slightly by removing the urgency to book "now" (which can cause inefficient routing), but it doesn't proactively optimize for low mileage like Option B does.

Option C (Maximum Travel Work Rule) is a hard limit (e.g., "Don't travel more than 50 miles"). While it prevents extreme outliers, it doesn't optimize the routes within that radius.

The Dispatcher Console Map is the most efficient tool for geographic mass actions.

Option A is correct. Salesforce Field Service allows dispatchers to draw custom Map Polygons directly on the Gantt map. Once a polygon is drawn around the affected bushfire area, the dispatcher can right-click the polygon (or use the actions menu) to perform Mass Actions on all Service Appointments contained within that shape. "Unschedule," "Cancel," or "Flag" are standard bulk actions available in this context.

Option B (Reports/Data Loader) is too slow for an emergency response.

Option C (Optimization) would just move the appointments to later times, not cancel/unschedule them.

Option D (List View) is difficult because defining a "bushfire area" using text filters (City, Zip) is often inaccurate compared to drawing the precise boundary on a map.

This question tests the Maintenance Plan generation logic.

Option D is correct. The requirement is Single Visit (One Appointment) for Multiple Assets .

One Work Order Line Item per Asset: This groups all the assets under a single parent Work Order. Each asset gets its own line item (WOLI) for tracking purposes.

One Service Appointment per Work Order: This creates a single appointment for the parent Work Order. The technician arrives once and works through the list of line items (Assets).

Option B ("One Work Order per Asset") would create separate Work Orders (and likely separate Appointments) for every single asset, resulting in multiple visits or a cluttered schedule.

Option C ("One SA per WOLI") would explicitly create a separate appointment for every single asset line item, causing massive double-booking/overlap.

The requirement is to schedule two distinct resources (a Human and a Vehicle) for the same job at the same time.

Option C is correct.

Vehicle as Service Resource: You must model the vehicle as a Service Resource (Type: Asset) to track its availability on the Gantt and prevent double-booking.

Complex Work (Same Start): To ensure the vehicle and the technician are booked together, you use Complex Work dependencies. "Same Start" ensures that the vehicle appointment and the technician appointment are scheduled to begin simultaneously.

Options A and D are incorrect because Products are not scheduled. Consuming a product does not check if the vehicle is available at that specific time, potentially leading to double-booking the van.

Option B is incorrect because "Immediately Follow" implies a sequence (Technician finishes - > Vehicle starts), which is not how a shared ride/equipment scenario works.

The goal is to prevent low-priority "Inspections" from being ignored indefinitely until they miss their deadline, without permanently ranking them above high-value "New Installs."

Option B is correct (based on the scenario's specific constraints). By using automation to elevate the Inspection's priority to '1' (High) only when it is due "tomorrow," the system treats it as urgent only when necessary to avoid the penalty. Since "New Installs" are also Priority '1', the two will compete on equal footing on that final day, ensuring the Inspection has a fighting chance to be scheduled alongside high-value work.

Option C (Dynamic Priority) is a standard solution for "aging" work. However, the option states it caps the value at '2'. In standard SFS priority (where 1 is highest), a '2' will never beat a '1'. Therefore, the inspection would still likely be bumped by a New Install (Priority 1) even on its due date, leading to a penalty.

Option D ("Schedule Over Lower Priority") is used for emergency reshuffling, but does not inherently solve the prioritization logic between these two specific task types.

Salesforce Field Service uses two distinct KPIs for service contracts: Availability and Reliability. The two differ in whether planned downtime (scheduled maintenance) is counted against the asset.

Option C is correct. Availability measures the proportion of expected uptime that the Asset was usable, excluding only unplanned downtime. Planned maintenance is expected and excluded from the calculation, so Availability = (expected uptime - unplanned downtime) / expected uptime.

Option D is partially right in form but mislabeled — Reliability is the metric that subtracts both planned and unplanned downtime: Reliability = (expected uptime - planned - unplanned downtime) / expected uptime. Mislabeling it as the Availability formula (Option A) is incorrect.

Option A is incorrect because that is the Reliability formula, not Availability.

Option B is incorrect because Asset Uptime is the numerator of these formulas, not a ratio of Availability divided by Reliability.

The Field Service Mobile Settings configuration controls the behavior of the mobile app (branding, location tracking, flows, etc.).

Option D is correct. To apply different settings to different groups of users, you must create multiple Field Service Mobile Settings records. You assign these settings records to specific User Profiles .

You would create one settings record with "Collect Service Resource Geolocation History" enabled (for the tracked users).

You would create a second settings record with it disabled (for the untracked users).

You then map the relevant Profiles to the appropriate Settings record.

Options A, B, and C imply global settings or non-existent tabs ("Mobile App Configuration" tab where you select users/profiles directly doesn't exist in the global settings in this manner; it is done via the specific Mobile Settings object assignments).

This scenario distinguishes between "External" contractors (buckets of work) and "Internal/Named" contractors (managed schedule).

Option C (Contractor A): Since they manage work outside Salesforce and work specific hours (9-10 am), they should be modeled as Capacity-Based Resources . This feature allows you to define a "bucket" of capacity (4 hours/day) without optimizing individual travel or start times. You simply dump work into their bucket until it is full.

Option A (Contractor B): Since they manage the schedule inside Salesforce (likely named users), they act like standard employees. To limit them to 4 hours of work within a 9-5 shift, you use a Work Rule (Count Rule) . You configure the rule to limit "Duration" to 240 minutes (4 hours) per day and use a Relevance Group to ensure this rule only applies to Contractor B (not internal employees or Contractor A).

Salesforce Field Service uses a chain of objects — Product → Product Item → Product Item Transaction → Product Consumed — to track inventory from stock to consumption. The link between these records is what enables full lifecycle visibility.

Option D is correct. Populating the 'Product Item' on each Product Consumed record creates the link back to the specific stock record (held at a Location for a Service Resource or warehouse). This connection lets Salesforce decrement inventory, generate Product Item Transactions automatically, and trace where the consumed item originated.

Option A is incorrect because Product Item Transactions are generated automatically based on Product Item activity — they are not manually populated on Product Consumed.

Option B is incorrect because Price Book Entry tracks pricing data, not stock. Leaving Product Item blank breaks the inventory chain.

Option C is incorrect because Location is helpful context but is not, by itself, what links Product Consumed to inventory; the Product Item connection is required.

Mapping resources to specific Zip Codes (which are not necessarily Service Territories) is a common high-volume requirement.

Option A is correct. Creating a standard Service Territory for every postal code (Option D) creates a hierarchy that is too deep and hurts performance.

Instead, modeling "Zip Code Coverage" as a Custom Object (or data table) allows for a cleaner data model. You then use the Extended Match Work Rule . This rule is highly flexible; it can verify that the Zip Code on the Service Appointment matches a record in the Zip Codes Covered related list on the Service Resource. This supports optimization without bloating the Territory or Skill tables.

Option B (Match Fields) only works for 1-to-1 matching (e.g., The Resource has one zip field). It cannot easily handle a resource covering 50 different zip codes unless you use the custom object approach described in A.