Configure Asset Management for Fuel and Maintenance in Dynamics 365
A manufacturing company uses Dynamics 365 Supply Chain Management. The company replaced its burners to limit carbon dioxide emissions. The new burners require frequent servicing to be compliant with environmental regulations. The new burners are more complex and take longer to service than the previous burners. The production controller must track fuel use in liters to schedule timely maintenance. The additional time taken to plan maintenance must be considered. You must configure the system to meet the requirements. Which two actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
Community Votes
67% of anonymous learners picked answer AD. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The core concept is linking physical asset metrics (fuel liters) to maintenance schedules using counters, while handling complex service requirements through attributes rather than simple BOMs.
This question addresses configuring asset management in Dynamics 365 Supply Chain Management to track fuel consumption and adjust maintenance planning times. The correct solution involves setting up counter types for usage tracking and creating attributes to capture specific maintenance data.
Many candidates select 'Register consumption' and 'Configure asset BOM', likely due to a misunderstanding of how consumption is tracked versus how it is configured, and confusing BOMs with attribute definitions.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The scenario requires two distinct configurations: tracking fuel use in liters to schedule maintenance and accounting for additional planning time. Configuring counter types allows the system to define 'liters' as a measurable unit linked to an asset, enabling automatic triggers for maintenance based on consumption thresholds. Creating attributes allows you to define custom properties or flags on the asset or maintenance activity, such as 'complexity level' or 'additional time required,' which can then be used in planning rules or simply recorded for compliance.Why the Other Options Are Wrong
Registering consumption (A) is an action performed during operation, not a configuration step to enable the tracking capability itself; the counter must exist first. Setting up asset service level (C) defines performance metrics like uptime, not the scheduling logic based on fuel volume. Configuring an asset BOM (D) lists the components required for repair but does not inherently track the consumption of fuel to trigger that repair or store the time complexity as a schedulable parameter.Community Comment Notes
One user argued for AD, stating that registering consumption tracks fuel and the BOM accounts for it, but this conflates the transactional act with the setup requirement. Another user correctly identified BE, noting that counters handle the 'liters' requirement and attributes handle the 'additional time' complexity. A third commenter suggested AC, missing the nuance that service levels are for SLAs, not operational scheduling triggers.Exam Strategy
Always distinguish between 'configuration' steps (setting up counters, attributes, BOMs) and 'transactional' actions (registering consumption). When a question asks to 'track' something to 'schedule' maintenance, look for Counter Types first. When it mentions 'additional time' or 'complexity' affecting planning, look for Attributes.
Frequently Asked Questions
Why isn't Register Consumption the correct configuration?
Registering consumption is a transactional action taken when fuel is actually used. To 'track' it for scheduling, you must first configure the Counter Type that defines what is being measured.
Can Asset BOM handle the additional planning time requirement?
No. An Asset BOM lists the parts needed for repair. It does not store metadata about the complexity or duration of the service, which is best handled by Attributes.