Pottery Line Needs a Product Master with Variants

MB-330 By islever Editorial Last updated

Create and manage products Manage inventory pricing and costing

Short answer

C Create a product master with pre-defined variants so the pottery line gets Orange and Red colors sharing one cost.

Question

You need to configure the system to support the pottery line.
What should you do first?
  1. Set up a new product with product configuration.
  2. Create a new product with tracking dimensions.
  3. Create a new product master with pre-defined product variants. Correct Answer
  4. Create a new product with storage dimensions.

Key Takeaways

The question tests whether you build the foundational product master with pre-defined variants before applying product, tracking, or storage dimensions — the trap is treating a variant product as a plain new product.

The MB-330 pottery scenario needs one product master with pre-defined Orange and Red color variants sharing a single cost, making option C the first step to configure.

Common mistake: Option A is the most tempting trap: choosing product configuration suggests modelling the two colors as a configuration, but product configuration is for constraint-based configure-to-order items and is unnecessary for simple pre-defined color variants.

Expert Analysis

The qualifier "first" drives this question. The stem asks what to do first to support the pottery line, so the answer must be the foundational record that everything else hangs from — not a downstream attribute, dimension, or costing detail. Only option C creates that foundation: a single product master that will later carry the Color dimension and the Orange and Red variants.

Why the pottery scenario forces a product master. The pottery must be sold in two colors that share the same cost. In Dynamics 365 SCM, one physical item with several values of a single product attribute is modelled as a product master with pre-defined (product dimension) variants, and cost can be kept common across those variants. That is exactly option C, and the supporting commentary reaches the same conclusion: create the product master, enable Color, define Orange and Red as pre-defined variants, and keep one cost.

Why A is wrong. "Product configuration" is the constraint-based, configure-to-order/engineered-product capability (configuration models, constraint rules, and a configured BOM). The pottery line is a simple two-color choice, not an engineered configuration, so A reaches for a heavyweight feature that is neither required nor first.

Why B and D are wrong. Tracking dimensions (batch/serial) and storage dimensions (site/warehouse/location/bin/pallet) are attributes you assign after a product master exists; neither produces the required Orange and Red values, and neither addresses the color attribute at all. Choosing a plain "new product" also skips the variant structure the scenario demands.

Therefore the first action is option C: create a product master with pre-defined product variants.

Exam Strategy

When a stem asks what to do "first", look for the foundational record — a product master, item template, or base setup — and treat dimensions, attributes, and costing as later steps. Also read for a repeated attribute with a shared cost: that pattern signals a product master with pre-defined product variants, which lets you discard configure-to-order and single-dimension answers quickly.

Frequently Asked Questions

Why use pre-defined variants instead of creating two separate pottery products?

Pre-defined variants keep one product master, one item number, and shared costing while the Color dimension carries Orange and Red. Two separate products would duplicate setup and break common inventory and cost reporting.

Do the Orange and Red pottery variants need separate cost records?

No. The scenario states the same cost regardless of color, so both pre-defined variants can share one cost. You would split costs only if a dimension genuinely drove different material or labor cost.

What is the difference between product configuration and product variants?

Pre-defined variants are fixed combinations of product dimensions such as Color, Size, or Style chosen at order entry. Product configuration is constraint-based configure-to-order for engineered products built from a configuration model and rules.

More MB-330 FAQ →

Community Votes

C
100%

100% of anonymous learners picked answer C. 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.

From public community threads 3

  1. Gemami 👍 1 Answered C
    Correct answer: C. Create a new product master with pre-defined product variants. Why? The pottery must be available in two colors: orange and red, with the same cost regardless of color. In Dynamics 365 SCM, you can: - Create one product master for the pottery. - Enable the Color product dimension. - Create two predefined variants: Orange and Red. - Use the same cost for both variants. Why not the others? - A. Product configuration: Intended for configurable products, typically involving more complex configuration requirements. - B. Tracking dimensions: Used for batch and serial number tracking. - D. Storage dimensions: Used for site, warehouse, location, etc.
  2. python123 👍 1
    It is correct
  3. Kev_Sharp 👍 1 Answered C
    Correct

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Configure Asset Management for Fuel and Maintenance in Dynamics 365

S-grade

Configuring ABC Model Codes in Dynamics 365 SCM

S-grade

Dynamics 365 SCM Maintenance Round vs Plan

S-grade

Configuring Exporter Reporting for Shipments in D365 SCM

S-grade

← Back to MB-330 Study Guide