Free Microsoft MB-330 Practice Test Questions MCQs

Explanation:
The question focuses on meeting requirements for CustomerD regarding inventory management and product allocation. When dealing with customer-specific requirements in Dynamics 365 Supply Chain Management, parameters related to inventory reservation, expiration date management, and wave processing are typically configured. The correct parameters would address how inventory is reserved and allocated specifically for this customer's orders.

Correct Option:

C. FEFO date-control led -
This parameter enables First-Expired-First-Out functionality, which is essential when managing products with expiration dates. If CustomerD requires products with specific freshness or expiry date requirements, this parameter ensures that inventory nearing expiration is picked first, preventing waste and ensuring customer satisfaction with fresh products.

Incorrect Options:

A. Reservation hierarchy -
While this defines how inventory reservations are prioritized across dimensions, it's not specifically addressing customer requirements but rather global inventory structure setup.

B. Sellable days -
This parameter defines how many days before expiration a product can still be sold, which is related but not specifically configured per customer requirement.

D. Wave templates -
These control warehouse work creation and processing but are more operational than customer-specific requirement configurations.

E. FIFO with include physical value -
This is a costing method parameter that affects financial inventory valuation, not customer-specific order fulfillment requirements.

Reference:
Microsoft Learn: Set up FEFO date-controlled warehouse work

Explanation:
The question addresses resolving an issue with mango preserve while minimizing location directives. Location directives in Dynamics 365 determine where items are picked or placed in the warehouse. When specific products require special handling or storage locations, product filters are used to override standard directives without creating multiple duplicate directives for different items.

Correct Option:

B. Item group setup product filter - This allows configuration at the item group level, which is efficient when multiple products share similar characteristics. By setting up product filters on the item group for mango preserve, you can modify location directive behavior for the entire group without creating individual filters for each product, minimizing the number of required directives.

Incorrect Options:

A. Customer product filter - This filters based on customer-specific requirements, not product characteristics, and would not resolve a product-specific storage issue.

C. Released product setup product filter - While this can resolve the issue, it requires configuring filters for each individual released product, which increases maintenance and doesn't minimize location directives.

D. Warehouse management setup product filter - This is a general setup parameter that defines filter codes but doesn't directly apply them to products or item groups.

Reference:
Microsoft Learn: Product filters for location directives

Explanation:
This question presents a matrix table showing different solutions and menu setups for reprinting labels in warehouse operations. The image shows four combinations: using warehousing app only or web client only, paired with different reprint menu options (by item, by last, by enum). The task is to identify which combinations will successfully resolve the operator's label reprint issue.

Correct Options:

Process: Reprint labels | Solution: Use the warehousing app only | Menu Setup: Reprint by last
This combination works because operators in the warehouse need mobile device access to reprint labels immediately. "Reprint by last" allows operators to quickly reprint the most recently generated label without searching, which is efficient for resolving immediate label issues during warehouse operations.

Process: Reprint labels | Solution: Use the web client and warehousing app | Menu Setup: Reprint by item
This combination provides flexibility by allowing reprints from both interfaces. "Reprint by item" enables searching and reprinting labels for specific items, which is useful when operators need to replace damaged labels or when multiple label reprints are needed for different items.

Incorrect Options:
Reprint by item with warehousing app only - While possible, this would be inefficient for operators who need quick access to reprint the last label rather than searching by item each time.

Reprint by last with web client only - Web client access may not be practical for floor operators who need immediate label reprints without returning to an office computer.

Reprint by enum with any solution - This menu setup is not mentioned in standard label reprint scenarios and would likely require custom development, making it less practical for standard label reprint resolution.

Reference:
Microsoft Learn: Configure menu items for mobile devices for license plate receiving

Explanation:
This drag-and-drop question evaluates knowledge of the typical sequence of actions a warehouse operator performs in Dynamics 365 Supply Chain Management using the Warehouse Management mobile app after completing core warehouse work such as receiving or movement. The focus is on finalizing placement of inventory and preparing it for operational use. In standard WMS flows, the operator first completes the directed put-away work to physically move items to the correct storage location, then changes the inventory status to make the stock available (or blocked/quality-held as required). Other journal-based processes are not the immediate next steps in this context.

Correct Option:

Step 1: Complete put away work
After picking up items (e.g., during receiving or movement), the mobile app directs the operator to the put-away location via work instructions. Completing this put-away work confirms the physical movement, updates location-specific on-hand quantities, and closes the work order in the system. This is a mandatory step in directed warehouse processes before inventory can be considered fully processed and ready for status updates or picking.

Step 2: Change inventory status
Once put away is finished, the operator frequently uses the "Change inventory status" menu item on the mobile device to update the status of the license plate or location (e.g., from Received → Available, or to Blocked for inspection). This step controls reservation, picking eligibility, and reporting accuracy, and is a common immediate follow-up action after completing put-away work in many warehouse configurations.

Incorrect Option:
Post movement journal — Incorrect for the next steps because movement journals are used in non-directed (basic inventory) scenarios or for manual corrections/adjustments with financial impact. In advanced WMS with work templates and location directives, inventory movements are handled through directed work (put away/movement work), not manual journals as the follow-up to put away.

Post cycle count away work — Incorrect because cycle counting is an independent inventory verification process. It involves creating cycle count work, performing counts via the mobile app, approving variances, and then posting the cycle count journal. It is not part of the standard sequential flow immediately after completing put away or changing status in inbound or internal movement scenarios.

Post cycle count journal — Incorrect as this is the final posting step of the separate cycle counting process after discrepancies are reviewed and approved. It adjusts inventory quantities and is unrelated to the immediate next actions following put-away completion in typical operator workflows.

Reference:
Microsoft official documentation on warehouse management mobile device workflows, inventory status management, and work execution sequences (no external links included per your instruction).

Explanation:
The question addresses making changes based on internal audit findings. When audit findings reveal issues with quality control or non-conforming products, Dynamics 365 provides specific features to handle defective or questionable inventory. The feature chosen should enable proper isolation and tracking of problematic items identified during the audit process.

Correct Option:

C. Quarantine order -
This feature allows isolation of non-conforming or questionable inventory until quality inspection is completed. When audit findings identify quality issues, enabling quarantine orders ensures problematic items are physically separated from available stock, preventing accidental use or shipment. The quarantine process enforces proper inspection procedures before items are either rejected or returned to inventory.

Incorrect Options:

A. Inventory journal workflows -
These manage approval processes for inventory adjustments but don't specifically address quality-related audit findings requiring physical isolation of products.

B. Scrap method -
This defines how scrapped materials are accounted for but only comes into play after items have already been deemed non-repairable, not for initial isolation based on audit findings.

D. Tag counting -
This is a cycle counting method using numbered tags to ensure count accuracy, which addresses inventory accuracy but not quality-related audit findings requiring product isolation.

Reference:
Microsoft Learn: Quarantine orders

Explanation:
The question asks about determining how many pickle bottles are contained within each case. This involves defining the relationship between different units of measure (bottles and cases). In Dynamics 365 Supply Chain Management, this relationship must be established to enable proper inventory tracking, purchasing, and sales across different units.

Correct Option:

B. Unit of measure conversion per product -
This allows you to define the specific conversion factor between different units for a particular product. For pickle bottles, you would configure that 1 case equals X bottles. This product-specific conversion ensures accurate inventory calculations when receiving cases and selling bottles, or vice versa.

Incorrect Options:

A. Unit sequence group -
This defines the order of units used for purchasing, sales, and inventory, but doesn't establish the actual mathematical conversion between units.

C. Unit of measure conversion per product variant -
While this allows variant-specific conversions, it's more granular than needed unless different variants of pickles have different case quantities.

D. Operating units -
These are organizational divisions like cost centers or business units, not related to unit conversions for products.

Reference:
Microsoft Learn: Unit of measure and conversion policies

Explanation:
The question requires configuring kosher pickle requirements specifically for VendorA. When dealing with vendor-specific product requirements like kosher certification, Dynamics 365 provides several configuration options. The correct setup ensures that kosher pickles are properly tracked and only sourced from approved vendors with appropriate certifications. The vendor-specific nature of kosher certification requires configurations that link products to approved vendors.

Correct Options:

Requirement: VendorA agreement | Configuration: Set approved vendor list
Setting up an approved vendor list for kosher pickles ensures that only VendorA can supply these products. This configuration validates that any purchase order for kosher pickles automatically checks against the approved vendor list, preventing unauthorized sourcing from vendors without proper kosher certification.

Requirement: VendorA agreement | Configuration: Create trade agreement
Trade agreements allow you to define specific pricing and discount terms for kosher pickles purchased from VendorA. This configuration ensures that when purchasing kosher-certified pickles from VendorA, the agreed-upon pricing structure is automatically applied to purchase orders.

Incorrect Options:

Set invoice account field -
This configuration determines which vendor receives payment but doesn't address kosher certification requirements or sourcing restrictions.

Populate default vendor -
While this suggests a preferred vendor, it doesn't enforce the exclusive sourcing requirement for kosher-certified products from VendorA.

Using any configuration for VendorB agreement -
Since the question specifically addresses VendorA requirements for kosher pickles, configurations should only be applied to VendorA.

Reference:
Microsoft Learn: Approved vendor lists and Trade agreements

Explanation:
The question requires matching Dynamics 365 features to specific requirement types for VendorC: Shipment and On-hand. Different vendor collaboration and inventory management features address different aspects of the vendor relationship. Shipment requirements typically involve tracking and managing incoming goods, while on-hand requirements relate to inventory ownership and availability.

Correct Options:

Requirement type: Shipment | Feature: Vendor collaboration Vendor collaboration enables vendors to manage purchase order confirmations and shipment information directly. For shipment requirements, this feature allows VendorC to update delivery dates, provide advanced shipping notices, and manage packing slips, improving visibility and coordination of incoming shipments.

Requirement type: On-hand | Feature: Consignment inventory
Consignment inventory allows VendorC to maintain ownership of goods until they are consumed or sold. For on-hand requirements, this feature enables tracking of vendor-owned inventory at your warehouse, providing accurate visibility of available stock while deferring payment until actual usage.

Incorrect Options:

Landed cost - This feature manages additional costs associated with shipping and importing goods, such as freight and duties, but doesn't directly address shipment collaboration or on-hand inventory ownership requirements.

Product lifecycle management - This feature manages product versions, engineering changes, and product retirement, which relates more to product design and engineering than to vendor shipment or inventory ownership requirements.

Using features for opposite requirement types - Vendor collaboration primarily addresses shipment coordination, not on-hand inventory, while consignment specifically addresses on-hand vendor-owned inventory, not shipment tracking.

Reference:
Microsoft Learn: Vendor collaboration and Consignment inventory setup

Explanation:
The question requires matching configurations to specific requirements for an operations coordinator and Vendor1's inbound load status. The table shows different Dynamics 365 modules (Transportation management, Landed cost, Inventory management, Product information management) and inbound load statuses (Confirmed, Received, Registered, Shipped). The correct configuration must align with coordinator responsibilities and load tracking needs.

Correct Options:

Requirement: Operations coordinator | Configuration: Transportation management
Transportation management provides tools for coordinating shipments, managing carriers, and tracking inbound loads. Operations coordinators need this module to plan and monitor incoming shipments, assign freight, and manage delivery schedules for Vendor1's inbound loads.

Requirement: Vendor1 inbound load status | Configuration: Landed cost
Landed cost functionality tracks inbound load status through the entire journey from shipment to receipt. This module provides visibility into each status stage (Shipped, Confirmed, Registered, Received) and manages additional costs associated with the inbound journey, which is essential for accurate Vendor1 load tracking.

Incorrect Options:

Inventory management - While this manages received inventory, it doesn't provide the comprehensive inbound load status tracking needed for Vendor1's shipment journey.
Product information management - This handles product definitions and specifications but doesn't track inbound load status or support operations coordination.

Other status mismatches - The inbound load status requires a module that can track the complete lifecycle from shipping to receipt, which landed cost specifically provides.

Reference:
Microsoft Learn: Transportation management and Landed cost overview

Explanation:
The question requires configuring vendor rebate parameters for correct calculation of vendor claims. In Dynamics 365, vendor rebates require configuration of both the break type (how rebate tiers are structured) and the basis for calculation (what value the rebate is taken from). The available options include Amount, Gross, Net, and Quantity.

Correct Options:

Requirement: Rebate line break type | Configuration: Amount
The rebate line break type determines how rebate tiers are structured. When set to Amount, rebate percentages or amounts change based on the total purchase amount reaching certain thresholds. This is common for vendor rebate agreements where rebate rates increase at specific spending levels.

Requirement: Taken from | Configuration: Gross
The "Taken from" field determines the basis for calculating the rebate amount. Gross represents the total invoice amount before discounts. Using Gross as the calculation basis ensures vendor claims are calculated on the full purchase value, which is typical for many vendor rebate agreements.

Incorrect Options:
Quantity - While quantity can be used for break types in some scenarios, Amount is more appropriate for monetary threshold-based rebate structures.

Net - Net represents the amount after discounts. Using Net would reduce the rebate calculation basis, which may not align with standard vendor rebate agreements where rebates apply to gross purchases.

Using Amount for "Taken from" - Amount specifies the break type structure, not the calculation basis for the rebate itself.

Reference:
Microsoft Learn: Vendor rebate setup