Scenario practice questions

You are configuring a 'Cluster Picking' profile for a warehouse worker. Which configuration ensures that the worker can pick items for multiple orders simultaneously?

Trap 1: Assign a work template with 'Split' enabled.

Work template splitting is used to divide work into smaller chunks, but it does not facilitate the simultaneous picking of multiple orders into distinct clusters. Cluster picking requires specific profile definitions to manage multiple active orders, which standard work template splitting is not designed to achieve.

Trap 2: Enable wave picking in the mobile menu.

Wave picking groups orders for a common replenishment or shipping process, but it does not enable the simultaneous picking of different orders into a cluster by a single worker. Cluster picking is a separate, dedicated feature set within the mobile device menu item configuration.

Trap 3: Create a new location directive for cluster.

Location directives are for finding the optimal pick and put locations, not for managing the logical grouping of multiple orders for a single worker. Cluster picking is a profile-driven operation that works with existing directives, not an alternative to the standard location selection process.

A
Assign a work template with 'Split' enabled.
Why it fails: Work template splitting is used to divide work into smaller chunks, but it does not facilitate the simultaneous picking of multiple orders into distinct clusters. Cluster picking requires specific profile definitions to manage multiple active orders, which standard work template splitting is not designed to achieve.
B
Set up a Cluster profile with defined positions.
A cluster profile manages the structure of the cluster, including the number of positions and the sorting logic. By configuring this, the system allows the worker to pick multiple items for different orders in one go, drastically increasing picking efficiency for smaller, high-velocity order profiles.
C
Enable wave picking in the mobile menu.
Why it fails: Wave picking groups orders for a common replenishment or shipping process, but it does not enable the simultaneous picking of different orders into a cluster by a single worker. Cluster picking is a separate, dedicated feature set within the mobile device menu item configuration.
D
Create a new location directive for cluster.
Why it fails: Location directives are for finding the optimal pick and put locations, not for managing the logical grouping of multiple orders for a single worker. Cluster picking is a profile-driven operation that works with existing directives, not an alternative to the standard location selection process.

Question 2mediummultiple choice

You are configuring a cross-docking scenario where items arriving on a purchase order must be immediately moved to a shipping bay for a pending sales order. Which component must be enabled to facilitate this automatic flow?

Trap 1: Transportation management load builder

The load builder is used to group shipments into loads for transportation purposes. It manages the logistics of shipping rather than the internal warehouse movement logic required to move goods from receiving directly to shipping, which is the specific function of cross-docking templates in the system.

Trap 2: Wave demand replenishment template

Wave demand replenishment is for moving stock from bulk storage to picking areas. It is the opposite of cross-docking, as it is designed to increase stock levels in picking locations rather than bypassing storage entirely to expedite the movement of incoming goods to the shipping dock area.

Trap 3: Location directive for 'Pick'

Location directives define how the system finds inventory for picks. They are used for standard picking flows and do not contain the intelligence required to intercept incoming purchase orders and route them directly to shipping, which requires the specific logic found in cross-docking template configurations.

A
Transportation management load builder
Why it fails: The load builder is used to group shipments into loads for transportation purposes. It manages the logistics of shipping rather than the internal warehouse movement logic required to move goods from receiving directly to shipping, which is the specific function of cross-docking templates in the system.
B
Cross-docking template
A cross-docking template is required to define the criteria under which inbound items are redirected to an outbound staging area. It links the inbound supply to the outbound demand, automatically triggering the necessary work to bypass normal put-away processes and move goods directly to the shipping bay.
C
Wave demand replenishment template
Why it fails: Wave demand replenishment is for moving stock from bulk storage to picking areas. It is the opposite of cross-docking, as it is designed to increase stock levels in picking locations rather than bypassing storage entirely to expedite the movement of incoming goods to the shipping dock area.
D
Location directive for 'Pick'
Why it fails: Location directives define how the system finds inventory for picks. They are used for standard picking flows and do not contain the intelligence required to intercept incoming purchase orders and route them directly to shipping, which requires the specific logic found in cross-docking template configurations.

Question 3mediummultiple choice

A distribution center uses warehouse management in Dynamics 365 Supply Chain Management. The warehouse manager wants to create a new mobile device menu item that allows workers to perform a full or partial license plate receive against a purchase order. The worker must first scan the purchase order number, then the item, and then the license plate. Which mobile device menu item creation method should you use?

Trap 1: Purchase order item receiving

This method is used for receiving against a purchase order but does not support license plate receiving. It is designed for scenarios where items are received directly into a location without the need to capture license plate information. Because the scenario requires capturing the license plate, this method does not meet the requirement.

Trap 2: Inbound load receiving

Inbound load receiving is used when receiving against a load rather than a purchase order. Although it may support license plates in some contexts, the scenario specifies receiving against a purchase order and scanning the purchase order number first, which aligns with license plate receiving, not load receiving.

Trap 3: Purchase order line receiving

Purchase order line receiving allows receiving against a purchase order line but does not include license plate capture. It is suitable for direct receiving without license plates, so it cannot fulfill the requirement to scan a license plate during receiving.

A
Purchase order item receiving
Why it fails: This method is used for receiving against a purchase order but does not support license plate receiving. It is designed for scenarios where items are received directly into a location without the need to capture license plate information. Because the scenario requires capturing the license plate, this method does not meet the requirement.
B
License plate receiving
License plate receiving is the correct method because it enables workers to receive items against a purchase order and associate them with a license plate. It supports full or partial receiving and prompts for the purchase order, item, and license plate in sequence, exactly as the scenario requires.
C
Inbound load receiving
Why it fails: Inbound load receiving is used when receiving against a load rather than a purchase order. Although it may support license plates in some contexts, the scenario specifies receiving against a purchase order and scanning the purchase order number first, which aligns with license plate receiving, not load receiving.
D
Purchase order line receiving
Why it fails: Purchase order line receiving allows receiving against a purchase order line but does not include license plate capture. It is suitable for direct receiving without license plates, so it cannot fulfill the requirement to scan a license plate during receiving.

Question 4hardmultiple choice

Which THREE of the following are components of a Product Configuration Model? (Choose three)

Trap 1: Financial dimensions.

Financial dimensions are general ledger-based constructs for reporting and are not components of a product configuration model. While they are important for accounting, they do not participate in the logical construction or validation of the product itself during the configuration phase of the sales process.

Trap 2: General Ledger account strings.

Account strings are used in financial accounting to record entries in the general ledger. They have no relationship to product configuration logic. Including them in a configuration model would be incorrect, as they are not used to define the product structure or validate the physical buildability of an item.

A
Attributes.
Attributes are the core inputs of a model. They represent the characteristics a user chooses, such as material type, size, or color. Without attributes, the model cannot collect the necessary data to define what the user wants to configure, rendering the entire configuration model useless for dynamic product generation.
B
Constraints.
Constraints are the logical rules that define valid combinations of attributes. They ensure that a user cannot select incompatible options. Without constraints, the system would allow the creation of impossible configurations, leading to errors in the Bill of Materials or production routing, which would cause significant manufacturing downstream issues.
C
Calculations.
Calculations allow the model to dynamically compute values based on the user's input, such as the total weight or the final sales price. This is crucial for accurate costing and logistics, as it allows the system to generate realistic production requirements based on the specific attributes selected by the customer.
D
Financial dimensions.
Why it fails: Financial dimensions are general ledger-based constructs for reporting and are not components of a product configuration model. While they are important for accounting, they do not participate in the logical construction or validation of the product itself during the configuration phase of the sales process.
E
General Ledger account strings.
Why it fails: Account strings are used in financial accounting to record entries in the general ledger. They have no relationship to product configuration logic. Including them in a configuration model would be incorrect, as they are not used to define the product structure or validate the physical buildability of an item.

Question 5hardmultiple choice

Which TWO scenarios require the use of a Quarantine warehouse to manage inventory quality?

Trap 1: Moving items from a production order to scrap.

Moving items to scrap is typically handled via inventory adjustment journals or specific scrap journals directly from the production order. A quarantine warehouse is for inspection and quality control, not for discarding inventory that has been deemed unusable or defective by the production process.

Trap 2: Splitting inventory for multi-site transfer.

Transfer orders are the standard mechanism for moving inventory between sites. A quarantine warehouse is not intended for transit or transfer scenarios; using it for this purpose would misrepresent the inventory as being under quality hold, leading to incorrect reporting in the system.

Trap 3: Adjusting inventory levels based on a cycle count.

Cycle counting is used to reconcile physical counts with system records. It does not involve quarantine warehouses. If a discrepancy is found, an adjustment journal is used; there is no quality hold implied simply by identifying that the physical count differs from the system quantity.

A
Moving items from a production order to scrap.
Why it fails: Moving items to scrap is typically handled via inventory adjustment journals or specific scrap journals directly from the production order. A quarantine warehouse is for inspection and quality control, not for discarding inventory that has been deemed unusable or defective by the production process.
B
Holding items after a partial receipt for quality inspection.
When a partial receipt occurs, moving the goods into a quarantine warehouse ensures the items remain in the system but are unavailable for outbound processing. This allows quality teams to perform inspections while the remainder of the order remains available for other operations without contamination.
C
Separating inventory that failed a vendor test.
Quarantine warehouses allow for the segregation of items that failed vendor testing. This keeps the stock in the system for tracking and credit processing purposes but prevents the warehouse team from fulfilling shipments with defective materials, ensuring compliance with quality standards until resolution occurs.
D
Splitting inventory for multi-site transfer.
Why it fails: Transfer orders are the standard mechanism for moving inventory between sites. A quarantine warehouse is not intended for transit or transfer scenarios; using it for this purpose would misrepresent the inventory as being under quality hold, leading to incorrect reporting in the system.
E
Adjusting inventory levels based on a cycle count.
Why it fails: Cycle counting is used to reconcile physical counts with system records. It does not involve quarantine warehouses. If a discrepancy is found, an adjustment journal is used; there is no quality hold implied simply by identifying that the physical count differs from the system quantity.

Question 6easymultiple choice

A company is running master planning in Dynamics 365 Supply Chain Management. They want to simulate the effect of a new master plan without affecting existing planned orders. Which type of master plan should they create?

Trap 1: Forecast plan

'Forecast plan' is not a type of master plan in Dynamics 365 Supply Chain Management. Master plan types include static, dynamic, and simulation. Forecast plans are not a standard concept; forecasts are inputs to master plans, not separate plan types.

Trap 2: Dynamic plan

A dynamic plan is used for operational planning and reflects current data. Running a dynamic plan can create or update planned orders, which would affect existing planned orders. It is not intended for simulation without impact.

Trap 3: Static plan

A static plan is a master plan that uses a snapshot of data and is typically used for long-term planning. However, running a static plan may still generate planned orders that could affect existing orders if not managed. It is not specifically designed for simulation without impact.

A
Simulation plan
A simulation plan is a master plan that is used to test scenarios without affecting actual planned orders. When you run a simulation plan, the system generates planned orders that are stored separately and do not impact the live planning data. This allows you to evaluate the effects of changes safely.
B
Forecast plan
Why it fails: 'Forecast plan' is not a type of master plan in Dynamics 365 Supply Chain Management. Master plan types include static, dynamic, and simulation. Forecast plans are not a standard concept; forecasts are inputs to master plans, not separate plan types.
C
Dynamic plan
Why it fails: A dynamic plan is used for operational planning and reflects current data. Running a dynamic plan can create or update planned orders, which would affect existing planned orders. It is not intended for simulation without impact.
D
Static plan
Why it fails: A static plan is a master plan that uses a snapshot of data and is typically used for long-term planning. However, running a static plan may still generate planned orders that could affect existing orders if not managed. It is not specifically designed for simulation without impact.

Question 7easymultiple choice

A company wants to use the Vendor Collaboration module in Dynamics 365 Supply Chain Management. They need to allow vendors to view and respond to purchase orders. Which security role should be assigned to the vendor users?

Trap 1: Purchasing agent

The 'Purchasing agent' role is an internal role for employees who manage purchasing activities. It grants broad access to purchase orders and vendor management, which is not appropriate for external vendors. Assigning this role would give vendors excessive permissions and is a security risk.

Trap 2: System administrator

The 'System administrator' role has full access to the entire system, including all configuration and data. Assigning this to external vendors would be a severe security breach and is not intended for vendor collaboration. It grants far more permissions than needed.

Trap 3: Accounts payable clerk

The 'Accounts payable clerk' role is for internal finance users who process invoices and payments. It does not provide the necessary access to the vendor collaboration portal for viewing and responding to purchase orders. Thus, it is not suitable for vendor users.

A
Purchasing agent
Why it fails: The 'Purchasing agent' role is an internal role for employees who manage purchasing activities. It grants broad access to purchase orders and vendor management, which is not appropriate for external vendors. Assigning this role would give vendors excessive permissions and is a security risk.
B
Vendor (external)
The 'Vendor (external)' role is specifically designed for external vendor users in the Vendor Collaboration module. It grants access to the vendor portal where they can view purchase orders, confirm them, and manage other collaboration tasks. This role is the standard for vendor collaboration access.
C
System administrator
Why it fails: The 'System administrator' role has full access to the entire system, including all configuration and data. Assigning this to external vendors would be a severe security breach and is not intended for vendor collaboration. It grants far more permissions than needed.
D
Accounts payable clerk
Why it fails: The 'Accounts payable clerk' role is for internal finance users who process invoices and payments. It does not provide the necessary access to the vendor collaboration portal for viewing and responding to purchase orders. Thus, it is not suitable for vendor users.

Question 8hardmulti select

A company is defining a new category hierarchy for its electronics products in Dynamics 365 Supply Chain Management. The product team wants to use the hierarchy both to organize products and to control which product attributes are available for products in each category. Which two statements describe how category hierarchies and attribute assignments work in this scenario? (Choose two.)

Trap 1: Only one category hierarchy of each type can exist at a time, and…

Multiple category hierarchies can exist, and products are not required to belong to every category. A hierarchy organizes a subset of products according to its purpose. Claiming only one hierarchy per type can exist and must contain all products is incorrect and does not match the flexibility the system provides.

Trap 2: Attribute values entered on a category are automatically copied to…

Attribute values assigned at the category level provide defaults that products inherit, but they can be overridden per product. Saying they are copied automatically and cannot be changed is incorrect. Products retain the ability to specify their own attribute values, so this statement misrepresents how inheritance works.

Trap 3: A category hierarchy must be linked to a product dimension group…

Category hierarchies and product dimension groups serve different purposes and are not linked in this way. Attributes are assigned directly to categories, independent of dimension groups, which govern variant dimensions. Requiring a dimension group link is not part of the configuration and would not enable attribute assignment.

A
Product attributes can be assigned to a category so that products placed in that category can use those attributes.
Assigning attributes to a category makes those attributes available for products in that category. This is how a category hierarchy controls which characteristics, such as voltage or material, apply to products in each grouping. The statement accurately reflects how attributes and categories interact.
B
A category hierarchy can be assigned a category hierarchy type, such as Procurement or Sales, which determines the purpose it serves.
Category hierarchies have types, such as Procurement, Sales, and Retail, that define their purpose and where they can be used. Choosing the correct type ensures the hierarchy is available for the intended process, such as procurement categorization. This statement correctly describes a core behavior of category hierarchy configuration.
C
Only one category hierarchy of each type can exist at a time, and it must contain every product in the legal entity.
Why it fails: Multiple category hierarchies can exist, and products are not required to belong to every category. A hierarchy organizes a subset of products according to its purpose. Claiming only one hierarchy per type can exist and must contain all products is incorrect and does not match the flexibility the system provides.
D
Attribute values entered on a category are automatically copied to every product assigned to that category and cannot be changed per product.
Why it fails: Attribute values assigned at the category level provide defaults that products inherit, but they can be overridden per product. Saying they are copied automatically and cannot be changed is incorrect. Products retain the ability to specify their own attribute values, so this statement misrepresents how inheritance works.
E
A category hierarchy must be linked to a product dimension group before attributes can be assigned to its categories.
Why it fails: Category hierarchies and product dimension groups serve different purposes and are not linked in this way. Attributes are assigned directly to categories, independent of dimension groups, which govern variant dimensions. Requiring a dimension group link is not part of the configuration and would not enable attribute assignment.

Question 9mediummultiple choice

A company uses Dynamics 365 Supply Chain Management. They have a master plan that is configured to use 'Forecast' as a demand type. They have a sales forecast for 100 units in January. However, they receive a firm sales order for 80 units in January. How does Master Planning handle the forecast and the sales order to avoid double-counting demand?

Trap 1: It ignores the forecast entirely and plans only for the sales order…

Master Planning does not ignore the forecast when a sales order exists. The forecast is still considered, but it is reduced by the sales order quantity to avoid double-counting. If the forecast were ignored, the company might under-plan and miss demand beyond the firm orders. The system uses forecast reduction to combine both demand sources accurately. Thus, this option is incorrect because it fails to account for the remaining forecast.

Trap 2: It creates a planned order for 100 units based on the forecast and…

Master Planning does not ignore firm sales orders; they are firm demand and must be fulfilled. The forecast is reduced by the sales order quantity, not ignored. Creating a planned order solely based on the forecast would fail to prioritize the actual sales order. The system ensures both are considered, with the sales order taking precedence. Thus, this option is incorrect.

Trap 3: It adds the forecast and the sales order, resulting in total demand…

Adding the forecast and sales order would double-count demand because the sales order is likely part of the forecast. Master Planning uses forecast reduction to subtract the sales order quantity from the forecast. This prevents over-planning. The total demand should be the greater of the forecast or the sales order, not the sum. Therefore, this option is incorrect.

A
It ignores the forecast entirely and plans only for the sales order for 80 units.
Why it fails: Master Planning does not ignore the forecast when a sales order exists. The forecast is still considered, but it is reduced by the sales order quantity to avoid double-counting. If the forecast were ignored, the company might under-plan and miss demand beyond the firm orders. The system uses forecast reduction to combine both demand sources accurately. Thus, this option is incorrect because it fails to account for the remaining forecast.
B
It creates a planned order for 100 units based on the forecast and ignores the sales order.
Why it fails: Master Planning does not ignore firm sales orders; they are firm demand and must be fulfilled. The forecast is reduced by the sales order quantity, not ignored. Creating a planned order solely based on the forecast would fail to prioritize the actual sales order. The system ensures both are considered, with the sales order taking precedence. Thus, this option is incorrect.
C
It adds the forecast and the sales order, resulting in total demand of 180 units.
Why it fails: Adding the forecast and sales order would double-count demand because the sales order is likely part of the forecast. Master Planning uses forecast reduction to subtract the sales order quantity from the forecast. This prevents over-planning. The total demand should be the greater of the forecast or the sales order, not the sum. Therefore, this option is incorrect.
D
It reduces the forecast by 80 units, leaving a forecast of 20 units, and includes the sales order for 80 units.
Master Planning uses forecast reduction to prevent double-counting demand. When a firm sales order exists, the system reduces the forecast by the sales order quantity, up to the forecast amount. Here, the sales order for 80 units reduces the January forecast from 100 to 20 units. The sales order is then included as demand, resulting in total demand of 100 units (80 sales order + 20 remaining forecast). This ensures that only the net unfulfilled forecast is planned.

Question 10easymultiple choice

Which plan type should you use to run a simulation without affecting the live production schedules?

Trap 1: Static plan

Static plans are intended for official operational use. Running a simulation in a static plan will overwrite existing planned orders and potentially trigger procurement workflows or shop floor actions, which is disruptive and incorrect for conducting safe experiments or modeling hypothetical supply chain scenarios for planning purposes.

Trap 2: Master plan

The Master plan is the primary static plan used for official production and purchasing. It is not suitable for simulations as changes made here immediately update the planned order list, which is then used by the warehouse and procurement teams for actual execution, leading to significant operational confusion and errors.

Trap 3: Forecast plan

Forecast plans are used to manage demand forecasts and do not handle the full net requirements calculation for production and procurement. They lack the logic for creating the planned orders needed to test supply chain throughput, making them ineffective for simulating actual production or replenishment scenarios.

A
Dynamic plan
The Dynamic plan is specifically designed for simulation and what-if analysis. It allows users to run master planning experiments with different parameters or updated demand signals without overwriting the official static plan, ensuring that the live operational environment remains unaffected until the new results are validated and approved.
B
Static plan
Why it fails: Static plans are intended for official operational use. Running a simulation in a static plan will overwrite existing planned orders and potentially trigger procurement workflows or shop floor actions, which is disruptive and incorrect for conducting safe experiments or modeling hypothetical supply chain scenarios for planning purposes.
C
Master plan
Why it fails: The Master plan is the primary static plan used for official production and purchasing. It is not suitable for simulations as changes made here immediately update the planned order list, which is then used by the warehouse and procurement teams for actual execution, leading to significant operational confusion and errors.
D
Forecast plan
Why it fails: Forecast plans are used to manage demand forecasts and do not handle the full net requirements calculation for production and procurement. They lack the logic for creating the planned orders needed to test supply chain throughput, making them ineffective for simulating actual production or replenishment scenarios.