Microsoft AB-210 Practice Test Questions Answers

The correct answer is Opportunity summary . The requirement is not to score the opportunity, show the next activity, or display health indicators; it is to reduce the seller’s manual review effort before contacting the customer. Microsoft’s Copilot capability for Dynamics 365 Sales provides AI-generated summaries for opportunity records so sellers can quickly understand key deal context, related activities, emails, and important history without reading the full timeline manually. Microsoft specifically states that Copilot record summarization generates concise summaries of key information from sales records such as opportunities, leads, and accounts.

Because the company uses a custom opportunity form , the opportunity summary widget must be added to that form. Microsoft’s implementation guidance explicitly flags custom opportunity forms and asks whether the opportunity summary widget has been added, and the Copilot summary documentation notes that the opportunity summary widget is available by default on the standard form but must be added to custom forms. Up next guides sellers to the next activity, Health score and Predictive opportunity scoring evaluate opportunity risk or likelihood, and Timeline highlights is narrower than the full AI-generated opportunity overview.

References/topics: Copilot opportunity summary; custom opportunity forms; AI-generated sales record summaries; seller productivity in Dynamics 365 Sales.

The solution does not meet the goal. The requirement is explicit: AI billing must use pre-paid credits . Microsoft’s Dynamics 365 Sales billing guidance separates Copilot and agent billing into two models: prepaid capacity and pay-as-you-go . Prepaid capacity uses Copilot Studio message pack subscriptions that are purchased in advance, while pay-as-you-go bills for the actual number of messages consumed during the month.

Configuring capacity overages to a billing plan is not the prepaid-credit model. Overages are tied to consumption beyond allocated capacity and are handled through billing-plan/pay-as-you-go behavior. That conflicts with the requirement to use pre-purchased credits. For prepaid billing, the correct approach is to purchase Copilot Studio message packs or capacity packs and assign that prepaid capacity to the Dynamics 365/Power Platform environment. Microsoft’s Power Platform capacity guidance states that prepaid capacity can be assigned to environments, and when prepaid capacity is exhausted, administrators must reallocate capacity, purchase more credits, or enable pay-as-you-go billing.

Therefore, configuring overages may support monthly usage billing, but it does not satisfy the stated requirement that billing must use prepaid credits.

References/topics: Dynamics 365 Sales consumption-based billing; prepaid capacity; Copilot Studio message packs; Copilot credit capacity; pay-as-you-go overage handling.

Requirement

Configuration

Define shared properties for several drone models

Product family

Combine drones and accessories into a package

Bundle

Represent a single drone model

Product

The correct configuration is based on the product catalog hierarchy in Dynamics 365 Sales. A Product family is used when several related products need to share common characteristics or inherited properties. For example, a drone product family can define shared attributes such as flight time, camera type, battery compatibility, or warranty tier, and individual drone models can inherit or specialize those attributes. This is exactly what the requirement means by defining shared properties for several drone models.

A Bundle is used when multiple sellable products are combined into one package. If the company wants to sell a drone together with spare batteries, propellers, carrying cases, or accessories, that package should be configured as a bundle. The seller can then add the bundle to an opportunity, quote, order, or invoice instead of manually selecting each component.

A Product represents a single sellable item, such as one specific drone model. Price list is not correct for any of these requirements because price lists define pricing structures and currencies; they do not define catalog hierarchy, shared product properties, or bundled offerings.

References/topics: Dynamics 365 Sales product catalog; product families; product bundles; products; product hierarchy and catalog configuration.

Issue

Action

Opportunity updated today is NOT included in the chart

Update roll-up settings

Time period for the goal is inaccurate

Have the manager update the goal

For the opportunity updated today not appearing in the goals chart, the issue is the goal rollup timing , not the opportunity record itself. Dynamics 365 Sales goal actuals are calculated through rollup processing. Microsoft states that automatic goal rollup duration and frequency are controlled from the Goals tab in system settings, and that manual rollup can also be performed when needed. Therefore, the correct action is to update the roll-up settings so goal charts reflect recent opportunity changes more appropriately. Microsoft also notes that selecting Recalculate updates goal actuals based on the latest data, confirming that goal charts depend on rollup recalculation rather than instant real-time updates.

For the inaccurate goal time period, the correct action is to have the manager update the goal . In Dynamics 365 Sales goal management, the goal manager is responsible for setting or modifying goal targets, adjusting the goal time period, and assigning the goal owner. The salesperson is typically the goal owner who is measured against the target, but the manager controls the goal definition and period.

References/topics: Dynamics 365 Sales goals; goal rollup settings; goal recalculation; goal manager responsibilities; opportunity target tracking.

The correct answer is Goal metric . In Dynamics 365 Sales, the goal metric defines how goal performance is calculated. Microsoft explains that each goal uses a goal metric to determine how the goal is tracked, and goal metrics can track actual, in-progress, and custom values through rollup fields. For won opportunity revenue, the metric can use the Opportunity table as the source and roll up the actual value for opportunities that are closed as won.

The quarterly requirement is handled by the goal’s time period. The goal metric specifies the calculation logic, including the source table, source attribute, date attribute, and source status such as Won. Microsoft’s goal metric documentation states that the date attribute is validated against the goal time period, so records participate in the rollup only when their date falls between the goal start and end dates. A rollup query is not the best answer because it only applies additional filtering criteria to an existing goal metric; it does not create the core calculation.

References/topics: Dynamics 365 Sales goals; goal metrics; rollup fields; won opportunity calculations; quarterly goal tracking.