MB-335 · Question #239
Drag and Drop Question A company is implementing repair management for its Dynamics 365 Supply Chain Management. A customer reports that a specific laptop computer fan increases in speed. When the…
The correct answer is Symptom code; Condition; Symptom area; Diagnosis area. Dynamics 365 SCM Repair Management - Component Explanation The Scenario Broken Into 4 Issues The scenario describes a laptop with a fan problem, which maps to four distinct documentation needs: | # | Issue Being Documented | Component Used |…
Question
Drag and Drop Question A company is implementing repair management for its Dynamics 365 Supply Chain Management. A customer reports that a specific laptop computer fan increases in speed. When the fan reaches maximum speed, the computer shuts down unexpectedly and will not reboot for several hours. The company must configure repair management components to address this and similar scenarios for diagnosis and repair. You need to configure each repair management component to properly document the scenario. Which component should you use for each issue? To answer, move the appropriate components to the correct issues. You may use each component once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Answer:
Exhibit
Answer Area
Drag items
Correct arrangement
- Symptom code
- Condition
- Symptom area
- Diagnosis area
Explanation
Dynamics 365 SCM Repair Management - Component Explanation
The Scenario Broken Into 4 Issues
The scenario describes a laptop with a fan problem, which maps to four distinct documentation needs:
| # | Issue Being Documented | Component Used |
|---|---|---|
| 1 | The specific observable symptom ("fan increases in speed") | Symptom code |
| 2 | The state the device is in ("shuts down, won't reboot for hours") | Condition |
| 3 | The broad category the symptom belongs to (e.g., cooling/thermal) | Symptom area |
| 4 | The category technicians use to investigate root cause | Diagnosis area |
Individual Placement Reasoning
1. Symptom code A symptom code is a specific, granular symptom the customer reports - here, "fan speed increases abnormally." It lives within a symptom area. This is the discrete, codeable event the technician logs, not a broad classification.
2. Condition Condition captures the state the item is in when received. "Shuts down unexpectedly and won't reboot for several hours" describes the device's observable condition - not the symptom itself but what state resulted from it. Common mistake: confusing this with symptom. A symptom is what the customer notices happening; a condition is the state the item is in.
3. Symptom area Symptom area is the parent grouping for symptom codes - think of it as the category header (e.g., "Cooling System" or "Hardware - Fan"). It sits above the symptom code in the hierarchy. Common mistake: mapping the specific fan speed issue here - that's too specific for an area, which should be a broader classification.
4. Diagnosis area Diagnosis area is the technician-facing grouping for diagnoses (e.g., "Thermal Management"). It classifies what kind of diagnosis will be performed, not the result. Common mistake: conflating diagnosis area with a specific diagnosis code - the area is just the category.
Key Hierarchy to Remember
Symptom area → contains → Symptom codes (customer-reported)
Diagnosis area → contains → Diagnosis codes (technician-assigned)
Condition (state of the item)
Conditions are standalone - they don't nest under symptom or diagnosis hierarchies. Diagnosis area and symptom area are both containers, while symptom code and diagnosis code are the specific entries within them.
Topics
Community Discussion
No community discussion yet for this question.