Microsoft D365 Customer Experience Analyst (MB-280) Practice Questions & Study Guide

Free Microsoft D365 Customer Experience Analyst (MB-280) Practice Questions Preview

• Question 1

  HOTSPOT -
  
  Case study -
  This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
  To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
  At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
  
  To start the case study -
  To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question.
  
  Background information -
  Contoso Ltd. has started a new division that provides janitorial services to businesses.
  The sales teams for this division are using a dedicated instance of Dynamics 365 Sales.
  Contoso Ltd.'s sellers are becoming accustomed to Copilot in Sales and Sales Insights features. They have identified several desired enhancements.
  
  System configuration -
  The base currency for all opportunities in the system is US dollars (USD). The administrator has NOT enabled installed premium Sales Insights features. All users have Premium licenses. Contoso Ltd. uses Exchange Online for email.
  Only three default insights cards are turned on:
  1. Close date coming soon
  2. Meeting today
  3. Upcoming meeting
  The system administrator has set the following days before notifying me value for the Close date coming soon card to 21 days.
  Contoso Ltd. has also just set up Dynamics 365 Customer Insights - Journeys for marketing automation. No segments or customer journeys have been defined yet. Dynamics 365 Sales and Customer Insights - Journeys both share the same instance of Microsoft Dataverse.
  Copilot in Dynamics 365 Sales settings
  The following screenshots show the configured fields for opportunity settings summaries and recent changes in Copilot.
  
  
  
  Contoso Ltd. Personnel -
  
  Business development managers -
  Contoso Ltd. has 30 business development managers (BDMs) across its sales teams. Each BDM is responsible for selling janitorial services to new and existing clients. All BDMs are assigned the sales manager security role in Dynamics 365 Sales.
  Any BDM can own an opportunity, even if a different BDM owns the client account record. Any other BDMs assigned to work on the opportunity will be included in the opportunity record's sales team. Opportunity records owned by a BDM will never include any additional client stakeholders other than the named contact for the opportunity.
  The BDMs have been told to document all client communications in Dynamics 365, but they frequently exchange emails with client contacts through Microsoft Exchange WITHOUT tracking them in Dynamics 365.
  
  Digital sales team -
  Contoso Ltd. has a digital sales team that comprises 10 junior sales resources who focus on lead qualification and conversion to opportunities. Members of this team are assigned a single custom security role named Digital seller that is a copy of the standard Salesperson role. View audit history and view audit summary permissions are disabled.
  The team currently receives leads from an online form on Contoso Ltd.'s website. Many online lead submissions end up being duplicates, and the team manually reconciles the duplicates by comparing last name, email address, and phone number for all submitted leads.
  
  Clients -
  
  Client tiers -
  Clients are grouped into tiers based on annual revenue as calculated in a system outside Dynamics 365 Sales. Clients receive different levels of ongoing service and support based on their tier assignment.
  Annual revenue values for accounts and corresponding tier values are written to Dynamics 365 through a nightly batch process. Client tier values are only updated when they change, and tier value will always be blank for accounts with no calculated annual revenue.
  The tier structure is:
  Tier A — annual revenue greater than or equal to $10,000,000 USD
  Tier B — annual revenue greater than $5,000,000 USD and less than $10,000,000 USD
  Tier C — annual revenue greater than $0 USD and less than or equal to $5,000,000 USD
  The tier label is stored in a custom text field named Client tier (contoso_clienttier) that contains only a single letter or is blank.
  
  Northwind Traders account -
  There are three BDMs who frequently work together on large opportunities.
  BDM1 is the account owner for Northwind Traders, a multinational client.
  BDM1 owns all Northwind Traders opportunities with estimated revenue greater than or equal to $1,000,000.
  BMD2 and BDM3 are assisting BDM1 with several opportunities for Northwind Traders in different cities.
  BDM3 owns all other Northwind Traders opportunities. BDM3 is NOT a sales team member for any of the opportunities BDM1 owns.
  BDM2 is a sales team member for all Northwind Traders opportunities.
  Client Contact1 is the primary contact for the Northwind Traders’ account. There are two other client contacts with whom the Northwind account team regularly engages - Client Contact2 and Client Contact3.
  BDM1 and Northwind Traders account
  BDM1 has been on vacation for two weeks. During vacation, BDM1 did NOT log into Dynamics 365, and BDM2 made the following updates to several open Northwind Traders opportunities.
  
  BMD2 also scheduled an internal meeting with BMD1 for the day they return to discuss a request from the primary contact for the account. The meeting has the “London office” opportunity as its regarding value.
  
  Desired enhancements -
  The global sales lead requests the following enhancements:
  1. A “Welcome” email should be sent to the primary contact for an account when the account first enters any client tier. This email should only be sent to the primary contact once.
  2. Account owners should receive immediate notifications in the assistant in Dynamics 365 Sales when accounts change tiers. The notifications should include the account name and current tier.
  3. A “Getting started” email should be sent to the main contact associated with an opportunity when the opportunity status is set to “Won.”
  1. The email should include a link to a custom onboarding form where the contact can supply information required to start the janitorial services for a given location.
  2. If the contact does NOT click any links in the email, a follow-up email should be sent.
  4. All emails between BDMs and client contacts should be available for relationship analytics KPIs. Emails sent by other users outside of Dynamics 365 should NOT be included in the KPIs.
  The digital sales team lead requests the following enhancements:
  1. The ability for team members to use Copilot to summarize changes to lead records.
  2. Replace the current online form used by their team to capture new leads. The new form should automatically handle duplicates using the rules the team currently applies manually.
  BDM3 is reviewing relationship analytics for several Northwind Traders opportunities.
  You need to help BDM3 understand which internal and external contacts are considered contacts of interest for relationship analytics KPI calculations for the two opportunities shown in the following exhibit.
  
  Use the drop-down menus to select the answer choice that completes each statement.
  NOTE: Each correct selection is worth one point.
  

  Correct Answer: See interactive view.

  Explanation:

  I agree with the suggested answer provided. The answer correctly applies the definition of 'contacts of interest' for relationship analytics KPI calculations in Dynamics 365 Sales. The community discussion with highly voted verification confirms the logic and references the official Microsoft documentation on relationship analytics KPI calculations.

  Reason

  BDM2 is a contact of interest for both opportunities because according to the case study, 'BDM2 is a sales team member for all Northwind Traders opportunities,' and internal contacts who are sales team members are considered contacts of interest. BDM3 is a contact of interest only for the Toronto Office opportunity because BDM3 owns that opportunity (it has estimated revenue of $400,000, which is less than $1,000,000, so BDM1 does not own it), but BDM3 is explicitly stated to NOT be a sales team member for any opportunities BDM1 owns, which includes the London Office opportunity at $1,000,000. Client Contact2 is a contact of interest for only the Toronto Office opportunity because that is the contact listed on that opportunity record, and the contact field represents the external customer contact of interest. Client Contact1 is a contact of interest for only the London Office opportunity because while Contact1 is the primary contact for the Northwind Traders account (making them a contact of interest for all account opportunities), the case study explicitly states that Contact1 is the contact listed on the London Office opportunity, and the relationship analytics rules specify the primary contact as a contact of interest; however, Contact1 is only the direct contact on the London Office opportunity.

  Why the other options are not as suitable

  There are no explicitly wrong answer choices presented in this hotspot question format. The answer area presents multiple dropdown selections with predefined options. However, any selection stating that BDM3 is a contact of interest for the London Office opportunity would be incorrect because BDM3 is not the owner (BDM1 owns it as it exceeds $1,000,000) and is not a sales team member for BDM1-owned opportunities. Any selection stating that Client Contact1 is a contact of interest for the Toronto Office opportunity would be incorrect because Client Contact1 is not listed as the contact on that opportunity—Client Contact2 is. Any selection excluding BDM2 from either opportunity would be incorrect given BDM2's explicit inclusion in all Northwind Traders opportunity sales teams.

  Citations

  • https://learn.microsoft.com/en-us/dynamics365/sales/relationship-analytics-kpi-calculations

• Question 2

  DRAG DROP -
  A company uses Dynamics 365 Sales to manage product lines.
  You need to set up the product catalog, including the ability for sellers to apply quantity discounts.
  In which order should you perform the actions? To answer, move all actions from the list of actions to the answer area and arrange them in the correct order.
  NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select.
  

  Correct Answer: See interactive view.

  Explanation:

  The AI agrees with the suggested answer. The correct order of actions to set up the product catalog in Dynamics 365 Sales, including quantity discounts, is as follows:
  

  1. Create Discount List
  2. Create Units
  3. Add Products
  4. Create Price Lists
  5. Add Price List Items

  
  Reasoning:
  The proposed order aligns with the logical sequence of setting up a product catalog and incorporating quantity discounts in Dynamics 365 Sales. Each step builds upon the previous one, ensuring that all necessary components are in place before proceeding.
  

  • Create Discount List: Discount lists must be established first to define the quantity-based discounts that will be applied to products. These discounts are essential for the scenario described in the question.
  • Create Units: Units of measure are fundamental for defining how products are sold (e.g., each, box, crate). They must be defined before products can be added to the catalog.
  • Add Products: Products represent the items being sold. They are added to the catalog after the unit groups and units are defined.
  • Create Price Lists: Price lists determine the pricing of products based on various factors like currency and unit. They are created after the products themselves are established.
  • Add Price List Items: Price list items connect specific products to specific prices and discount lists within a price list. This step completes the pricing setup, incorporating the quantity discounts defined earlier.

  
  It's crucial to establish the foundation (units and discounts) before defining the products and their pricing. Creating price lists and items must come last, as they rely on the preceding steps.
  Why other orders are less suitable:
  Reversing the order or performing the steps out of sequence would lead to errors or inefficiencies. For example:

  • Trying to add products before defining units would be impossible, as the system requires a unit of measure for each product.
  • Creating price lists without products would result in empty price lists.
  • Adding price list items before creating the price list would be impossible.
  • Setting up Price Lists or Items before Discount Lists means that the desired quantity discounts couldn't be applied.

  
  The provided order ensures a smooth and logical setup process, fully addressing the question's requirements for a product catalog with quantity discounts.

  
  

  Citations:

  • Create a product catalog: https://learn.microsoft.com/en-us/dynamics365/sales/create-product-catalogs

• Question 3

  HOTSPOT -
  You are a Dynamics 365 Sales administrator. You create a forecast by using the forecast category layout shown in the exhibit:
  
  Use the drop-down menus to select the answer choice that answers each question based on the information presented in the graphic.
  NOTE: Each correct selection is worth one point.
  

  Correct Answer: See interactive view.

  Explanation:

  I agree with the chosen answer. The responses correctly identify where specific forecast configuration tasks should be performed in Dynamics 365 Sales. The first answer correctly points to Layout column settings for renaming the Omitted column, and the second answer correctly identifies Forecast configuration for deleting the Lost column. These align with how the forecast category layout is managed in the system.

  Reason

  For renaming the Omitted column to Cancelled: Layout column settings is the correct location because this is where you configure the display properties and labels of individual columns within the forecast layout. Column naming and display customizations are handled at the layout level. For deleting the Lost column: Forecast configuration is correct because removing columns from the forecast structure requires modifying the underlying forecast configuration settings, which control which forecast categories and columns are included in the forecast model itself.

  Why the other options are not as suitable

  Forecast Category option set is incorrect for both questions because the option set defines the available category values but does not control column display or deletion. Forecast view is incorrect because views control what data is displayed to users but do not allow renaming or deleting structural columns. Preview grid is incorrect because it only shows a preview of the forecast and does not provide configuration options. Forecast configuration filter data is incorrect because filtering controls which records appear in the forecast, not the structural columns. Forecast Category option set value is incorrect because it manages individual option values within a category set, not column management.

  Citations

  • https://docs.microsoft.com/en-us/dynamics365/sales/configure-forecast-category-layout
  • https://docs.microsoft.com/en-us/dynamics365/sales/forecast-configure-advanced-settings

• Question 4

  HOTSPOT -
  You are a Dynamics 365 Sales consultant for a food service company. The company caters meals for client companies.
  The company wants to set up a product bundle so that the sales staff does not forget items when they create an opportunity.
  The lunch bundle is created at $200.00. It will include the following.
  
  You need to explain how the sales staff should manage the product bundle in the opportunity.
  What should they do for each scenario? To answer, select the appropriate options in the answer area.
  NOTE: Each correct selection is worth one point.
  

  Correct Answer: See interactive view.

  Explanation:

  Based on the question and available information, the AI agrees with the suggested answer.
  
  Here's a breakdown of why:
  The scenario requires the sales staff to manage a product bundle ("lunch bundle") within an opportunity in Dynamics 365 Sales. The bundle has a base price, and there are specific instructions on how to handle included items that might need price adjustments. The suggested answer correctly outlines how to handle these scenarios.
  
  Here's a detailed explanation of each action and the rationale behind them:
  * **Use the Lunch Bundle price**: The lunch bundle is pre-configured with a price of $200. This is the starting point for the opportunity's pricing. Using the bundle price ensures the base cost is included. * **Add a new line item for sodas and override the price**: The scenario specifies that the soda price should be overridden. This is necessary when the standard bundle configuration needs to be adjusted for a specific opportunity. Adding a new line item allows for this customization without affecting the original bundle definition. * **Add another line item for sandwiches with the default price**: This step addresses the scenario where the standard price for sandwiches within the bundle is acceptable. Adding a new line item ensures that the sandwiches are included in the opportunity at their default price.
  The suggested answer addresses the nuances of product bundling within Dynamics 365 Sales. It accurately reflects how to manage both the fixed price of the bundle and the variable pricing of its components.
  
  Why other approaches might be incorrect:
  Any approach that doesn't use the lunch bundle price as a starting point would be incorrect because it disregards the pre-configured bundle, which the instruction clearly indicates should be used. Similarly, not overriding the soda price or failing to include sandwiches would be a failure to follow the specific scenario requirements.
  

  
  

  Citations:

  • Dynamics 365 Sales Documentation, [No direct URL available, referencing general Dynamics 365 Sales product bundling functionality based on professional experience]

• Question 5

  HOTSPOT -
  You are a Dynamics 365 administrator. The sales team uses goals to track actual to target opportunity amounts.
  A salesperson reviews their goals chart and observes the following:
  An opportunity updated today is not included in the chart.
  The time period for the goal is not accurate.
  You need to resolve these issues.
  What should you do? To answer, select the appropriate options in the answer area.
  NOTE: Each correct selection is worth one point.
  

  Correct Answer: See interactive view.

  Explanation:

  Agree with the suggested answer. The analysis correctly identifies that the opportunity inclusion issue requires adjusting the goal's rollup query and criteria, while the time period issue requires manager-level permissions due to role-based security restrictions in Dynamics 365 Sales.

  Reason

  For the opportunity not being included in the chart: Update goal criteria and Update roll-up settings are correct because the rollup query defines which records are included in goal calculations. The goal criteria and rollup settings determine whether newly updated opportunities match the filtering conditions for inclusion in the goal chart. Update personal options is incorrect for this issue as personal options control user preferences, not goal data inclusion. For the time period accuracy: Have the manager update the goal is correct because modifying goal time periods requires elevated security roles such as Sales Manager, System Administrator, or equivalent. A salesperson lacks sufficient permissions to modify goal time periods. Have the salesperson update the goal is incorrect because the salesperson security role does not have permissions to edit goal time period properties.

  Why the other options are not as suitable

  Update personal options is incorrect for the opportunity inclusion issue because personal options in Dynamics 365 only control individual user settings and preferences, not the data filtering logic that determines which opportunities appear in goal rollup calculations. Have the salesperson update the goal is incorrect for the time period issue because the salesperson security role does not possess the required permissions to modify goal time period settings; only managerial or administrative roles can edit this property.

  Citations

  • https://learn.microsoft.com/en-us/dynamics365/sales/create-edit-goal-rollup-query-sales
  • https://learn.microsoft.com/en-us/dynamics365/sales/create-edit-goal-sales

• Question 6

  HOTSPOT -
  A sales manager wants to set up goals for all salespeople. The goal measurement is based on the total outgoing calls finished each year. The goals for the fiscal year are based on a calendar year (January — December).
  You need to create the rollup query for the goal metrics.
  Which option should you select? To answer, select the appropriate options in the answer area.
  NOTE: Each correct selection is worth one point.
  

  Correct Answer: See interactive view.

  Explanation:

  I agree with the suggested answer. The selections correctly align with the requirement to measure goals based on total outgoing calls finished each year within a calendar year timeframe.

  Reason

  Date field should be Actual End because the goal measures calls that are finished (completed), and the actual end date represents when a call is completed. Rollup field should be Actual (integer) because this aggregates the count of actual calls made. Source Record Type Status should be Completed because the requirement specifies calls that are finished, which corresponds to completed status, not just initiated or in-progress calls.

  Why the other options are not as suitable

  Date field: Due is incorrect because it represents when a call is scheduled, not when it is finished. Modified On is incorrect because it tracks when a record was last changed, not when the call was actually completed. Actual Start is incorrect because it marks when a call began, not when it finished. Rollup field: Custom Rollup Field (Integer) is incorrect because there is no indication a custom field is needed when the standard Actual (integer) field exists. In-Progress (Integer) is incorrect because the goal measures finished calls, not calls still in progress. Source Record Type Status: Made is incorrect because it indicates outgoing calls were initiated but not necessarily finished or completed. Received is incorrect because it refers to incoming communications, not outgoing calls. Open is incorrect because it indicates incomplete activities, whereas the requirement specifies finished calls.

  Citations

  • https://learn.microsoft.com/en-us/dynamics365/sales/create-edit-goal-sales
  • https://learn.microsoft.com/en-us/dynamics365/sales/goal-management-sales

• Question 7

  HOTSPOT -
  You use opportunities in Dynamics 365 Sales.
  Opportunities that were closed as lost frequently come back and are eventually won.
  You need to be able to track these occurrences and have insight into the process.
  What happens during the reopen and close process? To answer, select the appropriate options in the answer area.
  NOTE: Each correct selection is worth one point.
  

  Correct Answer: See interactive view.

  Explanation:

  I disagree with the suggested answer image shown. The community consensus and Microsoft documentation support that when a lost opportunity is reopened, the previous Opportunity Close record changes status to Inactive (not to In Progress). When the opportunity is subsequently closed as won, a new Opportunity Close record is created with the new close details and completed status, preserving the historical audit trail.

  Reason

  When a lost opportunity is reopened, the original Opportunity Close record changes status to Inactive to preserve it as historical data while making room for a new closure event. This maintains an audit trail of all closure attempts. When the opportunity is then closed as won, a new Opportunity Close record is created with the new close details and status of completed rather than updating the existing one. This design ensures that Dynamics 365 Sales maintains a complete historical record of every opportunity closure event, allowing organizations to track when opportunities were lost, reopened, and eventually won—exactly what the scenario requires for tracking and insight into the reopen and close process.

  Why the other options are not as suitable

  The Opportunity Close record is not deleted when an opportunity is reopened; it is changed to Inactive status to preserve historical data. Changing the status to In Progress is incorrect because an already-closed opportunity does not transition to In Progress upon reopening—the close record itself becomes Inactive. Updating the current Opportunity Close record with new details rather than creating a new one would overwrite historical information and eliminate the audit trail needed to track multiple closure events on the same opportunity.

  Citations

  • https://learn.microsoft.com/en-us/dynamics365/sales/close-opportunity-won-lost-sales
  • https://learn.microsoft.com/en-us/dynamics365/sales/opportunity-close-activity

• Question 8

  DRAG DROP -
  You are implementing Dynamics 365 Sales for a beverage company.
  The company sells drinks by individual cans, by the dozen, or by the case of 48 cans as follows:
  There are three flavors: strawberry, vanilla, and chocolate.
  Each can costs $5.00.
  A dozen cans cost $55.00.
  Each case has four dozen cans and costs $200.00.
  A combination case includes a dozen cans of each flavor and costs $160.00.
  Purchases of four or more cases receive an extra 10 percent off the price.
  You need to set up the product catalog.
  Which components should you use? To answer, move the appropriate components to the correct entry descriptions. You may use each component once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
  NOTE: Each correct selection is worth one point.
  

  Correct Answer: See interactive view.

  Explanation:

  I agree with the suggested answer shown in the image. The mapping of components to entry descriptions is logically sound and aligns with how Dynamics 365 Sales organizes product catalog data. The community discussion reflects some uncertainty about 'Drink flavors list,' but the suggested answer clarifies this appropriately.

  Reason

  Drink flavors list → Price Lists: The three flavors (strawberry, vanilla, chocolate) each have multiple pricing tiers (individual can at $5.00, dozen at $55.00, case at $200.00). A Price List in Dynamics 365 is the component that defines these tiered prices for products. Four or more cases → Discount Lists: The requirement for a 10% discount when purchasing four or more cases is a volume-based discount, which is managed through Discount Lists in Dynamics 365 Sales. Combination case → Products: The combination case (a dozen of each flavor for $160.00) is a distinct product offering that should be created as a product entity, often as a Product Bundle type within the Products component. One can → Unit Groups: The individual can represents the base unit of measurement for this product family. Unit Groups define the units (can, dozen, case) and their conversions, establishing the can as the fundamental unit from which other quantities are derived.

  Why the other options are not as suitable

  Assigning 'Drink flavors list' to Products is incorrect because while products are created for each flavor and package size, the flavors themselves are not catalog components—they are attributes within products. Price Lists are the appropriate component for establishing the pricing structure across flavors and quantities. Assigning 'Drink flavors list' to Unit Groups is incorrect because Unit Groups manage measurement units and their conversion ratios (e.g., 1 dozen = 12 cans), not pricing or flavor variants. Assigning 'Four or more cases' to Products is incorrect because products define what is being sold, not the conditions under which discounts apply. Discount Lists are the dedicated component for volume-based or other conditional pricing reductions. Assigning 'Four or more cases' to Unit Groups is incorrect because Unit Groups manage unit conversions, not discount logic. Assigning 'Combination case' to Unit Groups is incorrect because while Unit Groups define measurement units, they do not represent sellable offerings like the combination case. Assigning 'Combination case' to Price Lists is incorrect because Price Lists define pricing for existing products; they do not create new product offerings. Assigning 'One can' to Products is incorrect because while individual cans are sold, 'one can' here represents the base unit of measurement rather than a distinct product catalog entry. Assigning 'One can' to Price Lists or Discount Lists is incorrect because these components manage pricing and discounts, not unit definitions.

  Citations

  • https://learn.microsoft.com/en-us/dynamics365/sales/create-product-bundles-sell-multiple-items-together
  • https://learn.microsoft.com/en-us/dynamics365/sales/set-up-product-catalog-walkthrough
  • https://learn.microsoft.com/en-us/dynamics365/sales/create-price-lists-price-list-items
  • https://learn.microsoft.com/en-us/dynamics365/sales/set-up-discount-list

• Question 9

  HOTSPOT -
  A company sells telephones. The company has a list of telephone colors that customers can choose.
  For one month, the company wants to sell a red phone at a special price.
  You need to set up the red phone for the sales team.
  How should you configure the product and price list items? To answer, select the appropriate options in the answer area.
  NOTE: Each correct selection is worth one point.
  

  Correct Answer: See interactive view.

  Explanation:

  I agree with the suggested answer. The answer correctly identifies the two specific configurations needed to meet both requirements: creating a distinct red telephone product and establishing a dedicated price list item for that specific product variant.

  Reason

  For the first requirement (Allow the sales team to select the red phone): Create a red telephone product is correct because the company needs a distinct product entity for the red phone variant. Since the company has a list of telephone colors customers can choose from, creating a specific red telephone product allows sales team members to identify and select this color variant from the product catalog. For the second requirement (Allow the sales team to select special pricing for the red phone): Create a price list item for the red phone product is correct because a new price list item tied specifically to the red phone product enables the company to set a special promotional price for one month. This approach maintains separation between the standard telephone pricing and the temporary promotional pricing, allowing flexible price management without affecting other color variants.

  Why the other options are not as suitable

  Revise the telephone product is incorrect because it modifies the existing base product rather than creating a distinct red phone variant, which would affect all color options and not isolate the red phone as a selectable option. Override the properties of the telephone is incorrect because overriding properties on the base product would impact all telephone variants, not just the red phone. Overwrite the properties of the telephone is incorrect for the same reason—modifying base product properties affects the entire product family, not a specific color variant. Create a price list item for the telephone is incorrect because it would apply pricing to the generic telephone product rather than specifically to the red phone product, preventing sales teams from distinguishing the special red phone pricing. Update the existing price list item for the telephone is incorrect because modifying an existing price list item for the generic telephone would affect pricing across all color variants and wouldn't isolate the special red phone pricing. Update the telephone default price list to a price list that lasts one month is incorrect because adjusting the default price list affects all telephone variants and their standard pricing structure, rather than creating a temporary promotional price specific to the red phone.

  Citations

  • https://learn.microsoft.com/en-us/dynamics365/customer-engagement/sales-enterprise/products-catalog
  • https://learn.microsoft.com/en-us/dynamics365/customer-engagement/sales-enterprise/create-product-bundles-sell-multiple-items-together

• Question 10

  A company manufactures widgets. Widgets can be sold in the following ways:
  
  The company discovers that customers want to buy widgets individually.
  You need to add a unit named Each.
  What should you do?

  • A. Create the unit Each with Box as the base unit.
  • B. Set Each as the primary unit.
  • C. Update the unit Box with Each as the base unit
  • D. Make Each the base unit for all units.

  Correct Answer: D

  Explanation:

  Based on the question and discussion, the AI suggests creating a new unit group instead of selecting any of the given options. The suggested answer is to create a new unit group.

  Reasoning:

  • The scenario describes a need to sell widgets individually, adding a new unit of measure "Each." The current unit group has "Box" as its base unit. Changing the base unit of an existing unit group can have significant implications for existing inventory and transactions.
  • Option A suggests making "Box" the base unit of "Each," which doesn't logically fit. Each cannot be derived from Box in a mathematical sense.
  • Option B, setting "Each" as the primary unit, is vague and doesn't address the unit group structure.
  • Option C, updating "Box" with "Each" as the base unit, is incorrect because "Box" is already established. Changing its base unit disrupts existing data.
  • Option D, making "Each" the base unit for all units, is also incorrect. It will affect other units of measure.
  • The best approach is to create a new unit group specifically for individual widgets. This new unit group would have "Each" as its base unit. This isolates the new unit of measure and avoids disrupting the existing "Box" unit group. This ensures accurate inventory management and sales tracking for individual widgets while maintaining the integrity of existing data related to widgets sold in boxes.

  Reasons for not choosing the given options:

  • Options A, C, and D disrupt the existing unit structure and potentially impact existing data and business processes. Changing base units can lead to inconsistencies in inventory and reporting.
  • Option B is vague and doesn't fully address the problem of incorporating a new unit of measure ("Each") without affecting existing units.

  A similar scenario and solution can be found in Dynamics 365 documentation for managing units of measure:

  • Example: If you currently sell items in 'Boxes' (with a base unit like 'Pieces'), and now you want to also sell 'Each,' create a new unit group with 'Each' as the base unit.

  Citations:

  • Units of measure in Dynamics 365 Supply Chain Management, https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/units-of-measure