Universal Containers would like to track Asset downtime.
What should a consultant recommend if a company wants to track Asset downtime?
Answer : D
Salesforce Field Service provides a standard object specifically designed to track when an Asset is unavailable, so that availability and reliability KPIs can be reported accurately.
Option D is correct. 'Asset Downtime Periods' is the standard out-of-the-box object that records when an Asset is down, including the start and end time and whether the downtime was planned or unplanned. These records are used to calculate Availability and Reliability metrics, and they integrate with maintenance and service contract reporting.
Option A is incorrect because 'Asset Timelines' is a visualization tool that displays Asset history, not the data store that captures downtime.
Options B and C are incorrect because a custom object or custom fields would duplicate functionality that Salesforce already provides natively, and would not integrate with the standard Availability/Reliability calculations.
What must be populated on the 'Product Consumed' record in order to be able to track the entire life cycle of items in the inventory, including their storage, transfer, and consumption?
Answer : D
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.
Universal Containers would like the Service Appointment times that are displayed on the 'Dispatcher Console' to reflect the actual times a field worker starts and completes the work. That way, if they finish early, they might be able to add additional work to the new white space.
What implementation approach should the Field Service consultant recommend?
Answer : D
The requirement is specifically to free up white space on the Gantt when a tech finishes early.
Option D is correct. The Gantt chart visual blocks are drawn based on Scheduled Start and Scheduled End. If a tech finishes a 2-hour job in 30 minutes, the Gantt bar will remain 2 hours long unless the Scheduled End is updated. By using a Mobile Flow to update both the Actuals (for reporting) and the Scheduled (for the Gantt), the bar shrinks, revealing 1.5 hours of open availability for the dispatcher to utilize.
Option C is the 'Purist' data view (don't change scheduled), but it fails the specific business requirement of allowing new work to be added immediately.
Option A suggests creating custom fields for the original times, which is a valid part of the solution (to keep a history), but Option D describes the core functional mechanism (Flow updating the standard fields) required to achieve the Gantt behavior. The 'Offline' warning in A is true but D is the more direct configuration answer.
Universal Containers services customers in the public sector. When technicians are needed for repair jobs in government buildings, it is crucial that only technicians with the relevant security badge are selected for the job.
Which two configuration options can a consultant recommend to achieve the business requirement?
Answer : B, E
To filter resources based on strict criteria (like security clearance), you use Work Rules (Hard Constraints).
Option B is correct (Match Boolean): This is a simple, effective method for binary requirements. You place a checkbox on the Service Appointment (e.g., 'Requires Security Badge') and a corresponding checkbox on the Service Resource (e.g., 'Has Security Badge'). The Match Boolean Work Rule enforces that if the Appointment is checked, the Resource must also be checked.
Option E is correct (Extended Match): If the requirement is more complex (e.g., matching a specific type or level of badge), the Extended Match Work Rule is best. It allows you to match a field on the Service Appointment (or Work Order) to a related list or field on the Service Resource. For example, matching the 'Badge Type' required by the Government Account to the 'Badge Type' held by the Resource.
Note: While Skills (Option C) are also commonly used for this, the question specifically points toward Work Rule configurations (Boolean/Extended) often used for strict compliance attributes.
A company wants to evaluate whether Global Optimization is giving them the desired results like reduced travel or improved resource utilization. As a result of the evaluation, the company has decided to deploy globally.
What should an admin do to provide visibility into KPI improvements for Global Optimization?
Answer : B
Optimization Insights is the dedicated Field Service feature that captures per-run metrics such as travel time saved, utilization, gap minimization, and unscheduled work, making it the standard way to evaluate Global Optimization quality.
Option B is correct. Enabling Optimization Insights records the before/after metrics for each optimization request --- travel minutes, scheduled vs. unscheduled count, average gap, and other KPIs. The data is available on the Optimization Request object and can be reported on directly in Salesforce.
Option A is incorrect because the SFS Dashboard package is an older, less precise tool that does not capture per-run optimization data.
Option C is incorrect because the Dispatcher Console is an operational view, not an analytics surface.
Option D is incorrect because subscribing to an Analytics App is unnecessary overhead when a built-in feature exists.
Universal Containers would like customers to be able to schedule appointments themselves in addition to being able to schedule appointments by calling into the call center.
Which two options should an architect recommend to meet UC's requirements? (Choose 2 options)
Answer : C, D
Customer self-scheduling requires an externally exposed booking action, while call-center bookings happen inside Salesforce. The Book Appointment action serves both surfaces.
Option C is correct. The Book Appointment global action returns available appointment slots based on the Scheduling Policy, Work Rules and Operating Hours, and lets a call-center agent confirm one. It is the standard internal-user booking surface.
Option D is correct. The Communities Book Appointment action exposes the same booking capability through an Experience Cloud (Communities) site, enabling customer self-service scheduling without contacting the call center.
Option A is incorrect because Get Candidates returns eligible resources for an existing appointment, not bookable time slots, and is a dispatcher tool.
Option B is incorrect because a nightly optimization job rearranges existing appointments and does not allow customers or agents to choose a slot.
Universal Containers uses In-Day Optimization to optimize a Service Territory schedule during working hours. The dispatchers have recently noticed that In-Day Optimization reschedules Service Appointments in status 'In Progress' to other Service Resources, which requires them to correct the schedule manually.
What should a consultant recommend to troubleshoot this behavior?
Answer : C
When running optimization (Global or In-Day), the engine is allowed to move any appointment that is not 'Pinned.'
Option C is correct. In Salesforce Field Service, you must explicitly define which statuses are considered Pinned (immovable) during optimization. This is configured in Field Service Settings > Optimization > Logic. If the 'In Progress' status is not selected in the 'Pinned Statuses' list, the optimization engine sees that appointment as movable. To improve the schedule, it might unassign the current tech and assign a different one, even though the tech is already on-site.
Ensuring 'In Progress' is 'excluded from optimization logic' (Pinned) forces the engine to schedule around that appointment rather than moving it.
Option B refers to 'Status Transitions,' which controls the lifecycle flow (e.g., New -> Scheduled -> In Progress) but does not control the scheduling engine's permission to move the job.