Pass the Salesforce Accredited Professional Certification AP-209 Questions and answers with ExamsMirror

The Dispatcher Console (Gantt) allows admins to customize which fields are visible in various panels and tooltips using standard Salesforce Field Sets.

A is correct (Resource Absence):You can control what information appears when a dispatcher hovers over a non-availability block (e.g., "Sick Day," "Doctor's Appointment") by editing the field set on the Resource Absence object.

B is correct (Service Appointment):This is the most heavily customized object. You can configure field sets to control the columns in the Appointment List, the text shown on the Gantt bar, and the fields in the tooltip (hover).

C is correct (Service Resource):You can customize the resource list (left-hand side of the Gantt) to show fields like "Vehicle Type," "Skill Level," or "Phone Number" by editing the field set on the Service Resource object.

Options D and E:Service Territory and Assigned Resource do not have direct field sets that control theDispatcher Consolelayout in the same way the primary transactional objects do.

Capacity-Based Scheduling is a simplified scheduling model (buckets of work) compared to the standard, granular optimization. Because it ignores specific travel times and start times, it has significant limitations.

Option B is correct:Capacity-Based Resources (contractors)cannotbe assigned Multi-Day Service Appointments. They work on a "Hours per Day" or "Jobs per Day" limit, and the system cannot span a single appointment record across multiple days for them.

Option C is correct:Theycannothandle Complex Work (dependencies like "Start Same Time" or "Follow Immediately"). Since the engine doesn't calculate their precise start time (it just ensures they haveenoughhours in the day), it cannot synchronize their work with other resources.

Option D is incorrect:You cannot create a Service Crew composed of Capacity-Based resources.

During Scoping (the initial phase), the goal is to align on the "What" and "Why" before moving to the "How."

Option A is correct (Work Parameters):You must define what constitutes a "Job" (Work Order), how long it takes, and what skills are needed. This is the foundation of the data model.

Option C is correct (Terminology):Mapping the customer's language to Salesforce terms (e.g., "We have 'Truck Rolls' -> In Salesforce, that is a 'Service Appointment'") is crucial to avoid confusion throughout the project.

Option D is correct (Project Objectives):Defining what is "Essential" (MVP) vs. "Nice to Have" sets the project boundaries and success metrics.

Option B (Sprint Review) happensduringthe build phase (Agile methodology), not during initial scoping.

Option E (Solution Design) is theoutputof the scoping/analysis phase, not a topic you ask about during the initial discovery.

This addresses the "Shift vs. Operating Hours" architecture.

Option B is correct. When a schedule has no consistent weekly pattern , using standard Operating Hours (which repeat Mon-Sun indefinitely) is inefficient. The best practice is to assign the Service Territory Member (the resource) a "Shell" Operating Hours record that has zero time slots (No Availability).

You then use Shifts to define the specific working times for specific dates (e.g., "Nov 1st: 9am-2pm").

Because the base Operating Hours are empty, the Scheduling Engine looks only at the Shifts to determine availability. This avoids the conflict of having to "subtract" time from a standard day or constantly update the base record.

When a contractor company provides aggregate hours rather than a list of named technicians, the correct model is a Capacity-Based Resource so the engine schedules against capacity in hours, not against a specific individual.

Option A is correct. A Capacity-Based Resource lets you express '20 hours per day' as capacity, assign Operating Hours of 9:00 AM–5:00 PM that match the contractor's agreed window, and add the 'maintenance' skill to restrict the type of work routed to them.

Option B is incorrect because preferring contractors is a soft preference; it does not enforce the contractor's distinct hours or capacity.

Option C is incorrect because creating a separate Service Territory does not, by itself, model contractor capacity or restrict the work type assigned.

Option D is incorrect because a Named Resource represents a single person, not a company providing aggregate hours, and the Designated Work approach does not capture the daily capacity cap.

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).

When dealing with a Bring Your Own Device (BYOD) strategy (common with contractors), device compatibility is the biggest technical hurdle.

Option B is correct. Salesforce explicitly publishes a list of supported devices and operating systems (iOS and Android versions) 6 . Since the company does not own the phones, they cannot guarantee every contractor has a compatible device. The consultant must warn the client to check these specs against their contractors' hardware.

Option A is a policy decision, not a technical constraint. You can track contractor location if they agree to it.

Option C is false; Contractor licenses (Community Plus) do include access to the Field Service Mobile App.

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.

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.

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.