MB-330 Implement Inventory and Asset Management Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Create a product variant for each expiration date and use variant-specific inventory.

  Why it's wrong here

  Product variants represent size, color, or style combinations, not time-based attributes like expiration. Creating a variant per expiration date would explode the product master and still would not provide the native batch expiration field the system uses for FEFO reservation and shelf-life reporting.

• ✗

  Enable only the Serial number dimension in the tracking dimension group and record expiration dates on the serial number.

  Why it's wrong here

  Serial numbers identify individual units, not groups of items received together, and they do not natively carry an expiration date field used for FEFO reservation. This setup would track each piece separately and would not support batch-level expiration reporting or batch reservation strategies.

• ✗

  Enable the Location dimension in the tracking dimension group and store expiration dates on the warehouse location.

  Why it's wrong here

  The Location dimension tracks physical storage positions, not item instances. An expiration date belongs to a specific batch of an item, not to a bin, and storing it on the location would prevent the system from distinguishing batches with different expiry dates stored in the same location.

• ✓

  Enable the Batch dimension in the item's tracking dimension group and set the expiration date to be managed per batch.

  Why this is correct

  Batch tracking requires the Batch dimension to be active in the tracking dimension group assigned to the item. Once active, batch numbers can be captured on receipts and issues, and the batch can carry an expiration date, enabling expiration-aware picking such as FEFO.