MB-335 · Question #151
Drag and Drop Question A discrete manufacturer uses the time and attendance registration for production operations. All employees register daily dock in and clock out times during a 40-hour. Monday th
The correct answer is Create a batch attribute, acid, of type fraction.; Define acid as a product-specific batch attribute on item B0001.; Add the customer-specific batch attribute on item B0001 for the customer and configure the range to 5.5 to 10.5.. Important Note: Question/Answer Mismatch The scenario describes a time and attendance / payroll configuration question, but the available items and correct arrangement are about batch attribute configuration (likely Microsoft Dynamics 365 Supply Chain Management). These belong to
Question
Exhibit
Answer Area
Drag items
Correct arrangement
- Create a batch attribute, acid, of type fraction.
- Define acid as a product-specific batch attribute on item B0001.
- Add the customer-specific batch attribute on item B0001 for the customer and configure the range to 5.5 to 10.5.
Explanation
Important Note: Question/Answer Mismatch
The scenario describes a time and attendance / payroll configuration question, but the available items and correct arrangement are about batch attribute configuration (likely Microsoft Dynamics 365 Supply Chain Management). These belong to two different questions that have been incorrectly combined. The explanation below addresses the actual answer options as given.
What This Answer Set Is Actually About
This is a batch attribute configuration question for a process manufacturing scenario. A customer requires item B0001 to have an acid percentage within a range of 5.5–10.5. You need to configure this in D365 SCM.
The Correct Arrangement Explained
Step 1: Create a batch attribute, acid, of type fraction
Why first: You must define the batch attribute itself before it can be assigned to anything. "Fraction" is the correct type because acid percentage is a decimal/numeric value (e.g., 7.5%), not a predefined list of choices. This is the foundational global setup step - the attribute doesn't exist in the system until this is done.
Common mistake: Choosing "type string" instead. String type is for text-based enumeration values (e.g., "Low/Medium/High"), not numeric ranges. Using string would prevent you from setting a numeric min/max range like 5.5–10.5.
Step 2: Define acid as a product-specific batch attribute on item B0001
Why second: Once the attribute exists globally, you associate it with the specific product (B0001). This tells the system that this item tracks the acid attribute. Without this step, the attribute is unlinked to any product and cannot be used for inventory or quality purposes on B0001.
Common mistake: Skipping this step and going straight to customer-specific configuration. The product-level association must exist before a customer-specific override can be layered on top of it.
Step 3: Add the customer-specific batch attribute on item B0001 for the customer and configure the range to 5.5 to 10.5
Why third/last: This is the most specific layer. Customer-specific batch attribute requirements override or narrow the product-level defaults. Only after the attribute exists (Step 1) and is linked to the product (Step 2) can you define a per-customer acceptable range. This follows D365's hierarchy: global attribute → product assignment → customer-specific requirement.
Common mistake: Treating the customer range as a global rule. It must be scoped to both the item and the customer, which is only possible after Steps 1 and 2 are complete.
Why the Other Items Are Excluded
| Item | Why Excluded |
|---|---|
| Create a batch attribute of type string | Wrong type - acid percentage requires numeric fraction, not enumerated text |
| Define allowable acid percentage-based enumeration values | Enumeration applies to string-type attributes; irrelevant here since we chose fraction |
Key Principle
The ordering follows a strict general → specific hierarchy:
Define the attribute → Attach to product → Customize for customer
Each step is a prerequisite for the next. You cannot assign what doesn't exist, and you cannot customer-restrict what isn't product-assigned.
Topics
Community Discussion
No community discussion yet for this question.
