Free Microsoft MB-335 Practice Test Questions MCQs

Explanation:
The question requires Kanbans to be automatically registered as empty as soon as the last job on the production order is completed. This is a critical step in a pull system to signal upstream processes that more material is needed. You need to configure the Kanban rule to trigger this "empty registration" automatically at the point of consumption or completion, rather than relying on a manual scan by an operator.

Explanation of Correct Option:

B. Select to register as empty when handling units are received.
This is the correct setting. In the Kanban rule, the "Register as empty" option dictates when the empty registration occurs. Selecting "When handling units are received" means that as soon as the finished handling unit (the completed product) is registered as received against the picking list or job, the source Kanban is automatically marked as empty. This aligns perfectly with the requirement for automatic registration upon job completion.

Explanation of Incorrect Options:

A. Set a fired Kanban quantity.
This option is used to define how many Kanbans are triggered by a planning event or manually. It controls the quantity, not the trigger for automatically emptying a Kanban.

C. Select to register as empty when the source requirement is registered.
This setting would empty the Kanban only when the upstream source (like a production order) is registered as finished. This is not the same as the "last job" of the consuming Kanban being completed.

D. Select to manually register as empty.
This would require the operator to physically scan or click a button to mark the Kanban as empty. The requirement specifically states the process must be "automatic," making this option incorrect.

Reference:
Microsoft Learn: Set up Kanban rules for manufacturing (Specifically the "Register as empty" field settings)

Explanation:
The question asks about ensuring that the working time calendar is used when scheduling manufacturing jobs. Disabling route groups for a process job type does not influence whether the system respects working time calendars during scheduling. Working time calendars are primarily controlled by scheduling methods, resource configurations, and calendar settings, not by route group configurations.

Explanation of Correct Option:

B. No.
This is correct because route groups define how operations are split into individual jobs (like process, queue, setup, or transport) and which run time categories apply. They do not control whether working time calendars are considered during scheduling. The working time calendar is applied through resource and calendar associations, and through the scheduling method (operations scheduling or job scheduling) selected.

Explanation of Incorrect Option:

A. Yes.
This is incorrect because route groups are unrelated to working time calendar enforcement. Route groups primarily determine job types, job dependencies, and how operations are broken down into detailed jobs. Disabling them would impact job splitting and categorization, but would have no effect on calendar-based scheduling constraints. The working time calendar usage is determined by resource calendar assignments and scheduling parameters.

Reference:

Microsoft Learn: Working with calendars in Dynamics 365 Supply Chain Management

Microsoft Learn: Route groups in manufacturing

Explanation:
The scenario describes process manufacturing with ingredients delivered at different concentrations, requiring compensation during production. The solution incorrectly suggests using catch weight for IngredientA. Catch weight is designed for products that vary in weight but are sold/purchased differently (like produce), not for potency or concentration variances. For concentration variations, potency management is the appropriate feature.

Explanation of Correct Option:

B. No.
This is correct because catch weight handles discrepancies between inventory units (weight) and sales units (pieces), not ingredient concentration variances. Potency management is the feature designed specifically for this scenario. It allows tracking active ingredient percentages and automatically calculates compensating ingredient quantities (like IngredientB) to ensure final product specifications are met regardless of received concentration variations.

Explanation of Incorrect Option:

A. Yes.
This is incorrect because catch weight does not address concentration or potency variations. Catch weight manages products where the weight varies but the item is tracked and sold differently (like cheese or meat). For pharmaceutical or chemical ingredients with varying concentrations, potency management must be configured, which tracks the actual potency percentage and enables automatic compensation calculations during batch order processing.

Reference:

Microsoft Learn: Potency management for process manufacturing

Microsoft Learn: Catch weight products overview

Explanation:
The scenario involves expensive, bulky items with seasonal availability, requiring precise replenishment to avoid excess inventory. The company needs to maintain inventory levels while managing space constraints. Among coverage dimensions, "Period" is designed to aggregate demand within a specific time frame, allowing for consolidated ordering while preventing overstocking. This balances availability with inventory carrying costs.

Explanation of Correct Option:

A. Period.
This is the correct answer. Period coverage aggregates all requirements within a defined period (such as a week or month) into a single planned order. For expensive aluminum sheets with limited availability windows, this allows the company to order enough to cover the entire period's demand in one shipment, minimizing inventory holding costs and space usage while ensuring material availability during seasonal supply windows.
Explanation of Incorrect Options:

B. Manual.
This coverage group requires planners to manually initiate replenishment orders. While it provides maximum control, it would not optimize inventory levels for seasonally available items and increases administrative burden. Manual replenishment might lead to missed ordering windows or inconsistent inventory levels.

C. Min/Max.
This maintains inventory between minimum and maximum levels based on historical consumption. For seasonally available items, this could trigger orders when inventory drops below minimum, potentially outside the supplier's availability window. It also tends to maintain higher safety stocks, conflicting with space constraints.

D. Requirement.
This creates planned orders for each individual demand (sales order or production order). This would result in frequent small orders, increasing freight costs and potentially missing supplier availability windows. It also increases receiving frequency, which may not align with seasonal supply patterns.

Reference:

Microsoft Learn: Master planning coverage settings

Microsoft Learn: Coverage codes in master planning (Period, Requirement, Min/Max, Manual)

Explanation:
The requirement states that products must be removed from on-hand inventory when they are picked and staged for production, not when they are physically consumed on the production line. This means inventory consumption should occur at the staging location immediately upon picking. The flushing principle determines when materials are deducted from inventory during the production process.

Explanation of Correct Option:

B. flushing principle, available at location.
This is correct because the "Available at location" flushing principle consumes materials when work is completed to move inventory to a production input location (staging). This aligns perfectly with the requirement: when workers pick and stage batch-tracked products, the system immediately removes them from on-hand inventory upon arrival at the staging location, even before actual production consumption.

Explanation of Incorrect Options:

A. mobile device menu item, start production order.
This option configures a menu item to begin a production order but does not control when materials are consumed. Starting a production order does not automatically flush materials; it only changes the order status and may enable additional warehouse transactions.

C. flushing principle, start.
The "Start" flushing principle consumes materials when the production order status is updated to "Started." This typically occurs at the beginning of production, not when items are picked and staged, which is earlier in the process and doesn't meet the staging requirement.

D. manufacturing execution, job card device.
The job card device is used for registering time, quantity, and progress on production jobs. While it can trigger material consumption, it requires manual registration at the production machine, not automatically when items are staged, and does not address the warehouse staging requirement.

Reference:

Microsoft Learn: Flushing principles in manufacturing

Microsoft Learn: Register material consumption in production

Explanation:
The scenario requires a notification mechanism when customer service selects a prototype product version that is not yet operational on sales orders. Product lifecycle states in engineering change management provide exactly this functionality by controlling which product versions are available for different business processes and displaying warnings or blocking transactions for non-operational versions.

Explanation of Correct Option:

C. product lifecycle states.
This is correct because product lifecycle states allow companies to control which transactions are permitted for each product version throughout its lifecycle. For prototype versions, you can configure the lifecycle state to be "Not operational" and set it to block sales order creation or display warnings. When customer service selects a prototype version, the system will trigger the configured notification or block the transaction.

Explanation of Incorrect Options:

A. engineering product category.
This defines the default values, attributes, and policies for a class of engineering products. While it determines which lifecycle states are available and how versions are managed, it does not directly control transaction blocking or notifications for prototype versions on sales orders.

B. version number rule.
This defines the naming convention and numbering format for product versions. It ensures consistent version identification but has no functionality to restrict or warn about prototype versions being selected on sales transactions.

D. product release policy.
This controls how engineering products are released to legal entities, including which attributes are transferred and whether products are automatically released. It manages the release process but does not provide transaction-time notifications or blocks for prototype versions.

Reference:

Microsoft Learn: Product lifecycle states overview

Microsoft Learn: Engineering change management lifecycle states

Explanation:
The scenario involves a critical machine breakdown during production, with completed quantities ready to ship and remaining work pending repair. Since negative inventory is not allowed, you cannot ship unproduced items. You need a solution that finalizes the completed portion while creating a new order for the remaining quantity once machinery is operational.

Explanation of Correct Option:

C. End the current production order and create a new order for the remaining quantity.
This is correct because ending the production order reports the completed quantity as finished and closes the order. You can then ship that quantity. The remaining quantity requires a new production order that will be scheduled after machinery repair. This approach maintains inventory accuracy without negative inventory and properly tracks production costs separately.

Explanation of Incorrect Options:

A. Split the current production order into two production orders.
Dynamics 365 does not support splitting an active production order into multiple orders. You cannot divide an existing order; you must handle completed quantities through reporting and create new orders separately for remaining work.

B. Ship the production quantity that is reported as finished.
While you can ship completed quantities, this alone does not address the remaining quantity on the original order. The production order would remain open with outstanding quantity, causing confusion and potentially affecting planning.

D. Cancel the production order and create a new order for the finished quantity.
Canceling voids the entire order, including completed work. You would lose tracking of completed quantities and associated costs. The finished items would need to be received again through a new order, creating duplicate records and costing issues.

Reference:

Microsoft Learn: Production order lifecycle

Microsoft Learn: Report production orders as finished

Explanation:
The scenario requires including 50 components in a finished good's BOM without listing them individually and without generating a separate production order for the kit. The phantom BOM concept is designed exactly for this purpose, where the kit item explodes its components directly into the parent BOM during production processing.

Explanation of Correct Option:

A. Select Phantom on the engineering fast tab on the kit item.
This is correct because setting the kit item as a phantom BOM ensures that when used in a parent BOM, the phantom item's components are exploded directly into the production order. No separate production order is created for the phantom item, and all 50 components appear on the picking list for the finished good, meeting both requirements.

Explanation of Incorrect Options:

B. Change the coverage group on the kit item to Manual.
Coverage groups control master planning replenishment logic, not BOM explosion behavior. Manual coverage would affect how the kit item is planned but would not prevent a separate production order when included in a parent BOM.

C. Change the line type to Pegged supply.
Pegged supply links a BOM line to a specific purchase order or production order for direct supply. It does not prevent the kit item from generating its own production order when included in a parent BOM.

D. Change the line type to Phantom.
While this mentions "Phantom," the option incorrectly identifies it as a line type. Phantom is an item setting on the engineering tab, not a BOM line type. BOM line types include Item, Vendor, and Pegged supply, but not Phantom.

Reference:

Microsoft Learn: Phantom BOMs overview

Microsoft Learn: BOM line types in manufacturing

Explanation:
The scenario involves canceled sales orders due to negative product reviews, which reduces the overall demand for the product. When demand decreases, existing planned production orders may exceed the new requirements. Action messages in master planning suggest adjustments to existing planned orders to align with changed demand.

Explanation of Correct Option:

C. Decrease.
This is correct because decrease action messages suggest reducing the quantity of existing planned orders when demand drops. With multiple sales orders canceled, the previously created planned production orders now have quantities that exceed actual need. The decrease action message will recommend reducing these planned order quantities to match the new, lower demand levels.

Explanation of Incorrect Options:

A. Increase.
This action message suggests increasing planned order quantities when demand exceeds supply. Since sales orders are being canceled, demand is decreasing, not increasing, making this inappropriate.

B. Postpone.
This action message suggests delaying planned orders when demand shifts later in time. While demand may have decreased, the requirement is to reduce quantities, not delay them. Postponement addresses timing, not quantity reduction.

D. Derived actions.
This refers to actions that cascade from one planned order to related orders. It is not a specific action message type but rather a relationship between actions on different orders.

E. Advance.
This action message suggests moving planned orders earlier when demand occurs before the current planned date. This addresses timing acceleration, not quantity reduction from canceled demand.

Reference:

Microsoft Learn: Action messages in master planning

Microsoft Learn: Maintain planned orders with action messages

Explanation:
The question requires printing license plate labels during the Report as finished step within manufacturing execution. License plates are the fundamental tracking mechanism for warehouse items, and when items are reported as finished, they are often placed into license-plate-controlled inventory. The manufacturing execution module must be configured to generate license plates at this specific step.

Explanation of Correct Option:

C. License plates.
This is correct because license plate configuration includes settings for automatic license plate creation and label printing during warehouse receiving processes, including production report as finished. When setting up license plates, you can define that a new license plate is created and its label printed automatically when a production order is reported as finished through the manufacturing execution interface.

Explanation of Incorrect Options:

A. Work templates.
Work templates determine how warehouse work is created and what tasks are performed. While they can trigger license plate printing during put-away, they do not control the initial Report as finished step in manufacturing execution where the license plate is first created.

B. Load planning workbench.
This is used for transportation and load planning, managing shipments and containerization. It has no role in manufacturing execution or printing license plates during production reporting.

D. Job card device.
The job card device is the interface workers use to report progress on production jobs. While it can display options and capture data, the actual license plate creation and label printing functionality is configured through license plate settings, not directly on the job card device menu items.

Reference:

Microsoft Learn: License plates overview

Microsoft Learn: Report production orders as finished in manufacturing execution