Microsoft Dynamics 365 Fundamentals CRM MB-910 (MB-910) — Questions 226–300

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because changing the data retention policy to zero days would delete all data for all customers, not just the specific customer who requested deletion, and it does not provide a targeted, auditable deletion mechanism required for GDPR compliance. Option B is wrong because reconfiguring data sources to exclude the customer would only prevent future data ingestion from that source, but it does not delete existing data already stored in Customer Insights, leaving the customer's data intact. Option D is wrong because manually deleting records from the source systems does not remove the data that has already been ingested and unified in Customer Insights; the data would still exist in the Customer Insights data store and would not satisfy the GDPR deletion request.

Why this answer

Why this answer

Why this answer

Why this answer

Why these pairings

Why this answer

How to eliminate wrong answers

Option A is wrong because assignment rules are used to automatically assign records to a user or team based on conditions, but they do not support routing based on product interest and geographic region in the same way as routing rules; assignment rules are more basic and lack the advanced condition evaluation and queue routing capabilities. Option C is wrong because queues are containers for holding records that need to be worked on, but they do not automatically assign leads; they require manual or rule-based assignment to move records out of the queue. Option D is wrong because business process flows provide a guided workflow for data entry and stages, but they do not handle automatic assignment or routing of leads based on attributes.

Why this answer

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option B (Predictive scoring) is wrong because it analyzes unified data to predict future behaviors (e.g., churn, next purchase), but it does not perform the initial data merging required to create the 360-degree view. Option C (Copilot for Customer Insights) is wrong because it provides AI-assisted natural language interactions and insights on existing data, but it cannot unify raw data from multiple sources. Option D (Customer segmentation) is wrong because it groups already-unified customer profiles into segments for targeting, but it does not perform the data ingestion and matching needed to build the unified view.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because a sales playbook is a collection of best practices, documents, and guidance, not an automated process that enforces a consistent sequence of stages. Option B is wrong because a workflow automates specific actions (e.g., sending an email when a lead is created) but does not define or enforce a multi-stage sales pipeline. Option D is wrong because a dialog process is a legacy feature for guided interactions (e.g., scripted conversations) and is not designed to enforce a linear sales process across records.

Why this answer

Why this answer

Why this answer

Why this answer

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because Unification is the process of matching and merging customer records from multiple data sources into a single profile, not for predicting churn. Option B is wrong because Measures are used to define KPIs and aggregate metrics (e.g., total purchases) but do not apply machine learning to forecast future behavior. Option C is wrong because Segments are static or dynamic groups of customers based on rules or conditions, not predictive models that output a churn probability.

Why this answer

How to eliminate wrong answers

Option B (Ingest) is wrong because the Ingest step is solely responsible for importing raw data from sources into Customer Insights, not for defining how duplicates are identified or merged. Option C (Merge) is wrong because the Merge step is the final action that consolidates duplicate records into a single profile after matching has already occurred; it does not control the matching rules themselves. Option D (Enrich) is wrong because the Enrich step adds external data (e.g., demographics or third-party attributes) to profiles and has no role in duplicate detection or matching rule configuration.

Why this answer

How to eliminate wrong answers

Option A is wrong because Appointment is used for scheduling meetings or events with a start and end time, not for logging a real-time phone interaction. Option B is wrong because Email is for tracking sent or received email messages, not for recording a phone call conversation. Option D is wrong because Task is for tracking to-do items or follow-up actions, not for capturing the details of a completed phone call.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because Power Automate licenses are not a prerequisite for Copilot; Copilot uses its own AI engine, not Power Automate flows, to draft emails. Option B is wrong because there is no separate 'Copilot add-in' to purchase; Copilot capabilities are bundled with the Dynamics 365 Sales Premium license. Option D is wrong because user-level Copilot licenses are not assigned individually; the Copilot functionality is enabled at the organization level once the Sales Premium license is acquired, and all licensed users with appropriate roles can access it.

Why this answer

How to eliminate wrong answers

Option A is wrong because prediction models are used for forecasting future outcomes (e.g., churn probability) rather than calculating historical KPIs like average CLV. Option B is wrong because data unification is the process of matching and merging customer records from multiple sources into a unified profile, not for computing numeric metrics. Option C is wrong because creating a segment of recent customers only groups those customers for targeting or analysis, but does not calculate the average CLV value itself.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because the marketing team would have to manually remove customers from the segment, which is unlikely to cause a consistent daily decrease without their knowledge, and Customer Insights does not automatically remove customers based on campaign feedback. Option B is wrong because if the model failed to calculate scores, it would likely result in no scores or an error, not a gradual daily decrease in segment size; the model is retrained successfully each night. Option D is wrong because temporary unavailability of customer profiles due to data refresh would cause intermittent or zero segment size, not a consistent daily decrease, and Customer Insights handles data refreshes without removing profiles from segments permanently.

Why this answer

Why this answer

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because an enrichment is a process that adds external data (e.g., demographic or firmographic data) to existing customer profiles, not a prerequisite for joining internal tables to create a segment. Option C is wrong because a measure calculates aggregated values (e.g., sum of purchases) but cannot be created until the underlying tables are linked via a relationship; the measure depends on the relationship, not the other way around. Option D is wrong because a new data source is only needed if the purchase data is not already ingested into Customer Insights; the question states the purchase data is already in a separate table, so no new data source is required.

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because the account field on the incident is used to specify the customer account, but it does not automatically populate the service account on the work order; the service account must be set separately or derived from the incident configuration. Option C is wrong because the tax code on the incident determines tax calculations, not the service account or bill-to account; it is unrelated to account assignment. Option D is wrong because the work order type defines default values for work order fields like priority or work order summary, but it does not specify default accounts for service or billing; account assignment is handled by the incident configuration.

Why this answer

How to eliminate wrong answers

Option A is wrong because work order products record the parts and services associated with a work order for billing and scheduling, but they do not manage inventory tracking or stock levels on vans. Option B is wrong because purchase orders are used to procure inventory from suppliers, not to track existing inventory on vans or link parts to work orders. Option D is wrong because inventory transfers move stock between locations (e.g., warehouse to van), but they do not directly track which parts are consumed on a specific work order or provide the inventory adjustment functionality needed for van stock tracking.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because re-running data ingestion does not change the matching logic; it only reimports the same data, which would still produce the same duplicates. Option B is wrong because enrichment adds external data to profiles but does not alter the deduplication process or resolve existing duplicate matches. Option C is wrong because increasing the match confidence threshold would reduce the number of matches, potentially missing true duplicates, and does not address the issue of false duplicates that already have high confidence.

Why this answer

How to eliminate wrong answers

Option A is wrong because configuring the enrichment service (e.g., adding demographic or interest data from third-party providers) is a post-ingestion step that enhances existing unified profiles, not the first step. Option B is wrong because creating a customer segment relies on having unified customer profiles already built from ingested and resolved data; you cannot segment data that hasn't been ingested. Option D is wrong because defining measures for KPIs (e.g., customer lifetime value or churn rate) requires the unified customer profiles and aggregated data to be available, which depends on prior data ingestion and unification.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because Data sources are where you import and manage raw data tables (e.g., sales transactions), not where you define calculated metrics. Option B is wrong because Segments are used to group customers based on conditions or measures, but they do not define the calculation logic itself. Option C is wrong because Predictions are used for machine learning models (e.g., churn prediction), not for simple aggregations like average order value.

Why this answer

How to eliminate wrong answers

Option A is wrong because a score of 0.9 indicates a high, not low, likelihood of purchase within 30 days; the scale is directly proportional to probability. Option C is wrong because the score is the predicted probability of the event (purchase), not a measure of the model's confidence in its own prediction; model confidence is a separate metric often expressed as a confidence interval or accuracy score. Option D is wrong because this prediction is specifically configured for purchase likelihood, not churn risk; churn risk would be a different model with its own output score and interpretation.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because the NameAndCityMatch rule is not the only rule being evaluated; the EmailMatch rule can independently match records with the same email address, even if names and cities differ. Option B is wrong because confidence levels affect the certainty of a match but do not prevent a match from occurring when a rule condition is satisfied; a high confidence setting does not block matching. Option C is wrong because matching rules in Customer Insights are not required to all be satisfied; the system matches if any single rule's conditions are met, not all rules.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because Sales Insights is an AI-driven analytics and predictive scoring feature, not a LinkedIn data enrichment tool. Option C is wrong because Copilot for Sales is an AI assistant that helps with tasks like email drafting and meeting summaries, but it does not directly integrate LinkedIn data for lead enrichment. Option D is wrong because Relationship Assistant is a notification and reminder engine for sales activities, such as follow-ups and task alerts, and has no capability to import LinkedIn profile data.

Why this answer

Why this answer

Why this answer

Why this answer

Why this answer

Why this answer

Why this answer

Why this order

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option B is wrong because enrichment with third-party data is used to enhance customer profiles with external information (e.g., demographic or firmographic data), not to manage data privacy or deletion requests. Option C is wrong because creating a measure for customer lifetime value is an analytical feature that calculates a metric based on historical data, not a mechanism for erasing personal data. Option D is wrong because segmentation with dynamic membership is used to group customers based on real-time attributes or behaviors, not to handle erasure or consent compliance.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because KQL queries in Customer Insights do not perform predictive analytics; they operate on existing data, not machine learning models. Option B is wrong because the query filters for a single `CustomerID` rather than grouping or segmenting multiple customers with high purchase amounts. Option D is wrong because the query uses `sum()`, not `avg()`, so it calculates a total, not an average.

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because data unification rules affect how records from different sources are matched and merged, not the timeliness of data ingestion; aggressive matching would not fix a streaming delay. Option B is wrong because the ERP data is already being ingested correctly and updated daily via batch files; increasing its frequency does not address the delay in the real-time streaming data from the online store. Option C is wrong because reconfiguring the online store data source to use batch import would introduce additional latency, making the delay worse instead of resolving it; the streaming approach is designed for real-time ingestion and should be fixed, not replaced.

Why this answer

How to eliminate wrong answers

Option A is wrong because it describes a condition for spending above 2000, which would require a 'greater than' operator, not the 'between' range shown. Option B is wrong because it would require no filtering condition at all, but the segment clearly includes a condition on spending. Option D is wrong because it describes spending below 500, which would use a 'less than' operator, not the 'between' range that includes values from 500 to 2000.

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option B is wrong because Lead B's score of 45 is below the threshold of 50, so it will not be automatically qualified. Option C is wrong because Lead A does meet the threshold and is automatically qualified, so 'Neither' is incorrect. Option D is wrong because Lead B does not meet the threshold, so 'Both' is incorrect.

Why this answer

How to eliminate wrong answers

Option B (Task) is wrong because a Task is a generic activity for tracking to-do items or work assignments, not a dedicated entity for recording a phone call with metadata like call duration or direction. Option C (Appointment) is wrong because an Appointment represents a scheduled meeting with a start and end time, not an ad-hoc phone call that occurs in real time. Option D (Note) is wrong because a Note is an annotation or text attachment on a record, not an activity that can capture structured call details or be associated as a timeline activity.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because writing a SQL query in the data management interface is not the recommended approach for building segments in Customer Insights; the platform is designed to abstract SQL complexity through the Segment Builder. Option B is wrong because Power Automate is an automation tool for workflows and integrations, not a segment creation tool for Customer Insights; it cannot directly filter customers into a persistent segment based on measures. Option C is wrong because manually tagging each high-value customer profile is impractical, error-prone, and does not scale; Customer Insights is built for automated, dynamic segmentation based on unified data.

Why this answer

Why this answer

Why this answer

Why this answer