Salesforce AP-209 Exam With Confidence Using Practice Dumps

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

Option C (Contractor A):Since they manage workoutsideSalesforce and work specific hours (9-10 am), they should be modeled asCapacity-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 scheduleinsideSalesforce (likely named users), they act like standard employees. To limit them to 4 hours of work within a 9-5 shift, you use aWork Rule (Count Rule). You configure the rule to limit "Duration" to 240 minutes (4 hours) per day and use aRelevance Groupto ensure this ruleonlyapplies to Contractor B (not internal employees or Contractor A).

To stop a resource from receiving work, you must mark them as inactive and ensure the scheduling engine respects that status.

Option C is correct:Deactivating the Service Resource(unchecking the "Active" checkbox on the record) is the standard way to "fire" or terminate a resource. It preserves history but flags them as no longer working7.

Option A is correct:You must ensure yourScheduling Policyincludes theActive ResourcesWork Rule8. This rule explicitly tells the optimization engine: "Do not assign appointments to any resource where Active = False." Without this rule, the engine might still technically assign work to an inactive record if no other constraints block it.

Option B(Delete) is bad practice (data loss).

Option D(Excluded Resources) is for specificjob-by-jobexclusions (e.g., "Don't send Bob to this specific customer"), not for global termination.

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.