Free AP-209 Questions Attempt

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.

To prioritize junior resources without creating rigid "hard constraints" (which might prevent scheduling altogether if no junior is available), you should use Service Objectives (Soft Constraints).

Option C is correct (Resource Priority):By assigning a higher priority value to Junior Service Resource records and adding the "Resource Priority" objective to the scheduling policy, the optimization engine calculates a higher score for these resources. This acts as a general "preference" to use them whenever possible.

Option E is correct (Least Qualified):The "Skill Level" Service Objective has a setting called "Prefer Least Qualified." When enabled, the engine prefers the resource who has thelowestskill level that still meets the job requirement. For example, if a job requires Skill Level 50, and you have a Senior (Level 90) and a Junior (Level 55), the engine will pick the Junior. This is a best practice to prevent "over-qualified" resources (Seniors) from being booked on routine jobs, keeping them free for complex tasks.

Asset replacement and history in Salesforce are tracked using the Asset Relationship object.

Options A and B are correct.TheAsset Relationshipobject links two assets together (e.g., Old Asset -> New Asset) with a relationship type like "Replacement" or "Upgrade." On the Asset page layout, this related list (often labeled "Asset Relationships" or "Related Assets") allows you to see the history in both directions:

Forward:See the new asset that replacedthisasset (Option A).

Backward:See the old asset thatthisasset replaced (Option B).

Options C and D are incorrect. "Primary Assets" is typically a concept associated with Service Contracts (covering the main asset) or Entitlements, not the history of physical swaps/upgrades between asset records.

(Note: The provided PDF source likely contains an error marking D as correct. "Primary Assets" is not the standard location for replacement history.)

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.