Does Cycle Counting Grouping Configure Scheduled and Threshold Cycle Counts?
Short answer
B Worker/location groupings only define who counts and where; weekly scheduling and below-threshold triggers require cycle count plans.
Question
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear on the review screen.
A company is implementing Dynamics 365 Supply Chain Management.
The warehouse manager manually creates item cycle counts for the workers to complete. The manager plans to use cycle counting capabilities available in Warehouse management to better manage inventory processes.
The system must be configured to do the following:
• Create scheduled cycle counts for workers to complete each week.
• Automatically create cycle counts when inventory falls below set levels.
You need to configure the system.
Solution: Configure cycle counting groupings for specific workers and warehouse locations.
Does the solution meet the goal?
Key Takeaways
Tests the distinction between cycle counting groupings (worker/location scope) and cycle count plans (timing, frequency and below-threshold triggers) — the trap is assuming groupings generate counting work automatically.
In Dynamics 365 Supply Chain Management, cycle counting groupings only assign who performs counts and in which warehouse locations, so they cannot schedule weekly counts or trigger counts when on-hand inventory drops below a threshold. This page confirms the proposed solution does not meet the stated goals.
Common mistake: Selecting "Yes" because groupings sound like a complete cycle counting configuration; learners forget that the weekly schedule and the inventory-below-threshold trigger must come from a cycle count plan, not from the worker/location grouping.
Expert Analysis
Why the Answer Is Correct
The requirement has two distinct triggers: a recurring weekly schedule and an automatic count when inventory falls below a defined level. In Warehouse management, the record that defines when counting work is generated is the cycle count plan: it carries the frequency (for example, a weekly interval) and the threshold settings that create count work when on-hand quantity drops below the configured level. Cycle counting groupings only answer a different question — which workers handle the count and which warehouse locations are in scope for that grouping. Because the proposed solution configures groupings alone, neither the weekly schedule nor the low-inventory trigger exists, so the goal is not met. The correct approach is to set up cycle count plans (with frequency and threshold criteria) and then optionally use groupings to distribute the resulting count work to the right workers.
Why the Other Options Are Wrong
Answer A ("Yes") would only be defensible if groupings themselves generated counting work on a schedule or from a stock-level condition, and they do not — they are an assignment/scoping mechanism. Groupings have no frequency field and no on-hand threshold logic, so no weekly counts and no automatic below-level counts would ever be created. Selecting "Yes" also leaves the warehouse manager still manually creating counts, which is exactly the process the company wants to eliminate. The only configuration that satisfies both stated bullets is a cycle count plan, optionally combined with work pools/groupings for routing.
Community Comment Notes
As CCexamn explained, groupings determine who and where cycle counting happens but "they do not establish the required automatic triggers." The same commenter also contrasted related setup pieces such as deviation limits, which govern acceptable differences between expected and counted quantities rather than creating counts, and work pools, which organize warehouse work rather than deciding when cycle counting work is generated. The shared conclusion is that cycle count plans are the missing element for both the weekly schedule and the below-threshold trigger.
Official Reference
https://learn.microsoft.com/en-us/dynamics365/supply-chain/warehousing/cycle-counting
This link opens the official vendor documentation in a new tab.
Exam Strategy
When a "Solution:" statement names only a scoping or assignment record (groupings, work pools, worker assignments), check whether it actually addresses every stated trigger — scheduling and threshold-based creation usually require a cycle count plan, so the answer is "No."
Frequently Asked Questions
Which configuration creates weekly scheduled cycle counts in Warehouse management?
Why don't cycle counting groupings trigger counts when inventory falls below a level?
Discussion 2 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 2
-
CCexamn 👍 1 Answered BAnswer: B. No The solution does not meet the goal. - Deviation limits control acceptable differences between the expected quantity and the counted quantity. They don't trigger cycle counting when inventory falls below a threshold. - Work pools organize/group warehouse work; they don't determine when cycle counting work is created. To meet the requirements, you need cycle count plans: - Weekly scheduled counts → configure a cycle count plan with a recurrence/schedule. - Count when inventory falls below a set level → configure the cycle count plan using a threshold (for example, quantity or percentage threshold) to trigger cycle counting work.
-
CCexamn 👍 1 Answered BAnswer: B. No Cycle counting groupings for workers/locations determine who/where cycle counting is performed, but they do not establish the required automatic triggers.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.