Microsoft Updated AB-210 Exam Questions and Answers by dorothea

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.

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.

The correct components are mobile security roles and appropriate user licenses . Installing the mobile app alone does not grant access to Dynamics 365 Sales records. Microsoft’s mobile setup guidance states that Dataverse security privileges control access to Dynamics 365 mobile apps, and the required mobile privilege is preconfigured for Sales roles but may need to be added to custom roles. It also states that the app must be shared with the security role assigned to the user, and users without the privilege can see an empty app list or an access error.

The license requirement is equally important. The Dynamics 365 Sales mobile experience exposes Sales Hub or Sales Professional according to the user’s license, so sellers must have the correct Dynamics 365 Sales license assigned before they can access the appropriate Sales app and records. Mobile offline profiles are used for offline synchronization scenarios; they are not the base requirement for record access after app installation. Inbound and outbound profiles are unrelated to Sales mobile access and are not used to authorize sellers in the mobile application.

References/topics: Dynamics 365 Sales mobile app; Dataverse security roles; mobile access privilege; Sales Hub mobile access; Dynamics 365 Sales licensing.