Microsoft Dynamics 365 Supply Chain Management Functional Consultant Associate (MB-330)

C is correct.

Explanation: The Top-down and Minimal domains first solver strategies have been shown to be more efficient at solving models that contain several arithmetic expressions where no table constraints are used. Customer implementation studies have shown that the Top-down strategy outperforms the Minimal domains first strategy.

A is incorrect: The Default strategy has been optimized to solve models that rely on table constraints. It is most efficient when table constraints are used extensively, not when models contain arithmetic expressions without table constraints.

B is incorrect: While Minimal domains first can handle arithmetic expressions, customer implementation studies have shown that Top-down outperforms it in these scenarios.

D is incorrect: Z3 is recommended as the default solver strategy for general use, but the evidence specifically identifies Top-down as more efficient for models with arithmetic expressions and no table constraints.

C is correct.

Explanation: The evidence supports C because customer implementation studies have shown that the Top-down strategy outperforms the Minimal domains first strategy, and both are more efficient at solving models that contain several arithmetic expressions where no table constraints are used.

A is incorrect: The Default strategy has been optimized to solve models that rely on table constraints, not models that rely exclusively on arithmetic expressions.

B is incorrect: While Z3 is recommended as the default solver strategy, the Top-down strategy is specifically noted as more efficient for models containing several arithmetic expressions without table constraints.

D is incorrect: Although Minimal domains first is efficient for arithmetic expressions, customer implementation studies have shown that the Top-down strategy outperforms it.

B is correct.

Explanation: Product configuration uses Microsoft Solver Foundation (MSF) to solve expression constraints and conditions. MSF can find one or more valid solutions and eliminate invalid values for product configuration models.

A is incorrect: OML is the algebraic modeling language included with MSF for modeling and solving, but it is not the foundation that performs the actual solving of constraints.

C is incorrect: While product configuration models can be formulated as constraint satisfaction problems, CSP library is not the documented tool used by the product configurator.

D is incorrect: The expression editor is a user interface component for building expressions, not the solver foundation that validates and solves constraints.

C is correct.

Explanation: An item generally needs its own level in the BOM if it must be tracked, stored, or sold at some stage. The frame is assembled, stored, and sold, so give it a sub-BOM and reference it from the bicycle BOM to create a multilevel BOM.

A is incorrect: A single-level BOM doesn't contain the components of the components. Listing frame parts directly removes the frame as an item that you can store and sell.

B is incorrect: Wheels, seat, and handlebars don't require assembly, so they don't need their own BOMs. The frame, which is assembled, needs the sub-BOM.

D is incorrect: If the bicycle BOM doesn't reference the frame BOM, the bicycle BOM doesn't include the frame as a component, and the multilevel structure isn't created.

B is correct.

Explanation: The evidence states that selecting the Physical negative inventory checkbox allows the system to issue an item from inventory, even though stock levels are insufficient. If the item's item model group has Physical negative inventory selected, you can deliver the item, even if it's not registered as being physically present in the inventory.

A is incorrect: Financial negative inventory controls whether you can issue quantities that are physically available but not financially updated. In this scenario, the items aren't physically recorded in inventory.

C is incorrect: Registration requirements require you to register the receipt before you update inventory through the product receipt. This adds a step and doesn't allow delivery of unrecorded items.

D is incorrect: Picking requirements require item issues to have the Picked status before you can physically update inventory. This doesn't allow delivery of items that aren't in inventory.

D is correct.

Explanation: You must create a customer account for a prospect before you confirm the quotation. When the quotation is confirmed, the system generates a sales order.

A is incorrect: A sales agreement is a contract for a specific quantity over a period in exchange for special pricing or discounts. It isn't a prerequisite for confirming a quotation.

B is incorrect: A Journal sales order is a draft that doesn't affect stock quantities. Confirming the quotation generates the sales order.

C is incorrect: A proforma invoice is a draft invoice generated before invoice posting. It isn't required before you confirm a quotation.

A is correct.

Explanation: The evidence states that you must create a batch number before the system can assign it to a product. Unlike serial number assignment, you can't enter a batch number directly in the Batch number field on the order line. Rather, you need to create it on the Batch number page and then select it from the line in the sales or purchase order.

B is incorrect: The Serial number field identifies individual items, not a group of items. Entering the vendor batch number as a serial number doesn't create a batch number for tracing.

C is incorrect: Order activation turns on automatic number allocation in the Accounts receivable and Sales and marketing modules. It doesn't allow you to type a batch number directly on a purchase order line.

D is incorrect: To change an inventory dimension that you entered on a receipt transaction, you use a Transfer journal. A Movement journal doesn't add the vendor batch number, and posting without it breaks traceability to the vendor.

A is correct.

Explanation: If a target attribute is of the integer type but a calculation generates a decimal number, the system only returns the integer part of the calculated result, removes the decimal part, and does not round the result. A result of 12.70 is shown as 12.

B is incorrect: The system does not preserve the decimal portion when the target attribute is an integer type.

C is incorrect: The system does not round the result. It removes the decimal part rather than rounding up or down.

D is incorrect: The system handles this scenario by truncating the decimal portion rather than generating an error message.

C is correct.

Explanation: The evidence states that it's optional whether the warehouse storage dimension is mandatory. When the multiple-site functionality is active, the site storage dimension is already mandatory, so warehouse is the additional dimension that you can configure.

A is incorrect: You can't specify location as mandatory. Only product dimensions, site with multiple sites active, and optionally warehouse can be mandatory.

B is incorrect: You can't specify inventory status as mandatory. It is one of the remaining storage dimensions that the Mandatory setting doesn't support.

D is incorrect: You can't specify license plate as mandatory. It is one of the remaining storage dimensions that the Mandatory setting doesn't support.

B is correct.

Explanation: The evidence states that if you do not select any attributes for reuse, the system always reuses the configuration, regardless of the user's selections during a configuration session.

A is incorrect: Exact matching of attribute selections occurs only when you select the Include in reuse option for specific attributes. Without any attributes marked for reuse, the system does not check attribute values.

C is incorrect: Configuration reuse is automatic when enabled. The system verifies whether a matching configuration exists and reuses it without prompting the user to manually select a configuration.

D is incorrect: The Reuse configurations field set to Yes at the component level enables reuse. Not selecting attributes for reuse results in the system always reusing configurations, not in disabling the reuse feature.