매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
Advanced Field Service Accredited Professional 온라인 연습
최종 업데이트 시간: 2026년02월14일
당신은 온라인 연습 문제를 통해 Salesforce AP-209 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 AP-209 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 46개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
To exclude a specific subset of resources from being scheduled by the optimization engine, you use a Hard Constraint Work Rule.
Option D is correct. The Match Boolean Work Rule is designed to filter resources based on a checkbox (Boolean) field.
You would create a custom checkbox on the Service Resource object (e.g., Is_Contractor__c).
You configure the Match Boolean rule in the Scheduling Policy to enforce that Is_Contractor__c must be False.
When optimization runs, any resource where Is_Contractor__c = True fails the rule and is completely ignored/excluded from the schedule calculation.
Option A (Count Rule) limits volume, it doesn't exclude.
Options B and C (Match Field/Extended Match) match properties between the Job and the Resource (e.g., Skill or Location matching), which is not the same as a blanket exclusion of a resource type.
정답: A, C
Explanation:
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).
정답:
Explanation:
The Dispatcher Console Map is the most efficient tool for geographic mass actions.
Option A is correct. Salesforce Field Service allows dispatchers to draw custom Map Polygons directly on the Gantt map. Once a polygon is drawn around the affected bushfire area, the dispatcher can right-click the polygon (or use the actions menu) to perform Mass Actions on all Service Appointments contained within that shape. "Unschedule," "Cancel," or "Flag" are standard bulk actions available in this context.
Option B (Reports/Data Loader) is too slow for an emergency response.
Option C (Optimization) would just move the appointments to later times, not cancel/unscheduled them.
Option D (List View) is difficult because defining a "bushfire area" using text filters (City, Zip) is often inaccurate compared to drawing the precise boundary on a map.
정답:
Explanation:
To send push notifications to the Field Service mobile app based on specific criteria, you need both the configuration and the automation.
Option B is correct: You must first enable and configure Custom Notifications for the Field Service Connected App. This ensures the mobile device is capable of receiving and displaying the specific notification type.
Option D is correct: You need an automation trigger (Record-Triggered Flow) to detect the specific business condition: The Service Appointment Status changes to 'Dispatched' AND the Priority (or Work Type) is 'Emergency'. The flow then executes the "Send Custom Notification" action targeting the Assigned Resource user.
Option A and C refer to "Jeopardy," which is a different feature used to warn dispatchers about impending SLA violations, not to notify technicians of new work.
정답:
Explanation:
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 the lowest skill 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.
정답:
Explanation:
This is the standard troubleshooting procedure for "Why wasn't this scheduled?".
Option A is correct. If there is white space, but the optimizer didn't use it, there is likely a Rule Violation (Hard Constraint) preventing it (e.g., The resource is missing a Skill, the Territory doesn't match, or the Travel Time is too long). Manually dragging the appointment to that specific spot on the Gantt triggers the rule validation logic, and the console will pop up a "Rule Violation" message telling you exactly which rule failed (e.g., "Match Skills Rule Violation").
Option B helps find valid slots, but it doesn't explain why the current white space is invalid.
Option C addresses scoring (Objectives), not hard constraints (Rules). If there was space, the objectives would just give it a low score, not prevent scheduling entirely (unless the score was 0, but Rule Violations are the more common culprit for unscheduled work).
정답:
Explanation:
The requirement is to schedule two distinct resources (a Human and a Vehicle) for the same job at the same time.
Option C is correct.
Vehicle as Service Resource: You must model the vehicle as a Service Resource (Type: Asset) to track its availability on the Gantt and prevent double-booking.
Complex Work (Same Start): To ensure the vehicle and the technician are booked together, you use
Complex Work dependencies. "Same Start" ensures that the vehicle appointment and the technician appointment are scheduled to begin simultaneously.
Options A and D are incorrect because Products are not scheduled. Consuming a product does not check if the vehicle is available at that specific time, potentially leading to double-booking the van.
Option B is incorrect because "Immediately Follow" implies a sequence (Technician finishes -> Vehicle starts), which is not how a shared ride/equipment scenario works.
정답:
Explanation:
Asset replacement and history in Salesforce are tracked using the Asset Relationship object. Options A and B are correct. The Asset Relationship object 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 replaced this asset (Option A).
Backward: See the old asset that this asset 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.)
정답:
Explanation:
This scenario describes a structured process with validation (Checklist + Data + Images).
Option A is correct. Work Plans are the standard, modern feature for checklists in Salesforce Field Service. A Work Plan consists of "Work Steps." These steps can be linked to a Flow, which provides a user-friendly wizard to capture specific data inputs and upload images in a structured way.
Option B is the legacy method. Adding fields directly to the Service Appointment creates clutter and
doesn't offer a step-by-step "Checklist" experience.
Option C is a security risk (too much access) and provides no process guidance.
Option D (Deep Linking) is used to jump out of the app to another app, which is not needed here since SFS can handle flows natively.
정답:
Explanation:
During the "Day 1" or Scoping phase of an implementation, the goal is to define the high-level architecture and business model.
A is correct: Defining Integration points (ERP, HR, Inventory) is a foundational requirement that dictates the project scope and data strategy.
D is correct: Defining the Work (Work Types, Skills, Durations) is the core of the Field Service data model. You cannot configure the system without knowing what services are being performed.
E is correct: Defining the Territory Structure (Business Units) sets up the security model, sharing settings, and resource organization.
Options B and C are incorrect for the first day because they are detailed configuration specifics (Refinement). You cannot define "Service Objective Weights" or "Gantt Features" until you understand the basic business goals, services, and territories.
정답:
Explanation:
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.
정답:
Explanation:
This requires a balance of data accuracy (tracking the asset) and schedule accuracy (updating the duration).
Option D is correct because it uses Field Service Mobile Flows, which is the best practice for guiding technicians through complex processes.
Data: Creating a Work Order Line Item (WOLI) is the correct data model to track work done on a specific (secondary) Asset under the main Work Order.
Schedule: The flow can update the current Service Appointment's Duration and Scheduled End to
reflect the reality that the tech will be there longer.
Automation: Triggering a "Scheduling Recipe" (now typically handled via Flows/Optimization services) ensures that if the appointment runs long, subsequent appointments for the day are automatically shifted (Reshuffled) to prevent overlapping/late arrivals.
Options A and C fail to update the schedule duration, meaning the tech will likely be late to their next job without the dispatcher knowing.
Option B creates a second appointment, which is administratively heavy for "just looking at" another asset during the same visit.
정답:
Explanation:
The goal is to fit high-priority work into a schedule already filled with low-priority work.
Option B is correct. The system must know that the Repair jobs are more important than the Maintenance jobs. This is handled by the Scheduling Priority field (used in the optimization logic to decide which job to drop if there is a conflict) or the Priority field mapped to Service Objectives.
Option C is correct. Global Optimization is the best tool here. It will look at the entire week, see the high-priority unscheduled jobs, and the low-priority scheduled jobs. It will then un-schedule or move the maintenance jobs to make room for the urgent repairs.
Option D is correct. For Optimization to work, the existing maintenance appointments must not be Pinned. If they are pinned, the optimizer treats them as immovable rock, and it won't be able to free up the time needed for the repairs.
Option A (Manual assignment) is inefficient and risky (could double-book).
Option E (Resource Schedule Optimization) optimizes one person at a time; Global Optimization is better suited for balancing the load across the whole territory.
정답:
Explanation:
Global Optimization is the heavy-lifting batch process in Salesforce Field Service designed to create the most efficient schedule possible.
Option B is correct. Global Optimization uses a powerful algorithm to evaluate millions of potential combinations of resources, times, and routes to find the best overall score based on the Service Objectives.
Option C is correct. Unlike "Appointment Booking" (which finds a slot for a single job without disturbing others), Global Optimization has the authority to reshuffle (move) existing appointments. It can slide jobs earlier or later, or reassess assignments to minimize travel time and white space (gaps) in the schedule.
Option A is incorrect; Optimization is a batch process that takes significantly longer than the near real-time "Auto Scheduling."
Option D describes "In-Day Optimization." Global Optimization is typically run overnight because it changes the whole schedule, which is disruptive during the work day.
Option E is incorrect; all scheduling methods (Global, In-Day, Resource Schedule Optimization, and Appointment Booking) utilize the Scheduling Policy (Work Rules and Objectives).
정답:
Explanation:
This scenario requires managing availability for resources who work across multiple territories (Primary and Secondary memberships) specifically for "off-hours" emergencies.
Option D is correct because Shifts in Salesforce Field Service allow you to define ad-hoc availability outside of standard Operating Hours. Crucially, if you create a Shift without specifying a Service Territory, that availability applies to the resource's Primary Territory by default. However, because the resource also holds Secondary Territory Memberships for the other business units, the scheduling engine (specifically the "Match Territory" Work Rule) recognizes this availability as valid for those territories as well, provided the shift falls within the membership dates.
Setting the Time Slot Type to 'Designated' (or 'Extended') is the standard way to mark time for specific work types (like Emergencies) using Work Rules that filter on those time slot types.
Option B is incorrect because creating a separate shift for every territory is administrative overhead and unnecessary when a single non-territory-specific shift can cover the resource's availability across their memberships.
Option A is factually incorrect; resources can have multiple territory memberships.