Salesforce AP-209 Exam - Topic 1 Question 5 Discussion

Actual exam question for Salesforce's AP-209 exam

Question #: 5
Topic #: 1

A division of Green Energy Solutions has different work hours for each day, and the daily hours are inconsistent from one week to another (example: this Monday 9 am-4 pm, this Tuesday 8 am-6 pm, next Monday 8 am-3 pm, next Tuesday 9 am-2 pm). This creates a lot of overhead.

What can an administrator configure to add efficiencies into their scheduling process and mitigate administrative overhead?

ACreate Operating Hours for all combinations and build a workflow to change the Service Territory Operating Hours every week

BCreate Operating Hours with no availability, and use Shifts to define the daily changing availability

CCreate Operating Hours that encompasses all the hours, then create non availabilities for the hours that are off on a given day

DCreate a Service Territory with Operating Hours that encompasses all the hours, then create jobs for the specific hours needed to be covered

Show Suggested Answer

Suggested Answer: B

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.

by Jacqueline at Dec 17, 2025, 07:12 AM

Limited Time Offer

25%

Off

Get Premium AP-209 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Princess

5 days ago

I agree, B seems efficient. Shifts can handle daily changes well.

upvoted 0 times

...

Jolanda

10 days ago

This question is tricky! I think option B makes sense.

upvoted 0 times

...

Bambi

15 days ago

D could work, but it sounds like a lot of extra work.

upvoted 0 times

...

Marjory

20 days ago

A is too complicated for weekly changes.

upvoted 0 times

...

Luis

25 days ago

Surprised they haven't streamlined this already!

upvoted 0 times

...

Sherman

1 month ago

I disagree, C might be more straightforward for tracking.

upvoted 0 times

...

Makeda

1 month ago

I’m leaning towards option D since it allows for a broader coverage, but I wonder if creating jobs for specific hours could become cumbersome.

upvoted 0 times

...

Ilona

2 months ago

I practiced a similar question where we had to balance flexibility and efficiency. I feel like option A could lead to too much complexity with all those workflows.

upvoted 0 times

...

Tamesha

2 months ago

I think option C sounds familiar; it seems like a good way to manage the inconsistencies by setting non-availability for specific hours.

upvoted 0 times

...

Dion

2 months ago

I remember discussing how creating Operating Hours with no availability might simplify things, but I'm not sure if that's the best approach for fluctuating schedules.

upvoted 0 times

...

Tamala

2 months ago

I'm with Onita on this one. Option B seems like the sanest choice to deal with this scheduling chaos.

upvoted 0 times

...

Onita

3 months ago

Haha, this question is a scheduling nightmare! Option B sounds like the best way to wrangle those inconsistent work hours.

upvoted 0 times

...

Eve

3 months ago

Option D is the way to go. Creating a Service Territory with broad Operating Hours and then specific jobs for the needed coverage hours is a smart solution.

upvoted 0 times

...

Abraham

3 months ago

I like option C. Creating Operating Hours that encompass all the hours and then using non-availabilities for the off hours is a simple and straightforward approach.

upvoted 0 times

...

Tomas

3 months ago

This is a tricky one, but I think option B is the way to go. Being able to define the daily shifts separately, rather than trying to manage a bunch of different operating hour configurations, seems like it would be the most efficient solution.

upvoted 0 times

...

Zack

3 months ago

I'm leaning towards option D. Creating a service territory with operating hours that cover the full range, and then just scheduling specific jobs for the hours that need to be covered, seems like it would be the most flexible and low-maintenance approach.

upvoted 0 times

...

Chaya

4 months ago

Option C seems like it could work well. Creating operating hours that encompass all the possible hours, and then using non-availabilities to block off the hours that aren't needed on a given day, could be a good way to streamline the process.

upvoted 0 times

...

Raylene

4 months ago

I'm a little confused by this question. Do we need to create a new set of operating hours for each day, or can we use a more general set of hours and then define the specific availability for each day? I'm not sure which option would be the most effective.

upvoted 0 times

...

Mari

4 months ago

Option B seems like the most efficient solution. Using Shifts to define the daily changing availability is a great way to handle the inconsistent work hours.

upvoted 0 times

...

Rene

4 months ago

I think option B might be the best approach here. Creating shifts to define the daily changing availability seems like it would be the most efficient way to handle the inconsistent work hours.

upvoted 0 times

...

Darnell

4 months ago

Option B seems like the best way to handle daily changes.

upvoted 0 times

...