Microsoft Certified: Dynamics 365 Supply Chain Management Functional Consultant Associate (MB-330) Practice Tests

Explanation

Running operations scheduling first to get capacity overview, then running job scheduling to add detail provides both high-level planning and detailed execution scheduling. Dynamics 365 Supply Chain Management supports using operations scheduling and job scheduling independently or in combination, with operations scheduling typically run first when both are used. For Horizon Manufacturing's need for both capacity planning and detailed execution scheduling, the recommended approach is to first run operations scheduling followed by job scheduling. Operations scheduling provides the high-level capacity overview by scheduling operations at the resource group level with date-level scheduling. This gives the production planner visibility into whether sufficient capacity exists across resource groups, which periods are heavily loaded, and whether the overall production plan is feasible. Operations scheduling calculates operation durations and reserves capacity on resource groups but does not assign specific machines or calculate exact start and end times. Once operations scheduling provides this capacity validation, job scheduling is then run to add detail. Job scheduling explodes each operation into specific jobs, assigns each job to an individual resource within the resource groups, and calculates exact start and end times down to the hour and minute level. This detailed schedule enables shop floor execution, allowing workers and supervisors to know exactly which machine performs which operation and exactly when. The two-stage approach combines the strengths of both methods: operations scheduling for strategic capacity planning and validation, followed by job scheduling for tactical execution planning. The operations schedule acts as a framework that job scheduling then elaborates with specific resource and time details. Running operations scheduling only would be incorrect because it would not provide the detailed specific resource assignments and exact timing needed for shop floor execution. Workers need to know which specific machine to use and when, which operations scheduling does not provide. Running job scheduling only would be incorrect because while job scheduling can be run independently, starting with operations scheduling provides valuable capacity validation before investing time in detailed job scheduling. Operations scheduling helps identify capacity issues before detailed planning occurs. Running job scheduling first then operations scheduling would be incorrect because this reverse sequence does not make logical sense. Operations scheduling provides the broad framework that job scheduling elaborates, not the reverse.

Explanation

The Allow purchase order line registration when in external review toggle must be set to Yes to permit warehouse workers to register purchase order lines from mobile devices when the purchase order has an approval status of In external review. This parameter is configured on the Mobile device FastTab of the Warehouse management parameters page. This flexibility is useful in scenarios where your organization permits warehouse operations to proceed while purchase orders are still undergoing external review or approval processes. For example, if goods arrive at the warehouse while a purchase order is being reviewed by an external auditor or compliance team, workers can begin the receiving process rather than waiting for approval to complete. Without this setting enabled, workers would be blocked from registering purchase order lines on mobile devices until the approval status changes from In external review to Approved, potentially causing delays in warehouse operations and inefficient use of receiving dock space. Enable RSAT support toggle enables the Warehouse Management mobile app task validator for testing purposes, which logs and validates each step performed in the app but does not control purchase order registration capabilities. Use mobile device session logging toggle controls whether worker sign-ins are logged for audit and troubleshooting purposes but does not affect purchase order line registration permissions. Generate context-aware insights toggle enables AI-assisted overview of daily tasks on the workload screen to improve productivity but does not control whether workers can register purchase orders with In external review status.

Explanation

A query is created using the Edit query button on the location directive header, and this query allows you to specify conditions that determine when the location directive should be used. This is an additional layer of filtering beyond the basic header fields. For example, you could create a query that checks if a sales order is from a specific customer, if items belong to a certain product category, if the order was created through a particular sales channel like e-commerce, or if the order meets certain priority criteria. This query functionality provides powerful flexibility in designing location strategies that respond to your specific business rules. When the system evaluates which location directive to use, it first filters based on the work order type, site, warehouse, and directive code, and then evaluates the query conditions on the remaining candidates. Only location directives whose query conditions are satisfied will be considered. A location directive line is not created on the header - it is a separate record associated with the header that specifies quantity ranges, units, and actions. Work template associations link work templates to location directives through the directive code, but they do not specify conditions on the directive itself. A location profile is a separate configuration element used on locations to define their characteristics, not a component of the location directive structure. The query capability accessed through Edit query is the correct mechanism for adding conditional logic to determine when a directive applies.

Explanation

Proseware Manufacturing should configure the Transit time field to account for the 30 minutes of transportation time. Transit time is the transport time for transporting items between two operation resources or from the last operation to inventory. How the system uses transit time depends on how the operation's route group is set up. The transport time must be a positive value. For Proseware, the 30-minute transportation time between operations is exactly what transit time is designed to represent - the physical movement of items from one work area to another. This is distinct from queue waiting time, which represents items waiting before or after operations, and from operation execution time like setup or run time. Transit time specifically accounts for the logistics of moving work in progress through the facility. For example, if Proseware's welding operation is on the first floor and their painting operation is on the second floor, the transit time would account for the 30 minutes needed to transport welded assemblies from the first floor to the second floor. Including this transit time in scheduling ensures accurate production timelines and helps identify potential bottlenecks in material flow between operations. Queue time before represents waiting before an operation starts, not transportation time. Queue time after represents waiting after an operation completes, which could precede transportation but is not the transportation itself. Run time is the operation execution time and should not include transportation between operations. Transit time is specifically designated for transportation duration and must be properly configured for accurate scheduling that accounts for material movement logistics in the production facility.

Explanation

Properties should be configured on both calendars and resources to enable this functionality. You can use the Properties field to assign properties to your templates and resources. The system uses properties in the scheduling and structuring of production, allowing you to produce items that share the same properties simultaneously. For example, if you assign the property of red to a paint machine on Monday in the calendar, when you run the schedule, this resource paints items red only on Mondays. Resources use properties to help optimize production schedules by matching the property requirements of production operations with the properties available on resources during specific time periods. You can set up properties on the Properties page, and it is useful to set up properties on your calendars for use in setting up properties on resources. This allows the scheduling engine to match operations that require specific properties with resources and time periods that have those properties available. While resource properties are not required when you set up working time calendars, they provide powerful scheduling optimization when properly configured. Efficiency percentages control the rate at which resources operate during specific time periods but do not restrict which operations can be performed based on characteristics like color or other attributes. Resource groups organize multiple resources together but do not provide the specific matching capability needed to ensure red items are only painted on red-designated days. Working time templates define when resources are available to work but do not specify what types of operations can be performed during those times based on characteristics or attributes.