Free Practice Questions for Salesforce AP-209 Exam

This question tests the Maintenance Plan generation logic.

Option D is correct.The requirement isSingle Visit(One Appointment) forMultiple Assets.

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

One Service Appointment per Work Order:This creates asingleappointment 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.

To tier resources generally (not per customer), you use the Resource Priority Service Objective.

Option C is correct.TheResource Priorityobjective works on a scoring scale where aHigher Valueindicates aHigher Priority. The optimization engine attempts to assign the appointment to the resource that yields the highest overall schedule score.

By assigning Full-Time = 10, Contractors = 9, and Part-Time = 8, the engine will "score" the Full-Time option highest, followed by the Contractor.

Option Duses the inverse logic (1, 2, 3). If deployed, the engine would favor the Part-Time employees (Score 3) over the Full-Time employees (Score 1), which is the opposite of the requirement.

Options A and Brefer toPreferred Resource, which is typically defined on theAccountorWork Orderlevel (e.g., "Bob is preferred for Customer X"). It is not efficient for ranking entiregroupsof employees globally.

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

Option B is correct.When a schedule hasno 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 haszero time slots(No Availability).

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

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