Configure Asset Management for Fuel and Maintenance in Dynamics 365
Short answer
BE Configure counter types to track fuel usage in liters and create attributes to account for additional maintenance planning time.
Question
Key Takeaways
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.
Common mistake: 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.
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.
Community Votes
67% of anonymous learners picked answer AD. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 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, not of islever. The comments shown first are the most substantive of the thread — ranked by depth, community endorsement and relevance; expand the list below to read the rest.
From public community threads 3
-
Elyse0814 👍 2I feel like the answer is correct. Register consumption for the fuel and configure an asset bom to track/account for that consumption. https://learn.microsoft.com/en-us/dynamics365/supply-chain/asset-management/objects/object-bom
-
globeearth 👍 1B. Configure counter types - This configures the system to track fuel use in liters (e.g., a “Fuel Consumption” counter) and link it to a maintenance plan (e.g., service every 1,000 liters). It ensures timely maintenance scheduling based on usage, directly meeting the first requirement. E. Create attributes - This configures the system to account for the additional planning time due to the burners’ complexity. An attribute like “Estimated Service Time” (e.g., 4 hours) can be added to the asset and used in planning processes, meeting the second requirement. Why not A and D. A. Register consumption: This is an operational step, not a configuration action. It happens after maintenance, not as a setup for fuel tracking or time planning. D. Configure asset BOM: While useful for defining the burners’ parts and tracking their consumption post-maintenance , it doesn’t directly track fuel use (an operational metric) or address planning time.
-
Jeddai 👍 5Shouldn't it be A and C ?
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.