CCNA Describe Dynamics 365 Customer Insights Questions — Page 2 of 3

MCQeasy

A retail company wants to unify customer data from their e-commerce platform, loyalty program, and in-store POS system to create a single customer view. Which Dynamics 365 tool should they use?

A.Dynamics 365 Customer Service

B.Dynamics 365 Sales

C.Dynamics 365 Customer Insights - Data

D.Dynamics 365 Customer Voice

AnswerC

Customer Insights - Data unifies customer data from disparate sources into a single view.

Why this answer

Dynamics 365 Customer Insights - Data is the correct tool because it is specifically designed to ingest, unify, and enrich customer data from multiple sources (e-commerce, loyalty, POS) into a single customer profile using identity resolution and data transformation pipelines. This creates a 360-degree view of the customer, which is the core requirement described in the question.

Exam trap

The trap here is that candidates often confuse Customer Insights - Data with Customer Service or Sales because they all involve 'customer' data, but only Customer Insights - Data is a Customer Data Platform (CDP) built for data unification, not for service or sales workflows.

How to eliminate wrong answers

Option A is wrong because Dynamics 365 Customer Service is a case management and omnichannel engagement platform, not a data unification tool; it cannot ingest and merge disparate data sources into a single customer view. Option B is wrong because Dynamics 365 Sales focuses on managing sales pipelines, leads, and opportunities, and lacks the data ingestion and identity resolution capabilities needed to unify customer data from external systems. Option D is wrong because Dynamics 365 Customer Voice is a survey and feedback collection tool, not a data unification or customer data platform (CDP); it cannot merge e-commerce, loyalty, and POS data.

Practice this question →

MCQmedium

Refer to the exhibit. You are setting up a journey in Dynamics 365 Customer Insights - Journeys. The journey is triggered by a custom event 'ButtonClicked' and targets the 'Active Users' segment. After publishing, the journey does not start. What is the most likely cause?

A.The email template 'WelcomeEmail' does not exist.

B.The custom event requires authentication that is not configured.

C.The segment query uses an invalid field name for the Contact entity.

D.The trigger event does not include a 'ContactId' field.

AnswerC

An invalid field in the segment query prevents the segment from being evaluated.

Why this answer

A segment query referencing an invalid field name for the Contact entity will cause the segment to fail to resolve, preventing the journey from starting. In Dynamics 365 Customer Insights - Journeys, the journey engine validates the segment before launching; if the segment query contains a field that does not exist on the Contact entity, the segment cannot be evaluated, and the journey remains in a 'Draft' or 'Stopped' state.

Exam trap

The trap here is that candidates often assume journey startup failures are caused by missing event mappings or authentication issues, when in fact the most common cause is an invalid segment query that fails validation before the journey can begin.

How to eliminate wrong answers

Option A is wrong because a missing email template would cause an error when the journey attempts to send the email, but it would not prevent the journey from starting; the journey would still begin and fail later. Option B is wrong because custom events in Customer Insights - Journeys do not require authentication to be configured for the event to trigger the journey; authentication is only needed if the event source requires it, but its absence would not block journey startup. Option D is wrong because while a 'ContactId' field is typically needed to map the event to a contact, the journey can still start even if the field is missing; the issue would manifest as a failure to match the event to a contact, not as a failure to start the journey.

Practice this question →

MCQhard

You are the Dynamics 365 administrator for a healthcare provider that uses Customer Insights to manage patient profiles. The organization must comply with HIPAA regulations. Patient data is sourced from an electronic health record (EHR) system and from a patient portal. The EHR system is on-premises and sends data via a nightly batch file in CSV format. The patient portal sends data in real-time via API. You need to ensure that all patient data in Customer Insights is encrypted at rest and in transit. The platform already encrypts data at rest by default. However, you are concerned about the data in transit from the EHR system. What should you do?

A.Encrypt the CSV file before uploading.

B.Change the patient portal API to use batch uploads.

C.Configure the EHR data source to use SFTP for file transfer.

D.Enable double encryption at rest in Customer Insights.

AnswerC

Secures data in transit.

Why this answer

SFTP (SSH File Transfer Protocol) encrypts the CSV file during transit, addressing the concern about data in transit from the on-premises EHR system. Since the EHR sends data via a nightly batch file, using SFTP ensures the file is encrypted over the network, complementing the platform's default encryption at rest. This aligns with HIPAA requirements for protecting ePHI during transmission.

Exam trap

The trap here is that candidates may confuse encrypting the file itself (Option A) with securing the transfer channel, or assume that double encryption at rest (Option D) covers transit, when in fact HIPAA requires encryption both at rest and in transit, and the question specifically targets the transit vulnerability from the on-premises EHR system.

How to eliminate wrong answers

Option A is wrong because encrypting the CSV file before upload does not protect the data during transit; the file would still be transmitted in an unencrypted state unless the transfer protocol itself is secured. Option B is wrong because changing the patient portal API to use batch uploads addresses throughput or efficiency, not encryption in transit; the API already uses real-time data transfer, and batch uploads do not inherently add encryption. Option D is wrong because double encryption at rest in Customer Insights is a redundant security measure for data already encrypted at rest and does not address the data-in-transit concern from the EHR system.

Practice this question →

MCQhard

Your Customer Insights environment has multiple data sources with conflicting customer IDs. Some records from the loyalty system use email as ID, while the POS system uses a customer number. Which matching rule strategy should you use to unify these records?

A.Use conditional matching rules based on email and phone

B.Use exact match on customer numbers only

C.Set a priority order and keep the first source's ID

D.Use fuzzy matching on first and last name

AnswerA

Matches on shared attributes when ID is different.

Why this answer

Conditional matching rules allow you to define multiple conditions (e.g., match on email if available, otherwise match on phone) to resolve conflicts between different customer ID formats. This is the recommended approach in Dynamics 365 Customer Insights when data sources use different identifiers, as it maximizes the likelihood of correctly unifying records without requiring a single common key.

Exam trap

The trap here is that candidates often assume fuzzy matching on names is a safe fallback, but Microsoft specifically warns that name-based matching is error-prone and should only be used when no other unique identifiers are available.

How to eliminate wrong answers

Option B is wrong because exact match on customer numbers only would fail to unify records from the loyalty system that use email as ID, since those records lack a customer number. Option C is wrong because setting a priority order and keeping the first source's ID is a simplistic deduplication strategy that ignores the need to match records across sources, leading to duplicate or incomplete customer profiles. Option D is wrong because fuzzy matching on first and last name is unreliable for identity resolution, as names can be misspelled, changed, or shared by different individuals, and it does not leverage the available email or customer number identifiers.

Practice this question →

Multi-Selectmedium

A marketing team uses Dynamics 365 Customer Insights - Journeys. They need to create a journey that sends a personalized email to contacts based on their purchase history stored in a Dynamics 365 Sales entity. Which TWO components must they configure to ensure the journey runs correctly? (Choose two.)

Select 2 answers

A.Trigger

B.Email message

C.Condition

D.Query

E.Segment

AnswersA, E

A trigger starts the journey when specified conditions are met.

Why this answer

A trigger is required to start the journey when a specific event occurs, such as a contact being added to a segment or a custom event. In this scenario, the trigger initiates the journey based on the purchase history data from the Dynamics 365 Sales entity, ensuring the journey runs for the right contacts at the right time.

Exam trap

The trap here is that candidates often confuse the email message (the content) with the journey components that control execution, or they think a condition is always required, when in fact the trigger and segment are the two mandatory components to start and define the audience for the journey.

Practice this question →

MCQhard

A marketing team uses Dynamics 365 Customer Insights to create segments for targeted campaigns. They have a segment of 'High Value Customers' defined as those with a lifetime value in the top 20%. After a recent campaign, they want to evaluate the return on investment (ROI) for this segment. Which feature should they use to measure the campaign's impact on these customers?

A.Ingest campaign interaction data from external sources

B.Enrich profiles with demographic data

C.Use the built-in measures and analytics to compare segment performance before and after the campaign

D.Build a churn prediction model

AnswerC

Measures can track KPIs like revenue before and after campaign.

Why this answer

Dynamics 365 Customer Insights provides built-in measures and analytics that allow you to compare key performance indicators (KPIs) for a segment before and after a campaign. This directly enables ROI calculation by measuring changes in metrics like revenue or engagement specifically for the 'High Value Customers' segment, without needing external data ingestion or predictive models.

Exam trap

The trap here is that candidates may confuse data enrichment or ingestion features with analytical capabilities, mistakenly thinking that importing more data or building predictive models is required to measure campaign ROI, when the built-in measures and analytics are specifically designed for this comparison.

How to eliminate wrong answers

Option A is wrong because ingesting campaign interaction data from external sources is a data preparation step, not a feature for measuring ROI; it would require additional analytics to compare performance. Option B is wrong because enriching profiles with demographic data enhances profile attributes but does not provide campaign performance comparison or ROI measurement. Option D is wrong because building a churn prediction model is used to forecast customer attrition, not to evaluate the historical impact of a campaign on a specific segment.

Practice this question →

MCQhard

A company uses Dynamics 365 Customer Insights and wants to ensure that customer consent preferences from their email marketing system are reflected in customer profiles. The consent data includes a field 'ConsentGiven' (boolean). Which step is essential during data unification?

A.Add the email marketing system as a data source

B.Configure deduplication rules

C.Map the 'ConsentGiven' field to the unified customer entity

D.Create a segment based on consent

AnswerC

Ensures consent is included in profiles.

Why this answer

Mapping the 'ConsentGiven' field to the unified customer entity is essential because data unification in Dynamics 365 Customer Insights involves defining how source fields are projected into the target unified schema. Without this mapping, the consent preference from the email marketing system would not be included in the final unified customer profile, even if the data source is added and deduplication is configured.

Exam trap

The trap here is that candidates often confuse adding a data source (a necessary first step) with the actual field mapping required to bring specific attributes into the unified entity, assuming the system automatically includes all fields from the source.

How to eliminate wrong answers

Option A is wrong because adding the email marketing system as a data source is a prerequisite step, but it alone does not ensure the 'ConsentGiven' field appears in the unified profile; mapping is required. Option B is wrong because deduplication rules handle merging duplicate records, not the inclusion of specific fields like consent preferences. Option D is wrong because creating a segment based on consent is an output action that uses the unified data, but it does not affect the unification process itself.

Practice this question →

MCQmedium

A retail company uses Dynamics 365 Customer Insights to unify customer data from their online store, loyalty program, and in-store POS systems. After unification, they notice that some customers have duplicate profiles. What is the most likely cause and recommended action?

A.Re-run the data unification process without any changes

B.Review and adjust the match rules used during the data unification process

C.Manually delete duplicate customer records from the source systems

D.Contact Microsoft support to increase the deduplication limit

AnswerB

Adjusting match rules can reduce false positives and improve deduplication accuracy.

Why this answer

Duplicate profiles after unification typically occur when the match rules (deduplication rules) are not configured precisely enough to identify that two records represent the same customer. In Dynamics 365 Customer Insights, the unification process uses these rules to merge profiles based on attributes like email or phone; if the rules are too loose or missing key identifiers, duplicates persist. Adjusting the match rules—such as setting exact match on email or using fuzzy matching with appropriate thresholds—resolves the issue without altering source data.

Exam trap

The trap here is that candidates assume duplicates are a data quality issue requiring manual cleanup or a support escalation, rather than recognizing that the unification engine's match rules are the primary control for deduplication and must be tuned appropriately.

How to eliminate wrong answers

Option A is wrong because re-running the unification process without any changes will produce the same duplicate results, as the underlying match rules remain unchanged. Option C is wrong because manually deleting duplicates from source systems is inefficient, error-prone, and violates data integrity; Customer Insights is designed to handle deduplication during unification without modifying source data. Option D is wrong because there is no configurable 'deduplication limit' in Customer Insights that requires contacting Microsoft support; the deduplication behavior is controlled entirely by match rules and system capabilities.

Practice this question →

Multi-Selectmedium

A retail company uses Dynamics 365 Customer Insights to unify customer data from multiple sources. They want to define a customer data platform (CDP) strategy. Which TWO actions are key capabilities of Customer Insights?

Select 2 answers

A.Unify customer data from various sources into a single customer profile

B.Integrate data from Salesforce CRM out-of-the-box

C.Execute automated email campaigns

D.Use AI to predict customer churn and next best action

E.Personalize website content in real time

AnswersA, D

Correct: Data unification is a core capability.

Why this answer

Customer Insights provides data unification (option A) and AI-driven predictive models (option D). Real-time website personalization is a capability of Dynamics 365 Marketing, not Customer Insights. Salesforce data integration is not a native feature; it requires custom connectors.

Automated email campaign execution is part of Dynamics 365 Marketing.

Practice this question →

MCQeasy

A company wants to ensure customer data in Dynamics 365 Customer Insights complies with GDPR. Which feature helps manage consent?

A.Prediction models

B.Measures

C.Data unification

D.Consent management

AnswerD

Consent management allows tracking and honoring customer permissions.

Why this answer

Consent management in Dynamics 365 Customer Insights is the dedicated feature for capturing, storing, and honoring customer consent preferences, which is essential for GDPR compliance. It allows organizations to define consent purposes (e.g., marketing email, data sharing) and automatically enforce those preferences in downstream activities like segmentation and journeys. Without this feature, the system would have no native mechanism to track or respect individual consent choices.

Exam trap

The trap here is that candidates often confuse data unification (which merges records) with consent management, assuming that cleaning up duplicate data is sufficient for GDPR compliance, when in fact GDPR requires explicit, auditable consent tracking separate from data quality processes.

How to eliminate wrong answers

Option A is wrong because prediction models are used for AI-driven forecasting (e.g., churn, next best action) and have no role in managing consent or GDPR compliance. Option B is wrong because measures are aggregated calculations (e.g., KPIs, metrics) built from unified data, not a tool for consent tracking or privacy management. Option C is wrong because data unification is the process of matching and merging duplicate customer records from multiple sources into a single profile, which does not handle consent preferences or legal compliance.

Practice this question →

Multi-Selecthard

Which THREE of the following are capabilities provided by Dynamics 365 Customer Insights?

Select 3 answers

A.Data ingestion from multiple sources

B.Customer profile unification

C.Predictive analytics

D.Inventory management

E.Invoicing

AnswersA, B, C

Data ingestion is a core capability.

Why this answer

Dynamics 365 Customer Insights provides a unified data ingestion pipeline that can connect to multiple sources such as Azure Data Lake, Dataverse, Power Query connectors, and custom APIs. This allows organizations to bring in customer data from CRM, ERP, transactional systems, and external sources into a single customer data platform (CDP) for analysis and activation.

Exam trap

The trap here is that candidates may confuse the broad capabilities of the Dynamics 365 ecosystem (e.g., inventory or invoicing features) with the specific customer data platform (CDP) functions of Customer Insights, which is strictly about data ingestion, unification, and predictive analytics.

Practice this question →

MCQhard

You are a Dynamics 365 consultant for a multinational retail chain with operations in the US, Europe, and Asia. The company uses Dynamics 365 Customer Insights to create a single view of the customer across all regions. Each region has its own instance of Dynamics 365 Sales and separate data sources (POS, e-commerce, loyalty). The marketing team wants to create a global segment of customers who have purchased in at least two different regions in the past year. Currently, Customer Insights is set up with separate data unification processes for each region, and the unified profiles are not linked across regions. You need to design a solution to achieve the global segment. What should you do?

A.Re-create all data sources in a single Customer Insights environment and run unification globally

B.Export all unified profiles from each region to a common Excel file and manually identify duplicates, then import the combined list as a new segment

C.Use Power BI to combine the regional unified profiles and create the segment directly in Power BI

D.Set up a new Customer Insights environment that ingests data from each regional environment via Power Query and configure a cross-region matching rule using a common identifier such as email

AnswerD

This approach uses a global environment to unify data from regions, enabling cross-region matching.

Why this answer

It leverages a dedicated Customer Insights environment to ingest data from each regional environment via Power Query, enabling a cross-region matching rule using a common identifier like email. This approach creates a unified global customer view without duplicating or manually reconciling data, directly supporting the creation of a segment of customers who have purchased in at least two regions.

Exam trap

The trap here is that candidates may think a single environment with all raw data (Option A) is the simplest solution, but they overlook that Customer Insights supports cross-environment data ingestion and matching, which is more efficient and preserves existing regional data governance.

How to eliminate wrong answers

Option A is wrong because re-creating all data sources in a single Customer Insights environment would require migrating or re-ingesting all raw data from each region, which is inefficient and ignores the existing unified profiles; it also does not leverage the cross-region matching capability. Option B is wrong because manually exporting to Excel and identifying duplicates is error-prone, non-scalable, and violates data governance best practices; Customer Insights is designed to automate identity resolution, not rely on manual processes. Option C is wrong because Power BI is a visualization and analytics tool, not a data integration or identity resolution platform; it cannot create or manage Customer Insights segments or perform cross-region matching.

Practice this question →

MCQeasy

Refer to the exhibit. In Dynamics 365 Customer Insights - Data, the merge configuration uses 'LastUpdated' conflict resolution. What does this setting imply for the unified customer profile when there is conflicting data between the Customer and Purchase entities?

A.The value from the entity with the highest priority will be used.

B.The value from the entity that was last updated will be used.

C.The value from the Customer entity will always be used.

D.The value from the most recent data source will be used.

AnswerB

'LastUpdated' selects the value from the most recently updated record.

Why this answer

When 'LastUpdated' conflict resolution is selected in Dynamics 365 Customer Insights - Data merge configuration, the unified customer profile uses the value from the entity (Customer or Purchase) that was most recently updated. This ensures that the freshest data takes precedence, regardless of entity priority or data source order.

Exam trap

The trap here is that candidates confuse 'LastUpdated' conflict resolution with 'most recent data source' (Option D), but the resolution is per-entity record timestamp, not per-source ingestion order.

How to eliminate wrong answers

Option A is wrong because 'LastUpdated' conflict resolution does not consider entity priority; it uses the timestamp of the last update, not a predefined hierarchy. Option C is wrong because the Customer entity does not always win; the setting explicitly overrides any fixed entity preference in favor of the most recent update. Option D is wrong because the resolution is based on the last updated timestamp of the entity record, not on which data source was most recently added or ingested.

Practice this question →

MCQeasy

A retail company wants to unify customer data from their e-commerce platform, loyalty program, and in-store POS system to create a single customer profile. Which Dynamics 365 Customer Insights capability should they use?

A.Data unification

B.Power BI integration

C.Marketing segmentation

D.Customer Voice

AnswerA

Correct: Data unification is the feature that matches and merges customer records from multiple sources.

Why this answer

Data unification is the correct capability because it is specifically designed to reconcile and merge customer records from disparate data sources—such as e-commerce platforms, loyalty programs, and POS systems—into a single, unified customer profile. This process uses matching rules, deduplication, and conflict resolution to create a 360-degree view of each customer, which is the core requirement described in the question.

Exam trap

The trap here is that candidates often confuse data unification with segmentation or reporting, assuming that any analytics or grouping feature can merge data, when in fact unification is a distinct, prerequisite process for creating a single customer view.

How to eliminate wrong answers

Option B is wrong because Power BI integration is a reporting and visualization tool that connects to Customer Insights for dashboards, but it does not perform the actual merging or deduplication of customer data from multiple sources. Option C is wrong because marketing segmentation uses unified profiles to create targeted groups for campaigns, but it relies on data already unified and does not itself reconcile records from different systems. Option D is wrong because Customer Voice is a survey and feedback management tool that collects customer opinions, not a mechanism for merging or unifying customer data from operational systems.

Practice this question →

MCQmedium

You are a Dynamics 365 consultant for a multinational retail company. The company has recently deployed Dynamics 365 Customer Insights to unify customer data from point-of-sale (POS) systems, an e-commerce platform, and a loyalty program. The data ingestion pipeline is working, and unified customer profiles are being created. However, the marketing team reports that segments built using the 'LastPurchaseDate' attribute are not returning accurate results. Specifically, a segment defined as 'Customers who purchased in the last 30 days' includes customers whose last purchase was over 60 days ago, and excludes some customers who purchased yesterday. The data source for purchase transactions is updated daily via an incremental refresh. The 'LastPurchaseDate' field is computed from the transaction entity. Upon investigation, you notice that the unified profile entity shows a 'LastPurchaseDate' that is older than the most recent transaction for some customers. What is the most likely cause of this issue, and what should you do to fix it?

A.The matching rules are incorrectly configured, causing the system to use an older transaction; update the matching rules.

B.The transaction data is in a different data source that is not linked to the profile; create a new data source and link it.

C.The unification process has not been re-run after the latest data refresh; schedule the unification to run after each data refresh.

D.The incremental refresh is not configured correctly; reconfigure the data source to use full refresh instead.

AnswerC

Correct. Unification must be re-run to incorporate new data into profiles.

Why this answer

In Dynamics 365 Customer Insights, the unification process is a separate step that merges and deduplicates data from multiple sources into unified customer profiles. Even if the data source is refreshed incrementally, the unified profile entity will not reflect the latest transaction data until the unification process is re-run. Since the segment uses the 'LastPurchaseDate' from the unified profile, it will show stale data until unification is executed after each refresh.

Exam trap

The trap here is that candidates often assume that refreshing the data source automatically updates the unified profiles and computed attributes, but in Customer Insights, unification is a separate orchestration step that must be explicitly scheduled or triggered after data refresh.

How to eliminate wrong answers

Option A is wrong because matching rules control how customer records from different sources are linked, not how the 'LastPurchaseDate' is computed or updated; incorrect matching would cause duplicate or missing profiles, not stale date values. Option B is wrong because the transaction data is already ingested and the 'LastPurchaseDate' is computed from the transaction entity within the same data source; linking a new data source would not fix the staleness issue. Option D is wrong because incremental refresh is correctly updating the transaction data; switching to full refresh would be inefficient and unnecessary, as the core problem is that unification has not been re-run to propagate the refreshed data into the unified profile.

Practice this question →

MCQmedium

A business analyst wants to create a segment of customers who have purchased both a laptop and a mouse in the last 30 days. The data is stored in two separate tables: 'PurchaseHeader' and 'PurchaseLines'. What is the best approach?

A.Create a segment and use the 'AND' condition for both products

B.First unify the two tables into one view, then segment

C.Use the segment builder to add two conditions: one for product = Laptop and one for product = Mouse, both with date filter

D.Export the data to Power BI and create the segment there

AnswerC

Multiple conditions with AND logic can capture customers with both products.

Why this answer

Dynamics 365 Customer Insights - Data segment builder allows you to add multiple conditions on the same entity (PurchaseLines) using AND logic, filtering for both 'Laptop' and 'Mouse' within the last 30 days. This approach directly queries the transactional data without requiring table unification or external tools, leveraging the platform's native segment creation capabilities.

Exam trap

The trap here is that candidates may think they need to unify tables first (Option B) or use a single AND condition (Option A), when in fact the segment builder supports multiple conditions on the same entity with AND logic across different rows, which is the correct method for matching customers who bought both products.

How to eliminate wrong answers

Option A is wrong because a single segment condition cannot use AND to match two different product values in the same field; it would require OR logic or separate conditions. Option B is wrong because unifying tables into a view is unnecessary overhead; Customer Insights can join PurchaseHeader and PurchaseLines via relationships in the segment builder without creating a separate view. Option D is wrong because exporting data to Power BI for segmentation bypasses the native segment builder and introduces latency, complexity, and loss of real-time updates within Customer Insights.

Practice this question →

Multi-Selectmedium

Which THREE are capabilities of Dynamics 365 Customer Insights?

Select 3 answers

A.Customer service case management

B.Email campaign creation and sending

C.Unified customer profile from multiple data sources

D.Segmentation based on customer attributes and behavior

E.AI-driven predictions like churn and product recommendation

AnswersC, D, E

This is the core feature of Customer Insights.

Why this answer

Dynamics 365 Customer Insights is a customer data platform (CDP) that ingests data from multiple sources—such as transactional systems, web interactions, and CRM—to create a unified customer profile. This profile consolidates disparate data into a single, 360-degree view of each customer, enabling personalized engagement and analytics.

Exam trap

The trap here is that candidates often confuse the capabilities of Dynamics 365 Customer Insights with those of other Dynamics 365 apps, such as Customer Service or Marketing, leading them to select options that are valid for those apps but not for Customer Insights.

Practice this question →

MCQmedium

A company uses Dynamics 365 Customer Insights - Journeys to run a multi-channel campaign. They want to send an SMS message to contacts who have an opt-in for SMS. Which entity should they use to store the consent status for each channel?

A.Contact

B.Lead

C.Account

D.Segment

AnswerA

Contact entity includes consent fields for marketing and channels.

Why this answer

In Dynamics 365 Customer Insights - Journeys, consent for communication channels like SMS is stored directly on the Contact entity. Each contact record contains dedicated fields (e.g., 'Do not bulk email', 'Do not bulk SMS') that capture opt-in or opt-out status per channel. When a journey sends an SMS message, it checks the contact's SMS consent field to ensure compliance before delivering the message.

Exam trap

The trap here is that candidates often confuse the Segment entity as the source of consent data, but segments only filter contacts based on existing attributes—they do not store or manage consent status themselves.

How to eliminate wrong answers

Option B is wrong because the Lead entity is used for prospective customers who have not yet been qualified, and it does not store per-channel consent fields for marketing communications like SMS. Option C is wrong because the Account entity represents organizations or companies, not individual contacts, and consent is a personal attribute that must be stored at the contact level. Option D is wrong because a Segment is a dynamic or static group of contacts defined by rules or membership, not a data entity that stores consent status; segments reference contacts but do not hold consent fields themselves.

Practice this question →

MCQmedium

You are a Customer Insights administrator for a healthcare organization. The organization has strict data privacy requirements. They need to ensure that customer profiles containing sensitive health information are not exported to external systems without proper consent. The current configuration includes a segment called 'HealthDataSegment' that contains patients with specific conditions. The marketing team wants to export this segment to a third-party email marketing tool for a campaign. However, the compliance officer has mandated that no health data should leave the Customer Insights environment without explicit consent. What should you do to meet the compliance requirement while still allowing the marketing campaign?

A.Disable export for the segment and use only in-app campaigns

B.Use data masking in the export destination

C.Create a data policy in Customer Insights that restricts export of health attributes, and then export the segment excluding those attributes

D.Remove all health-related attributes from the customer profiles

AnswerC

Data policies control attribute-level export.

Why this answer

Dynamics 365 Customer Insights allows administrators to create data policies that restrict the export of specific attributes (e.g., health data) from segments. By defining a policy that excludes health-related attributes from the 'HealthDataSegment' export, you comply with the consent requirement while still allowing the marketing team to export the segment (minus sensitive data) to the third-party email marketing tool.

Exam trap

The trap here is that candidates often confuse data masking (which hides data at the destination but still transmits it) with data policies (which prevent the data from leaving the source environment entirely), leading them to choose Option B instead of the correct policy-based approach.

How to eliminate wrong answers

Option A is wrong because disabling export entirely prevents any campaign use of the segment, which is overly restrictive and not required by the compliance mandate—only health data needs to be restricted, not all data. Option B is wrong because data masking in the export destination does not prevent the sensitive data from leaving the Customer Insights environment; it only obscures it at the destination, which still violates the requirement that no health data should leave without explicit consent. Option D is wrong because removing all health-related attributes from customer profiles is a destructive, irreversible action that affects all downstream processes and analytics, whereas a data policy selectively restricts export without altering the source data.

Practice this question →

MCQmedium

Your Customer Insights instance has ingested data from a CRM and an e-commerce platform. After unification, some customers appear as duplicates. What is the most likely cause?

A.Matching rules are too strict

B.Matching rules are too loose

C.Data sources have different field names

D.Confidence level is set too low

AnswerB

Loose rules can merge unrelated records.

Why this answer

When matching rules are too loose, the system merges records that are not truly the same customer, creating duplicates after unification. In Customer Insights, matching rules define the conditions (e.g., exact match on email, fuzzy match on name) that determine whether records from different sources represent the same entity. Loose rules allow records with minor differences to be considered matches, leading to false positives and duplicate customer profiles.

Exam trap

The trap here is that candidates often confuse 'matching rules' with 'data mapping' or 'confidence levels,' assuming duplicates come from unmapped fields or low confidence, rather than understanding that overly permissive matching criteria directly cause false positive merges.

How to eliminate wrong answers

Option A is wrong because strict matching rules would reduce false positives and prevent duplicates, not cause them. Option C is wrong because different field names are handled by mapping fields during data ingestion, not by matching rules, and do not directly cause duplicates after unification. Option D is wrong because confidence level is a threshold for match suggestions in the merge process, not the cause of duplicates; a low confidence level would actually reduce automatic merges, not increase duplicates.

Practice this question →

MCQmedium

A company uses Dynamics 365 Customer Insights - Data to generate AI-driven predictions about customer churn. They want to use these predictions to trigger a journey in Customer Insights - Journeys that sends a retention offer. How should they integrate the two applications to achieve this?

A.Use Power Automate to trigger a journey

B.Use the Outbound marketing connector

C.Use the Data Insights connector

D.Use the Real-time marketing connector

AnswerC

The Data Insights connector enables Customer Insights - Journeys to use predictions from Customer Insights - Data.

Why this answer

The Data Insights connector in Dynamics 365 Customer Insights - Journeys is specifically designed to consume AI-driven predictions (such as churn propensity scores) from Customer Insights - Data and use them as triggers or segments for real-time journeys. This connector enables the direct flow of enriched customer data and predictive insights into journey orchestration without requiring intermediate tools.

Exam trap

The trap here is that candidates often confuse the Data Insights connector with the Real-time marketing connector, assuming the latter is the correct bridge for predictions, when in fact the Data Insights connector is the specific integration point for AI-driven insights from Customer Insights - Data.

How to eliminate wrong answers

Option A is wrong because Power Automate can trigger actions but is not the native integration for directly triggering a Customer Insights - Journeys journey from a Customer Insights - Data prediction; it would require custom logic and lacks the built-in prediction-to-journey mapping. Option B is wrong because the Outbound marketing connector is deprecated and designed for legacy outbound marketing scenarios, not for real-time journey triggers based on AI predictions from Customer Insights - Data. Option D is wrong because the Real-time marketing connector is a general term for connecting to real-time marketing features, but the specific connector that bridges Customer Insights - Data predictions to journeys is the Data Insights connector, not a standalone 'Real-time marketing connector'.

Practice this question →

MCQhard

A company has customer data in Salesforce, a SQL database, and Excel files. They need to bring all this data into Dynamics 365 Customer Insights. What should they use?

A.Dual-write

B.Common Data Model

C.Dataflows in Power Platform

D.Customer Insights data ingestion connectors

AnswerD

Customer Insights provides connectors for Salesforce, SQL, and files.

Why this answer

Customer Insights data ingestion connectors are purpose-built to import data from external sources like Salesforce, SQL databases, and Excel files directly into Dynamics 365 Customer Insights. These connectors support a wide range of data sources and handle the extraction, transformation, and loading (ETL) process, enabling unified customer profiles without requiring custom development.

Exam trap

The trap here is that candidates often confuse Dataflows in Power Platform with Customer Insights data ingestion connectors, but Dataflows are a general-purpose tool while Customer Insights provides specialized connectors optimized for customer data unification and profile creation.

How to eliminate wrong answers

Option A is wrong because Dual-write is a near-real-time integration pattern between Dynamics 365 Finance and Operations and Dataverse, not designed for importing data from Salesforce, SQL databases, or Excel files into Customer Insights. Option B is wrong because Common Data Model is a standardized schema for data entities, not a tool or service for ingesting data from external sources; it defines how data should be structured but does not perform ingestion. Option C is wrong because Dataflows in Power Platform are used for data preparation and transformation within Power BI or Power Apps, but they are not the primary or recommended method for bringing data into Dynamics 365 Customer Insights; Customer Insights has its own dedicated set of ingestion connectors that are more tightly integrated.

Practice this question →

Multi-Selecthard

A company is implementing Dynamics 365 Customer Insights - Data to create a 360-degree customer view. They have data in an on-premises SQL Server database, Dynamics 365 Sales, and third-party survey data in CSV files. Which THREE data ingestion methods are available in Customer Insights - Data to bring this data into the system? (Choose three.)

Select 3 answers

A.Microsoft Power Query

B.Common Data Model folder

C.Export destinations

D.Azure Data Lake Storage Gen1

E.API connector

AnswersA, B, E

Power Query is the primary data ingestion method for various sources.

Why this answer

Microsoft Power Query is correct because it is the primary data ingestion method in Customer Insights - Data for connecting to on-premises SQL Server databases, Dynamics 365 Sales, and CSV files. It provides a graphical interface to transform and load data from these sources into the unified customer profile, supporting both direct query and import modes.

Exam trap

The trap here is that candidates confuse Export destinations (which are outbound) with ingestion methods, and mistakenly think Azure Data Lake Storage Gen1 is supported when only Gen2 is available in Customer Insights - Data.

Practice this question →

MCQhard

You are a Dynamics 365 consultant for a manufacturing company that uses Customer Insights to unify data from their CRM (Dynamics 365 Sales) and their ERP (Dynamics 365 Finance). They want to use Customer Insights to calculate a measure for 'Average Order Value' per customer. After creating the measure, they notice that the values are incorrect because the currency from the ERP is in euros, while the CRM uses US dollars. The ERP data includes a currency conversion rate field. What should you do to ensure the measure uses a consistent currency?

A.Change the ERP data source to output values in USD.

B.Create a measure for conversion rate and use it in the average order value measure.

C.Use the 'CurrencyConvert' function in the measure to convert values.

D.Create a calculated column in the unified data that multiplies the order value by the conversion rate.

AnswerD

Calculated columns can transform data.

Why this answer

In Dynamics 365 Customer Insights, calculated columns are the appropriate way to transform data at the entity level before using it in measures. By creating a calculated column that multiplies the order value by the conversion rate, you ensure all values are in a consistent currency (USD) before the 'Average Order Value' measure aggregates them. This approach directly addresses the mismatch between EUR in the ERP and USD in the CRM without altering source systems or using unsupported functions.

Exam trap

The trap here is that candidates may confuse the 'CurrencyConvert' function available in Power Query (M) with a similar function in Customer Insights measures, or assume that a separate measure can be nested inside another measure, neither of which is supported in the measure definition interface.

How to eliminate wrong answers

Option A is wrong because changing the ERP data source to output values in USD is not feasible or recommended; it would require modifying the source system's data export logic, which is outside the scope of Customer Insights and may break other downstream processes. Option B is wrong because creating a separate measure for conversion rate does not integrate the conversion into the average order value calculation; measures in Customer Insights cannot reference other measures directly for row-level transformations. Option C is wrong because there is no 'CurrencyConvert' function available in Customer Insights measures; this function exists in Power Query (M language) but not in the measure definition interface, which relies on predefined aggregation functions.

Practice this question →

100

MCQeasy

You are a Dynamics 365 administrator for a mid-sized e-commerce company. The marketing team wants to use Dynamics 365 Customer Insights to create a unified customer profile that includes browsing history, purchase history, and customer support interactions. They also want to use this unified data to send personalized offers via email. You have access to Dynamics 365 Customer Insights and Dynamics 365 Marketing. What should you do first?

A.Set up data ingestion from browsing history, purchase history, and support interactions into Dynamics 365 Customer Insights, then unify the data into a single customer profile.

B.Configure Dynamics 365 Customer Insights to send personalized emails directly to customers using the unified customer profile.

C.Import all data directly into Dynamics 365 Marketing and use its native customer profile feature to unify the data.

D.Create a segment in Dynamics 365 Customer Insights based on purchase history, then export the segment to Dynamics 365 Marketing to send offers.

AnswerA

Correct: Data unification is the foundational step before any other actions.

Why this answer

The first step is to ingest the disparate data sources (browsing history, purchase history, and support interactions) into Dynamics 365 Customer Insights and then unify them into a single customer profile. This unified profile is the foundation for all downstream activities, such as segmentation and personalized email campaigns. Without this data unification, you cannot accurately target or personalize offers in Dynamics 365 Marketing.

Exam trap

The trap here is that candidates often assume they can jump straight to segmentation or email sending, forgetting that data must first be ingested and unified in Customer Insights before any meaningful personalization can occur.

How to eliminate wrong answers

Option B is wrong because Dynamics 365 Customer Insights does not have native email sending capabilities; it is a customer data platform (CDP) for data ingestion, unification, and segmentation, not an email marketing tool. Option C is wrong because Dynamics 365 Marketing does not have a native customer profile feature that can unify data from multiple sources; it relies on Customer Insights for unified profiles and segments. Option D is wrong because creating a segment based solely on purchase history before unifying all data sources would result in an incomplete and potentially inaccurate customer profile, missing key context from browsing history and support interactions.

Practice this question →

101

MCQmedium

You are a Dynamics 365 consultant for a large retail chain. The company uses Dynamics 365 Customer Insights to manage customer data. The marketing team wants to create a segment of 'High Value Customers' defined as customers with a lifetime value (LTV) greater than $5,000. They also want to send a special promotional offer to this segment via email. The data is already unified in Customer Insights. However, the LTV attribute is not currently calculated. You need to enable the marketing team to achieve their goal with minimal effort. What should you do?

A.Use Power Automate to create a flow that calculates LTV for each customer and updates the attribute in Customer Insights.

B.Import the LTV data into Dynamics 365 Marketing as a custom attribute and then create the segment there.

C.Create a new measure in Dynamics 365 Customer Insights called 'Customer Lifetime Value' using the built-in measure builder with the relevant transaction data.

D.Re-unify the customer data, ensuring that the LTV attribute is included from the source systems.

AnswerC

Correct: The measure builder allows easy calculation of LTV.

Why this answer

Dynamics 365 Customer Insights includes a built-in measure builder that allows you to define calculated attributes like 'Customer Lifetime Value' directly within the unified data model. This approach requires minimal effort as it leverages existing transaction data without needing external tools or data re-import. Once the measure is created, the marketing team can immediately use it to build the 'High Value Customers' segment in Customer Insights and then export that segment to Dynamics 365 Marketing for the email campaign.

Exam trap

The trap here is that candidates often assume external tools like Power Automate or manual data imports are necessary for calculations, overlooking the native measure builder in Customer Insights that is designed specifically for this purpose.

How to eliminate wrong answers

Option A is wrong because using Power Automate to calculate LTV and update the attribute is unnecessarily complex and introduces external dependencies; Customer Insights already provides a native measure builder for this purpose. Option B is wrong because importing LTV data into Dynamics 365 Marketing as a custom attribute bypasses the unified data in Customer Insights and requires manual data movement, which is not minimal effort. Option D is wrong because re-unifying the customer data to include LTV from source systems assumes the LTV is pre-calculated in those systems, which it is not; the correct approach is to calculate it within Customer Insights using the measure builder.

Practice this question →

102

MCQhard

Refer to the exhibit. You are configuring data unification in Dynamics 365 Customer Insights - Data. After running the unification process, you notice that the merged profile contains the 'Amount' field from the Orders entity but the 'Duration' field from the WebVisits entity is missing. The conflict resolution is set to 'SourceOrder' with ds_orders first. Which action should you take to include the 'Duration' field in the unified profile?

A.Change the matching rule to include the 'Duration' field as a condition.

B.Modify the merge configuration to include all fields from both entities in the output profile.

C.Add the 'Duration' field to the Orders entity definition.

D.Reverse the source order to place ds_web first.

AnswerB

The merge step must specify which fields to include in the unified profile.

Why this answer

The 'Duration' field is missing because the merge configuration is set to 'SourceOrder' with ds_orders first, meaning only fields present in the first source (ds_orders) are included in the unified profile by default. To include fields from ds_web (like 'Duration'), you must modify the merge configuration to explicitly include all fields from both entities in the output profile, overriding the default source-order-based field selection.

Exam trap

The trap here is that candidates confuse conflict resolution (which handles overlapping field values) with field inclusion (which determines which fields appear in the output), leading them to incorrectly choose reversing the source order or modifying matching rules instead of adjusting the merge configuration to include all fields.

How to eliminate wrong answers

Option A is wrong because the matching rule determines how records are matched across entities, not which fields are included in the merged output; changing it would not add the 'Duration' field. Option C is wrong because adding 'Duration' to the Orders entity definition would not automatically include it in the profile unless the merge configuration is updated to pull fields from both entities. Option D is wrong because reversing the source order would only swap which entity's fields take precedence in case of conflicts, but 'Duration' is not present in ds_orders at all, so it would still be missing.

Practice this question →

103

MCQeasy

A business analyst wants to create a segment of customers who have made a purchase in the last 30 days. Which Customer Insights component should they use?

A.Predictive models

B.Measures

C.Segmentation

D.Enrichment

AnswerC

Segments allow filtering customers by attributes or behaviors.

Why this answer

Segmentation is the Customer Insights component specifically designed to create subsets of customers based on defined criteria, such as purchase recency. By setting a condition like 'purchase date within the last 30 days,' the business analyst can dynamically generate a segment of qualifying customers for targeted actions.

Exam trap

The trap here is that candidates often confuse Measures (aggregated KPIs) with Segmentation (filtering records), because both involve data analysis, but only Segmentation creates a subset of customer records.

How to eliminate wrong answers

Option A is wrong because Predictive models are used to forecast future behaviors (e.g., churn probability) using machine learning, not to filter historical data like purchase recency. Option B is wrong because Measures aggregate numeric data (e.g., total sales, average order value) into KPIs, but they do not create customer subsets or segments. Option D is wrong because Enrichment augments existing customer profiles with external data sources (e.g., demographic or firmographic data), but it does not filter or group customers based on transactional criteria.

Practice this question →

104

MCQmedium

A company has multiple business units that each use a separate CRM system. They want to use Customer Insights to create a single view of customers across these systems. Which feature should they use?

A.Measures

B.Data sources

C.Data unification

D.Segments

AnswerC

Unification merges records from different sources.

Why this answer

Data unification is the correct feature because it is specifically designed to merge customer records from multiple data sources (such as separate CRM systems) into a single, unified customer profile. This process uses matching rules and deduplication to resolve identities across disparate systems, enabling a 360-degree view of each customer.

Exam trap

The trap here is that candidates confuse 'Data sources' (which only ingest data) with 'Data unification' (which merges and deduplicates), leading them to select the option that sounds like it handles multiple systems but actually only connects to them.

How to eliminate wrong answers

Option A is wrong because Measures are used to define KPIs and calculated metrics (e.g., average order value) on unified data, not to merge data from multiple sources. Option B is wrong because Data sources are the connectors that bring raw data into Customer Insights, but they do not perform the merging or deduplication required to create a single customer view. Option D is wrong because Segments are dynamic or static groupings of customer profiles based on attributes or behaviors, created after unification has already occurred.

Practice this question →

105

Multi-Selecthard

Which TWO are best practices when configuring match rules in Dynamics 55 Customer Insights?

Select 2 answers

A.Use only exact matching to ensure no false positives

B.Combine exact and fuzzy matching for better coverage

C.Test match rules with a sample dataset before applying to all data

D.Create as many match rules as possible to capture all duplicates

E.Disable deduplication for high-volume data sources

AnswersB, C

Fuzzy matching catches variations like typos.

Why this answer

Combining exact and fuzzy matching in Dynamics 365 Customer Insights allows the system to identify both identical records (exact match) and near-duplicates with minor variations like typos or abbreviations (fuzzy match), improving deduplication coverage without sacrificing precision. This hybrid approach is a best practice to balance accuracy and recall when configuring match rules.

Exam trap

The trap here is that candidates often assume exact matching is always safer (Option A) or that more rules always catch more duplicates (Option D), but the exam tests the balanced approach of combining match types and testing with sample data.

Practice this question →

106

MCQmedium

A marketing team wants to use AI to predict which customers are most likely to purchase a new product. Which feature of Dynamics 365 Customer Insights should they use?

A.Predictive models

B.Enrichment

C.Measures

D.Segmentation

AnswerA

Predictive models use machine learning to forecast customer behavior.

Why this answer

Predictive models in Dynamics 365 Customer Insights use machine learning to analyze historical customer data and identify patterns that indicate a high likelihood of purchasing a new product. This feature allows the marketing team to create a binary prediction (e.g., will buy/will not buy) based on attributes such as past purchases, engagement, and demographics, directly addressing the need to predict which customers are most likely to purchase.

Exam trap

The trap here is that candidates often confuse segmentation (a static grouping) with predictive modeling (a dynamic, ML-driven forecast), especially when the question asks about 'predicting' behavior, leading them to choose segmentation because it also involves grouping customers.

How to eliminate wrong answers

Option B (Enrichment) is wrong because enrichment is used to enhance existing customer profiles with external data sources (e.g., demographic or firmographic data) and does not perform predictive analysis or model future behavior. Option C (Measures) is wrong because measures are used to define and calculate KPIs or aggregated metrics (e.g., total spend, average order value) from customer data, not to predict future outcomes. Option D (Segmentation) is wrong because segmentation groups customers based on static criteria or rules (e.g., age, region) and does not use machine learning to forecast purchase likelihood; it is a reactive grouping, not a predictive model.

Practice this question →

107

MCQmedium

A company wants to use Dynamics 365 Customer Insights to create a unified customer profile. The data sources include a CRM system, a loyalty program database, and web analytics. What is the first step they should take?

A.Define unification rules

B.Set up connections to Power BI

C.Configure data sources and ingest data

D.Create a customer segment

AnswerC

Data ingestion is the prerequisite for all subsequent steps.

Why this answer

In Dynamics 365 Customer Insights, the first step to creating a unified customer profile is to configure data sources and ingest data. Without data ingestion, there is no customer data to unify, segment, or analyze. This foundational step connects the CRM system, loyalty program database, and web analytics to the platform, enabling subsequent unification and segmentation.

Exam trap

The trap here is that candidates may think defining unification rules is the first step because it sounds like the core of profile creation, but Microsoft explicitly requires data to be ingested first, as unification rules operate on existing data entities.

How to eliminate wrong answers

Option A is wrong because defining unification rules (e.g., matching and merge rules) occurs after data has been ingested, not before; you cannot unify data that hasn't been imported. Option B is wrong because setting up connections to Power BI is an optional visualization step that happens after data is unified and segments are created, not as the first step. Option D is wrong because creating a customer segment requires unified customer profiles to exist, which depends on prior data ingestion and unification.

Practice this question →

108

Multi-Selectmedium

Which TWO actions are supported by Dynamics 365 Customer Insights?

Select 2 answers

A.Creating sales orders

B.Unifying customer data from multiple sources

C.Enriching customer profiles with external data

D.Managing inventory levels

E.Processing payroll

AnswersB, C

Core functionality.

Why this answer

Dynamics 365 Customer Insights is a customer data platform (CDP) designed to unify customer data from disparate sources such as CRM, ERP, and marketing systems into a single, comprehensive view. It supports enriching these unified customer profiles with external data (e.g., demographic or behavioral data from third-party providers) to enhance segmentation and personalization. Creating sales orders, managing inventory, and processing payroll are operational tasks handled by other Dynamics 365 applications like Sales, Supply Chain Management, and Finance, respectively.

Exam trap

The trap here is that candidates confuse Customer Insights as a general-purpose operational tool rather than a dedicated customer data platform (CDP) for analytics and unification, leading them to select transactional actions like sales orders or inventory management.

Practice this question →

109

Multi-Selecthard

Which THREE of the following are prerequisites for using Customer Insights predictive models?

Select 3 answers

A.Real-time data streaming

B.Data types that match the model requirements (e.g., numeric, categorical)

C.Power BI integration

D.Historical data with known outcomes

E.A minimum number of records (e.g., 1000)

AnswersB, D, E

Correct data types are required.

Why this answer

Customer Insights predictive models require that the data types in your dataset match the model's expected schema—for example, numeric fields for regression or categorical fields for classification. If the data types are mismatched (e.g., a string where a number is expected), the model will fail to train or produce inaccurate predictions. This prerequisite ensures the underlying machine learning algorithms can process the data correctly.

Exam trap

The trap here is that candidates confuse optional features (like real-time streaming or Power BI) with hard prerequisites, but Microsoft explicitly lists data type matching, historical outcomes, and minimum record count as non-negotiable requirements for model training.

Practice this question →

110

Multi-Selectmedium

Which THREE of the following are data sources that can be ingested into Dynamics 365 Customer Insights - Data?

Select 3 answers

A.Salesforce

B.LinkedIn

C.Azure SQL Database

D.SAP Concur

E.Dynamics 365 Sales

AnswersA, C, E

Salesforce connector is available.

Why this answer

Dynamics 365 Customer Insights - Data supports ingesting data from Salesforce via its built-in Power Query connectors. This allows organizations to unify customer data from CRM systems like Salesforce into a single customer data platform (CDP) for 360-degree views.

Exam trap

The trap here is that candidates may assume all popular business applications (like LinkedIn or SAP Concur) are automatically supported as data sources, but the exam tests only the specific connectors documented in the official Microsoft list for Customer Insights - Data.

Practice this question →

111

MCQmedium

Your Customer Insights data shows that some customer profiles have missing phone numbers. You have a third-party data provider that can supply phone numbers based on email addresses. Which capability should you use to add this data?

A.Data merge

B.Data import

C.Data matching

D.Data enrichment

AnswerD

Enrichment appends external data to existing profiles.

Why this answer

Data enrichment is the correct capability because it allows you to enhance existing customer profiles by appending missing attributes—such as phone numbers—from an external third-party data provider. In Dynamics 365 Customer Insights, enrichment uses a matching key (e.g., email address) to pull in additional data from a configured provider without overwriting or merging entire records.

Exam trap

The trap here is confusing data matching (which links records within or across datasets) with data enrichment (which adds external data to existing profiles), leading candidates to pick C instead of D.

How to eliminate wrong answers

Option A is wrong because data merge is used to combine duplicate customer profiles into a single unified profile, not to add missing attributes from an external source. Option B is wrong because data import brings in new data from files or connectors but does not automatically match and append missing fields from a third-party service. Option C is wrong because data matching identifies and links related records across datasets (e.g., for deduplication or unification), but it does not fetch or add external data like phone numbers.

Practice this question →

112

Multi-Selecteasy

Which TWO are valid data sources for Dynamics 365 Customer Insights?

Select 2 answers

A.Dataverse

B.Power BI dataset

C.Azure DevOps

D.Excel workbook

E.Common Data Model folder

AnswersA, E

Commonly used source.

Why this answer

Options A and E are correct: Dataverse and Common Data Model folder are valid data sources for Dynamics 365 Customer Insights. Option B is wrong because Power BI datasets are not directly supported as sources. Option C is wrong because Azure DevOps is not a data source.

Option D is wrong because Excel workbooks are not directly supported.

Practice this question →

113

MCQhard

A telecommunications company uses Dynamics 365 Customer Insights to analyze customer churn. They have created a churn prediction model and want to take real-time actions when a customer is predicted to churn, such as sending a retention offer. Which integration should they use?

A.Enrichment from Azure Data Lake

B.Power Automate to send email

C.Real-time marketing in Dynamics 365

D.Power BI embedded reports

AnswerC

Real-time marketing can trigger personalized offers based on predictions.

Why this answer

Real-time marketing in Dynamics 365 Customer Insights enables immediate, automated actions (such as sending retention offers) when a churn prediction model triggers. This integration uses customer segments and triggers from the prediction model to initiate outbound communications in real time, aligning with the requirement for real-time actions.

Exam trap

The trap here is that candidates often confuse Power Automate as the correct answer because it can send emails, but they miss that Real-time marketing in Dynamics 365 is the native, purpose-built integration for triggering actions directly from Customer Insights predictions without needing an external workflow tool.

How to eliminate wrong answers

Option A is wrong because Enrichment from Azure Data Lake is used to import and enhance customer data from external sources, not to trigger real-time actions based on predictions. Option B is wrong because Power Automate can send emails but is a general-purpose automation tool; it lacks the native integration with Customer Insights churn predictions and real-time marketing capabilities that Dynamics 365 provides. Option D is wrong because Power BI embedded reports are for visualizing data and analytics, not for executing real-time actions like sending retention offers.

Practice this question →

114

MCQeasy

Refer to the exhibit. A Customer Insights administrator creates a segment for high-value customers. Which customers will be included in this segment?

A.All customers

B.Customers with a CLV greater than 1000

C.Customers with a CLV of exactly 1000

D.Customers with a CLV less than 1000

AnswerB

The criteria is CLV > 1000.

Why this answer

The segment is defined as 'high-value customers,' and the rule shown in the exhibit filters for customers where Customer Lifetime Value (CLV) is greater than 1000. In Dynamics 365 Customer Insights, segments are built using conditions that evaluate numeric attributes, and the 'greater than' operator includes only records where the value exceeds the specified threshold.

Exam trap

The trap here is that candidates may confuse 'greater than' with 'greater than or equal to' or assume that 'high-value' includes the threshold value itself, leading them to select Option C.

How to eliminate wrong answers

Option A is wrong because the segment applies a specific condition on CLV, so it does not include all customers. Option C is wrong because the condition uses 'greater than' (>) not 'equals' (=), so customers with a CLV of exactly 1000 are excluded. Option D is wrong because the condition filters for CLV greater than 1000, not less than 1000.

Practice this question →

115

Multi-Selecthard

Which TWO data sources can be used to enrich customer profiles in Dynamics 365 Customer Insights? (Choose two.)

Select 2 answers

A.SharePoint document libraries

B.Third-party data providers

C.Power BI dashboards

D.Microsoft Graph

E.Finance and Operations general ledger

AnswersB, D

Third-party providers can supply demographic or behavioral data.

Why this answer

Dynamics 365 Customer Insights allows you to enrich customer profiles by integrating data from third-party data providers, such as Experian or Acxiom, to add attributes like demographic or firmographic information. This enrichment process uses the 'Enrichment' feature within the app, which connects to external data sources via connectors to enhance existing customer data.

Exam trap

The trap here is that candidates often confuse data sources for enrichment (which are external, third-party providers) with data sources for ingestion (like Finance and Operations or SharePoint), leading them to select options that are valid for importing data but not for the specific enrichment feature.

Practice this question →

116

MCQhard

A financial services company uses Dynamics 365 Customer Insights to generate a 360-degree view of customers. They want to use AI to predict which customers are likely to churn in the next 30 days. What should they configure?

A.Enable the churn prediction model in the AI insights module

B.Define a measure to calculate average transaction amount

C.Create a static segment based on past churn behavior

D.Add enrichment data from external demographics

AnswerA

The AI insights module includes prebuilt models for churn prediction.

Why this answer

The churn prediction model in the AI insights module is the correct configuration because Dynamics 365 Customer Insights provides prebuilt AI models, including a churn prediction model, that analyze customer data (e.g., interactions, transactions, and engagement) to predict which customers are likely to churn within a specified time frame, such as 30 days. This model uses machine learning to identify patterns and assign a churn score, enabling proactive retention efforts.

Exam trap

The trap here is that candidates often confuse static segmentation or manual measures with AI-powered predictive models, assuming that historical data alone can predict future behavior without machine learning.

How to eliminate wrong answers

Option B is wrong because defining a measure to calculate average transaction amount is a manual analytical step that does not leverage AI to predict churn; it provides a static metric rather than a predictive model. Option C is wrong because creating a static segment based on past churn behavior only captures historical data and cannot predict future churn, as it lacks the machine learning component that identifies emerging patterns. Option D is wrong because adding enrichment data from external demographics enhances customer profiles but does not configure a predictive AI model for churn; enrichment is a data preparation step, not a prediction mechanism.

Practice this question →

117

MCQmedium

A company wants to enrich customer profiles with external demographic data from a third-party provider. Which feature in Customer Insights allows them to import and map this data?

A.Data profiling

B.Connectors

C.Data sources

D.Enrichment

AnswerC

Correct: Data sources allow importing data from third-party providers via connectors.

Why this answer

Data sources allow you to connect to and import data from external systems, including third-party demographic providers. Option B (Connectors) is a component within Data sources, not a standalone feature for importing. Option D (Enrichment) is used to enhance existing customer profiles with additional data, but the data must first be imported via Data sources.

Option A (Data profiling) is used to analyze data quality and structure, not to import data.

Practice this question →

118

MCQmedium

A company wants to predict which customers are likely to churn in the next 30 days using historical data and AI. Which feature in Dynamics 365 Customer Insights should they use?

A.Segmentation

B.Measures

C.Copilot

D.Predictions

AnswerD

Correct: The Predictions feature uses AI to forecast outcomes like churn.

Why this answer

The Predictions feature in Dynamics 365 Customer Insights uses prebuilt AI models to analyze historical customer data and calculate churn probability scores for a specified future period, such as the next 30 days. This directly addresses the requirement to predict which customers are likely to churn, as it leverages machine learning to identify patterns and generate actionable insights without requiring custom model building.

Exam trap

The trap here is that candidates confuse the general AI assistance of Copilot with the specific predictive modeling capability of Predictions, or assume that Segmentation can be used to forecast churn by manually defining rules, when in fact only Predictions provides AI-driven churn probability scores.

How to eliminate wrong answers

Option A is wrong because Segmentation is used to group customers based on static or dynamic criteria (e.g., demographics, past behavior) but does not apply AI to predict future outcomes like churn. Option B is wrong because Measures are calculations (e.g., sum, count, average) over customer data to define KPIs, not predictive models that forecast future events. Option C is wrong because Copilot is an AI-powered assistant for natural language queries and task automation within the interface, not a dedicated predictive analytics tool for churn modeling.

Practice this question →

119

MCQeasy

Refer to the exhibit. A company configures enrichment in Customer Insights as shown. What will this enrichment do?

A.Unify customer data from Microsoft sources

B.Add interest data from Microsoft to customer profiles

C.Create a segment of customers with similar interests

D.Predict which customers are interested in a product

AnswerB

Microsoft enrichment provides interest data.

Why this answer

The enrichment in Customer Insights is configured to add interest data from Microsoft to customer profiles. This is because the enrichment feature allows you to pull in external data sources, such as Microsoft's interest and demographic data, to enhance existing customer profiles with additional attributes like brand affinities or lifestyle interests.

Exam trap

The trap here is that candidates confuse enrichment with segmentation or prediction, assuming that adding interest data automatically creates a segment or generates predictions, when enrichment only populates profile attributes for later use.

How to eliminate wrong answers

Option A is wrong because unifying customer data from Microsoft sources is a function of data unification or data ingestion, not enrichment; enrichment specifically adds new attributes from external sources rather than merging existing data. Option C is wrong because creating a segment of customers with similar interests is a separate segmentation step that uses enriched data, not the enrichment process itself. Option D is wrong because predicting which customers are interested in a product is a predictive model or machine learning capability, not a direct outcome of enrichment, which only adds static interest data.

Practice this question →

120

MCQhard

A financial services company uses Dynamics 365 Customer Insights - Data. They need to ensure customer data is protected according to GDPR. They want to automatically delete customer profiles after a retention period. Which feature should they configure?

A.Data sources

B.Enrichment

C.Data privacy

D.Data sharing

AnswerC

Data privacy allows administrators to set retention policies and automatically delete customer profiles after a specified period.

Why this answer

Customer Insights includes a Data privacy feature that allows administrators to set retention policies and automatically delete customer profiles after a specified period, helping ensure GDPR compliance. Option A is incorrect because Data sources are used to import data, not manage deletion. Option B is incorrect because Enrichment enhances data with additional attributes, not deletion.

Option D is incorrect because Data sharing controls access to data with other systems, not retention.

Practice this question →

121

Multi-Selecthard

An organization uses Dynamics 365 Customer Insights - Data. They want to ensure that the customer profiles are enriched with demographic data from a third-party provider. Which THREE steps are necessary to set up enrichment? (Choose three.)

Select 3 answers

A.Select the fields to be enriched

B.Map the external data attributes to your customer attributes

C.Create an export destination for the enriched data

D.Configure the enrichment provider

E.Define a matching rule to merge enriched data

AnswersA, B, D

You must specify which fields (e.g., demographic) to enrich.

Why this answer

In Dynamics 365 Customer Insights - Data, when setting up enrichment, you must select the specific fields (e.g., demographic attributes like age, income, or location) from your customer profile that you want to enrich with third-party data. This step defines which existing attributes will be updated or supplemented by the enrichment provider.

Exam trap

The trap here is that candidates often confuse enrichment steps with data export or data merging steps, mistakenly selecting 'Create an export destination' or 'Define a matching rule' as part of enrichment, when they belong to separate data management workflows.

Practice this question →

122

MCQmedium

A retailer uses Customer Insights to track customer interactions across online and offline channels. They notice that some customers have duplicate profiles. What is the first step to resolve this?

A.Export data to Excel and deduplicate there

B.Create a segment of duplicates

C.Delete the duplicate profiles manually

D.Run data unification with appropriate matching rules

AnswerD

Unification merges duplicates based on rules.

Why this answer

Customer Insights provides a built-in data unification process that uses matching rules to identify and merge duplicate customer profiles. This is the recommended first step to resolve duplicates, as it leverages the platform's deduplication capabilities without manual intervention or data export.

Exam trap

The trap here is that candidates may think manual deletion or export-based deduplication is faster, but the exam tests the understanding that Customer Insights has a dedicated, automated data unification feature designed specifically for this purpose.

How to eliminate wrong answers

Option A is wrong because exporting data to Excel for deduplication bypasses the native deduplication features of Customer Insights, introduces manual errors, and does not integrate back into the system. Option B is wrong because creating a segment of duplicates only identifies the duplicates but does not resolve them; it is a diagnostic step, not a resolution step. Option C is wrong because manually deleting duplicate profiles is inefficient, error-prone, and does not leverage the automated matching and merging rules that Customer Insights provides.

Practice this question →

123

MCQmedium

You are a marketing manager for a retail company that uses Dynamics 365 Customer Insights. You want to create a segment of customers who have not made a purchase in the last 90 days and who have a high predicted churn score. You have already set up a predictive churn model. However, when you try to create the segment using the churn score, you notice that the churn score field is not available in the segment builder. What is the most likely reason?

A.The churn model has not been published.

B.The churn model is still training.

C.The churn model was created from a different data source.

D.The customer data has not been unified.

AnswerA

Model must be published to use outputs.

Why this answer

The churn score field is generated by the predictive churn model and only becomes available in the segment builder after the model has been published. Until the model is published, the churn score is not written to the customer entity, so the field does not appear as a selectable attribute. Publishing the model finalizes the scores and makes them available for segmentation.

Exam trap

The trap here is that candidates may assume the churn model is automatically available for segmentation once trained, but Microsoft Dynamics 365 requires an explicit publish action to make the output fields accessible in the segment builder.

How to eliminate wrong answers

Option B is wrong because a model that is still training would not produce scores, but the question states the model has already been set up, implying training is complete; the issue is that the field is missing, not that scores are pending. Option C is wrong because the churn model uses the same unified customer data within Customer Insights, and a different data source would not prevent the churn score field from appearing in the segment builder—it would simply use that source's data for scoring. Option D is wrong because data unification is a prerequisite for running the churn model, and if data were not unified, the model would not have been set up successfully; the field's absence is due to the publication step, not unification.

Practice this question →

124

MCQhard

A company uses Dynamics 365 Customer Insights - Data and wants to ensure that customer data from the EU complies with GDPR. What should they configure?

A.Microsoft 365 compliance center

B.Data classification labels in Microsoft Purview

C.Data loss prevention (DLP) policies in Power Platform admin center

D.Data privacy settings within Customer Insights

AnswerD

Customer Insights has built-in privacy settings for GDPR compliance.

Why this answer

Dynamics 365 Customer Insights - Data includes data privacy settings specifically designed to help meet GDPR requirements, such as data retention policies, consent management, and data subject rights (e.g., delete or export). Option A is incorrect because the Microsoft 365 compliance center is for broader compliance across Microsoft 365 services, not directly for Customer Insights data. Option B is incorrect because data classification labels in Microsoft Purview are used for labeling sensitive data across the organization, but they are not the specific configuration within Customer Insights for GDPR compliance.

Option C is incorrect because DLP policies in Power Platform admin center govern data leakage prevention across Power Platform, but they do not address Customer Insights' specific privacy settings needed for GDPR.

Practice this question →

125

MCQeasy

A company is using Dynamics 365 Customer Insights to get a unified view of their customers. They have data from their e-commerce platform, CRM system, and customer support tickets. Which step is required to ensure that the same customer is recognized across these different data sources?

A.Enrich profiles with external data

B.Configure data matching rules

C.Create measures and KPIs

D.Set up data export destinations

AnswerB

Matching rules identify duplicates across sources.

Why this answer

B is correct because data matching rules in Dynamics 365 Customer Insights define how records from different sources (e-commerce, CRM, support tickets) are identified as belonging to the same customer. These rules use conditions like email, phone, or name to deduplicate and unify customer profiles into a single entity, ensuring consistent recognition across all ingested data sources.

Exam trap

The trap here is that candidates often confuse data enrichment (Option A) with identity resolution, mistakenly thinking adding external data is the key to linking records, when in fact matching rules are the core mechanism for unification.

How to eliminate wrong answers

Option A is wrong because enriching profiles with external data adds third-party attributes (e.g., demographic or credit scores) but does not perform identity resolution or matching to link records across sources. Option C is wrong because creating measures and KPIs calculates aggregated metrics (e.g., customer lifetime value) on already unified data, not the step to achieve unification itself. Option D is wrong because setting up data export destinations defines where unified data is sent (e.g., Azure Blob or Power BI), which occurs after unification, not as a prerequisite for recognizing the same customer across sources.

Practice this question →

126

Multi-Selectmedium

Which THREE data sources can be used to ingest data into Dynamics 365 Customer Insights?

Select 3 answers

A.Power BI dataflows

B.Microsoft Dataverse

C.SharePoint Online

D.Azure Blob Storage

E.Microsoft Excel files

AnswersA, B, D

Correct: Power BI dataflows can be used as a source.

Why this answer

Power BI dataflows are a valid data source for Dynamics 365 Customer Insights because they allow you to ingest, transform, and load data from various sources (e.g., databases, files, or cloud services) into Customer Insights. This integration leverages the Common Data Model to ensure data consistency and supports scheduled refreshes for up-to-date analytics.

Exam trap

The trap here is that candidates often assume any common data source like SharePoint or Excel is supported, but Microsoft specifically restricts direct ingestion to Power BI dataflows, Dataverse, and Azure Blob Storage to ensure data governance and schema compatibility.

Practice this question →

127

MCQhard

You are a solutions architect for a multinational corporation that uses Dynamics 365 Customer Insights. The company has customer data from multiple subsidiaries, each using different CRM and ERP systems. They want to create a single, unified customer profile that complies with data privacy regulations such as GDPR and CCPA. Additionally, they want to use the unified data to drive personalized marketing campaigns in Dynamics 365 Marketing. You need to design a solution that ensures data privacy and compliance. What should you do first?

A.Configure data privacy and compliance settings in Dynamics 365 Customer Insights, including data subject rights, consent management, and data retention policies.

B.Create segments for marketing campaigns before unifying the data, to test the process.

C.Export the unified customer profiles to Dynamics 365 Marketing and apply data privacy policies in Marketing.

D.Ingest all customer data from each subsidiary into Dynamics 365 Customer Insights and start the unification process.

AnswerA

Correct: This establishes the foundation for compliant data handling.

Why this answer

Data privacy and compliance settings must be configured before any data ingestion or unification. Dynamics 365 Customer Insights includes features for managing data subject rights (e.g., GDPR delete/export), consent, and retention policies. Establishing governance first ensures all subsequent processing complies with regulations like GDPR and CCPA.

Option B is incorrect because segmentation should occur after unification and governance, not before. Option C is incorrect because data privacy policies should be enforced in Customer Insights, the system of record for unified profiles, before exporting to Marketing. Option D is incorrect because ingesting data without first configuring privacy and compliance settings risks violating data protection regulations.

Practice this question →

128

MCQmedium

A marketing team wants to use Dynamics 365 Customer Insights to predict which customers are likely to churn. They have historical data on customer interactions and purchases. What should they create first?

A.A segment

B.A customer data unification process

C.A predictive model

D.An enrichment

AnswerB

Unifies data into single profiles.

Why this answer

Before any predictive analysis can be performed, the customer data must be unified into a single, coherent profile. In Dynamics 365 Customer Insights, the customer data unification process (data ingestion, mapping, matching, and merging) creates a unified customer entity. Without this unified view, predictive models cannot accurately identify churn patterns because they would be operating on fragmented or duplicated data.

Exam trap

The trap here is that candidates often assume a predictive model can be created immediately from raw data, overlooking the prerequisite of data unification which is the critical first step in Customer Insights.

How to eliminate wrong answers

Option A is wrong because a segment is a subset of unified customer profiles used for targeting or analysis; you cannot create a meaningful segment until the data is unified. Option C is wrong because a predictive model relies on unified customer data as its input; building a model before unification would produce unreliable results due to data inconsistencies. Option D is wrong because enrichment adds external data (e.g., demographic or firmographic attributes) to existing unified profiles, but it is not the foundational first step—unification must occur first.

Practice this question →

129

MCQhard

You are reviewing the exhibit of a Customer Insights - Data entity definition. The company wants to create a segment of customers whose TotalPurchaseAmount is greater than 1000. Which attribute should be used in the segment condition?

A.CustomerId

B.FirstName

C.Email

D.TotalPurchaseAmount

AnswerD

TotalPurchaseAmount holds the purchase amount value.

Why this answer

The segment condition requires an attribute that stores the total purchase amount for each customer. In Dynamics 365 Customer Insights - Data, the TotalPurchaseAmount attribute is a numeric measure that can be directly compared using a greater-than operator. Using any other attribute, such as CustomerId, FirstName, or Email, would not evaluate the purchase amount condition.

Exam trap

The trap here is that candidates may mistakenly think any customer attribute can be used in a numeric condition, but only attributes defined as numeric measures (like TotalPurchaseAmount) support comparison operators such as greater than.

How to eliminate wrong answers

Option A is wrong because CustomerId is a unique identifier for a customer record, not a numeric measure of purchase totals, so it cannot be used to evaluate a condition like > 1000. Option B is wrong because FirstName is a text attribute containing the customer's first name, which cannot be compared numerically. Option C is wrong because Email is a string attribute used for contact purposes, and it does not store purchase amount data.

Practice this question →

130

Multi-Selecthard

Which THREE outputs can be generated using Dynamics 365 Customer Insights?

Select 3 answers

A.Measures and KPIs

B.Invoice documents

C.Purchase orders

D.Customer segments

E.Predictive models

AnswersA, D, E

Measures are calculated outputs.

Why this answer

Dynamics 365 Customer Insights allows users to define and compute Measures and KPIs from unified customer data. These are aggregated calculations (e.g., average order value, churn rate) that provide actionable insights into customer behavior and business performance, directly supporting data-driven decision-making.

Exam trap

The trap here is that candidates confuse Customer Insights' analytical outputs (measures, segments, models) with transactional documents (invoices, purchase orders) that belong to operational ERP modules, testing whether you understand the CDP's scope as a data unification and insight platform.

Practice this question →

131

MCQhard

A financial services company uses Dynamics 365 Customer Insights to manage customer data. They need to ensure that the data unification process complies with GDPR right to erasure. Which feature should they configure to handle such requests?

A.Enrich profiles with consent data

B.Data source connection settings

C.Use the Customer Insights data lifecycle management to delete profiles based on a data subject request

D.Configure export destinations to exclude certain data

AnswerC

Lifecycle management allows deletion of profiles.

Why this answer

Customer Insights provides a dedicated data lifecycle management feature that allows administrators to delete individual customer profiles in response to a data subject request (DSR) under GDPR. This feature directly supports the right to erasure by enabling targeted deletion of a specific profile and its associated data across all unified customer entities, ensuring compliance without affecting other records.

Exam trap

The trap here is that candidates may confuse consent management (Option A) with the actual deletion mechanism, or think that export exclusions (Option D) can retroactively remove data, when in fact only the lifecycle management feature performs a permanent, targeted deletion of the unified profile.

How to eliminate wrong answers

Option A is wrong because enriching profiles with consent data captures and stores consent preferences (e.g., marketing opt-in), but it does not provide a mechanism to delete a profile in response to an erasure request. Option B is wrong because data source connection settings control how data is imported from external systems (e.g., Azure Data Lake, Dataverse), not how existing unified profiles are managed or deleted. Option D is wrong because configuring export destinations to exclude certain data controls what data is sent to external systems (e.g., Power BI, Azure Synapse), but it does not delete the source profile within Customer Insights itself.

Practice this question →

132

MCQmedium

A company wants to use Customer Insights to identify customers who are likely to respond to a new product campaign. Which feature should they use?

A.Enrichment

B.Predictive scoring

C.Measures

D.Segmentation

AnswerB

Predictive scoring uses AI to predict customer behavior such as likelihood to respond.

Why this answer

Predictive scoring in Dynamics 365 Customer Insights uses machine learning models to analyze historical customer data and engagement patterns, assigning a score that predicts the likelihood of a specific outcome—such as responding to a new product campaign. This directly matches the company's goal of identifying high-propensity customers for targeted outreach.

Exam trap

The trap here is that candidates confuse Segmentation (a static grouping tool) with Predictive scoring (a dynamic machine learning output), because both can be used to target customers, but only Predictive scoring answers the 'likely to respond' question using probability modeling.

How to eliminate wrong answers

Option A is wrong because Enrichment is used to augment customer profiles with external data sources (e.g., demographic or firmographic data), not to predict future behaviors like campaign response. Option C is wrong because Measures are aggregated calculations (e.g., total spend or average order value) that summarize historical data, but they do not generate predictive scores for future actions. Option D is wrong because Segmentation groups customers based on static criteria or rules (e.g., age or purchase history), but it lacks the predictive modeling capability to forecast which customers are most likely to respond to a campaign.

Practice this question →

133

Multi-Selectmedium

A company wants to use Customer Insights to improve customer retention. Which TWO features should they use?

Select 2 answers

A.Data profiling

B.Segments (based on churn risk)

C.Data sources configuration

D.Predictive models (churn model)

E.Data exports to external systems

AnswersB, D

Segments can be used to target retention campaigns.

Why this answer

Segments based on churn risk (Option B) allow you to group customers who are likely to leave, enabling targeted retention campaigns. Predictive models, specifically the churn model (Option D), use historical data and machine learning to calculate a churn probability score for each customer, which directly feeds into those segments. Together, they provide the actionable intelligence needed to proactively intervene and improve retention.

Exam trap

The trap here is that candidates confuse foundational setup tasks (data profiling, data sources, exports) with the actual analytical features (segments and predictive models) that directly solve the business problem of improving retention.

Practice this question →

134

MCQhard

A data analyst needs to create a measure in Dynamics 365 Customer Insights - Data that calculates the total revenue per customer from the past 90 days. They have a 'Sales' entity with fields: CustomerID, Revenue, and TransactionDate. Which type of measure should they create?

A.Calculated measure

B.Entity measure

C.Dimension measure

D.Attribute measure

AnswerA

Calculated measures allow custom aggregations like SUM over a time filter.

Why this answer

A calculated measure in Dynamics 365 Customer Insights - Data is used to perform aggregations (like SUM, COUNT, AVG) over a specified time window, such as the past 90 days, using fields from a single entity. Since the requirement is to sum Revenue per CustomerID filtered by TransactionDate within a rolling 90-day period, a calculated measure is the correct type because it allows defining a measure with a time-based filter and aggregation logic directly on the 'Sales' entity.

Exam trap

The trap here is that candidates confuse 'calculated measure' with 'entity measure' because both involve aggregation, but entity measures require a relationship between entities (e.g., a join), whereas a calculated measure works on a single entity with a filter.

How to eliminate wrong answers

Option B is wrong because an entity measure is used to compute metrics across multiple entities (e.g., joining 'Sales' with 'Customer'), not for a single-entity aggregation with a time filter. Option C is wrong because a dimension measure is not a valid measure type in Dynamics 365 Customer Insights - Data; dimensions are attributes used for grouping, not measures. Option D is wrong because an attribute measure does not exist in this context; attributes are fields within an entity, not a type of measure that can perform calculations or time-based filtering.

Practice this question →

135

MCQhard

Contoso Ltd. is a multinational retailer using Dynamics 365 Customer Insights to unify customer data from three regional CRM systems (North America, Europe, Asia) and a global e-commerce platform. The company has configured data sources for each system and run data unification, but the unified customer profiles show a high number of duplicates (approximately 15% of profiles are duplicates). The administrator has tried increasing the match confidence threshold but the problem persists. Additionally, the company wants to ensure that customer consent preferences (opt-in for marketing) are synchronized across all profiles. The administrator is considering adjusting the unification rules. The current matching rules use only email address. What is the best course of action to reduce duplicates while maintaining data accuracy?

A.Create separate unifications for each region

B.Add additional matching conditions such as phone number and postal code

C.Remove the email condition and use only customer name

D.Lower the match confidence threshold to 50% to match more records

AnswerB

Multiple conditions improve matching accuracy.

Why this answer

Adding additional matching conditions (such as phone number and postal code) increases the precision of duplicate detection. With only email as the match condition, records that share the same email but belong to different individuals (e.g., family accounts) or have data entry errors are incorrectly merged. By requiring multiple identifiers to match, the system reduces false positives while still catching true duplicates, improving the overall accuracy of the unified customer profiles.

Exam trap

The trap here is that candidates may think lowering the confidence threshold will reduce duplicates, but in reality, lowering the threshold increases the number of matched records (including false positives), while the correct approach is to add more matching conditions to improve precision without sacrificing recall.

How to eliminate wrong answers

Option A is wrong because creating separate unifications for each region would prevent cross-region duplicate detection and defeat the purpose of a single unified customer view, leading to fragmented profiles. Option C is wrong because removing the email condition and using only customer name would drastically increase false positives (names are not unique) and likely worsen the duplicate problem. Option D is wrong because lowering the match confidence threshold to 50% would match more records, increasing the number of false duplicates rather than reducing them, and would not address the root cause of insufficient matching criteria.

Practice this question →

136

MCQmedium

A retail company uses Dynamics 365 Customer Insights to unify customer data from online and in-store transactions. They want to define a customer segment based on customers who have made a purchase within the last 30 days and have a lifetime value above $500. Which feature should they use?

A.Create a segment based on conditions

B.Create a measure

C.Enrich customer profiles with demographic data

D.Create a prediction model

AnswerA

Segments can be defined using conditions on measures and activities.

Why this answer

Dynamics 365 Customer Insights allows you to define a segment based on conditions, such as combining a purchase recency filter (last 30 days) with a calculated lifetime value threshold (>$500). This uses the segment builder's rule-based logic to query unified customer profiles and transactional data, enabling precise targeting without custom code.

Exam trap

The trap here is confusing a measure (aggregated metric) with a segment (group of customers), as both involve conditions but serve fundamentally different purposes in Customer Insights.

How to eliminate wrong answers

Option B is wrong because a measure aggregates data (e.g., sum of purchases) into a metric, but it does not create a dynamic group of customers; segments are needed for grouping. Option C is wrong because enriching profiles with demographic data adds external attributes (e.g., age, income) but does not filter customers based on purchase recency or lifetime value conditions. Option D is wrong because a prediction model forecasts future behavior (e.g., churn probability) rather than defining a static rule-based segment based on historical data.

Practice this question →

137

MCQmedium

A manufacturing company uses Dynamics 365 Sales and Customer Insights. They want to identify customers who are likely to churn based on support ticket volume and purchase recency. Which Customer Insights feature should they use to build this analysis?

A.Predictive models

B.Measures

C.Segments

D.Enrichment

AnswerA

Predictive models, such as churn models, use historical data to predict future behavior.

Why this answer

A is correct because Predictive models in Dynamics 365 Customer Insights use built-in machine learning to analyze historical data—such as support ticket volume and purchase recency—and generate a churn probability score for each customer. This allows the company to proactively identify customers at risk of churning without requiring custom data science work.

Exam trap

The trap here is that candidates confuse Segments (which can be dynamic and based on conditions) with Predictive models, not realizing that Segments only filter existing data while Predictive models generate new probabilistic insights.

How to eliminate wrong answers

Option B is wrong because Measures are used to define and calculate KPIs or aggregations (e.g., total support tickets per customer), but they do not apply machine learning to predict future outcomes like churn. Option C is wrong because Segments are static or dynamic groupings of customers based on defined criteria (e.g., customers with >5 tickets in 30 days), but they do not generate predictive probability scores or model churn likelihood. Option D is wrong because Enrichment is used to append external data (e.g., demographic or firmographic data) to customer profiles, not to build predictive analyses from internal data.

Practice this question →

138

MCQmedium

A company is planning to implement Dynamics 365 Customer Insights. They have customer data stored in an on-premises SQL Server database and also in Salesforce CRM. They want to unify this data in Customer Insights. Which data ingestion method should they use to bring data from both sources?

A.Use Power Query connectors for cloud data only, then use a gateway for on-premises SQL

B.Use Power Query with a gateway for on-premises SQL and the Salesforce connector for Salesforce

C.Export data from SQL to Azure Blob Storage and then ingest from Blob, and use Salesforce API

D.Use third-party ETL tool to push data into Customer Insights via API

AnswerB

Both data sources can be ingested using Power Query connectors.

Why this answer

Dynamics 365 Customer Insights uses Power Query as its primary data ingestion engine, which supports both on-premises SQL Server via an on-premises data gateway and cloud-based Salesforce CRM through a dedicated Salesforce connector. This allows the company to unify data from both sources without requiring intermediate storage or third-party tools.

Exam trap

The trap here is that candidates may think on-premises data requires a separate ingestion method like Azure Blob Storage, not realizing that Power Query with an on-premises data gateway can directly connect to SQL Server, and that the Salesforce connector is a native Power Query connector.

How to eliminate wrong answers

Option A is wrong because it incorrectly states that Power Query connectors are for cloud data only; in reality, Power Query can connect to on-premises SQL Server using an on-premises data gateway, and the Salesforce connector is a native cloud connector. Option C is wrong because it introduces unnecessary complexity by requiring data export to Azure Blob Storage and then ingestion, which is not the recommended or direct method for Customer Insights when native connectors exist. Option D is wrong because while third-party ETL tools can push data via API, this is an indirect, more complex approach that bypasses the built-in, simpler Power Query connectors provided by Customer Insights.

Practice this question →

139

MCQhard

A company uses Dynamics 365 Customer Insights - Journeys. They have a journey that sends a discount offer to customers who have not made a purchase in 30 days. They notice that some customers are receiving the offer multiple times. Which journey setting should they modify?

A.Entity

B.Goal

C.Schedule

D.Frequency capping

AnswerD

Frequency capping limits how many times a customer can enter the journey or receive communications.

Why this answer

Frequency capping is the correct setting because it limits how many times a customer can enter or receive communications from a journey within a specified period. In Dynamics 365 Customer Insights - Journeys, this prevents customers who meet the trigger condition (e.g., no purchase in 30 days) from being re-entered into the same journey repeatedly, which is the root cause of receiving the offer multiple times.

Exam trap

The trap here is that candidates often confuse 'Schedule' (which controls when the journey runs) with the mechanism that prevents individual contacts from being re-entered, not realizing that frequency capping is a separate, contact-level suppression setting.

How to eliminate wrong answers

Option A is wrong because 'Entity' refers to the data table (e.g., Contact, Lead) that the journey targets, not a setting to control message repetition. Option B is wrong because 'Goal' is used to define and track a business outcome (e.g., number of purchases) within a journey, not to limit how often a customer receives messages. Option C is wrong because 'Schedule' defines the start and end times or recurrence pattern of the journey, but does not prevent a customer from being re-triggered multiple times if they continue to meet the entry condition.

Practice this question →

140

MCQhard

A large enterprise uses Dynamics 365 Customer Insights to manage customer data from multiple subsidiaries. They want to ensure that each subsidiary can only see their own customer data but the corporate team can see all data. What is the best approach?

A.Create separate data partitions within Customer Insights and assign access permissions accordingly

B.Create separate segments for each subsidiary

C.Apply enrichment filters to hide data

D.Use match rules to keep data separate

AnswerA

Data partitions allow segmentation of data and access control.

Why this answer

Data partitions in Dynamics 365 Customer Insights allow you to logically separate data from different sources (e.g., subsidiaries) within a single environment. By assigning role-based access permissions to each partition, you ensure that subsidiary users can only view their own partition data, while corporate users with broader permissions can access all partitions. This is the designed mechanism for multi-tenant or multi-business-unit data isolation without duplicating infrastructure.

Exam trap

The trap here is that candidates confuse segments (which are just filtered views of data) with security boundaries, assuming that creating separate segments for each subsidiary would restrict visibility, but segments do not enforce access control at the data level.

How to eliminate wrong answers

Option B is wrong because segments are dynamic groupings of customer profiles based on criteria, not a security boundary; they cannot enforce data visibility restrictions. Option C is wrong because enrichment filters are used to enhance data with external insights (e.g., demographics), not to hide data from users; they do not control access permissions. Option D is wrong because match rules define how to unify duplicate customer records across data sources, not how to separate or secure data; they would actually merge data, which is the opposite of the desired isolation.

Practice this question →

141

MCQmedium

A company wants to use Dynamics 365 Customer Insights to send personalized marketing emails based on customer behavior. Which integration is most appropriate?

A.Power Automate

B.Power Apps

C.Power BI

D.Dynamics 365 Marketing

AnswerD

Customer Insights integrates with Marketing to use unified data for personalized journeys.

Why this answer

Dynamics 365 Marketing is the correct integration because it is purpose-built to orchestrate customer journeys and send personalized marketing emails based on behavioral data from Customer Insights. Customer Insights provides unified customer profiles and AI-driven insights, which Dynamics 365 Marketing consumes via real-time segmentation and triggers to deliver tailored communications.

Exam trap

The trap here is that candidates often confuse Power Automate's ability to send emails (via connectors like Outlook) with the enterprise-grade marketing automation required for personalized, compliant email campaigns, overlooking that Dynamics 365 Marketing is the dedicated solution for this scenario.

How to eliminate wrong answers

Option A is wrong because Power Automate is a workflow automation tool that can trigger actions (e.g., send an email via a connector), but it lacks native marketing-specific features like email templates, journey design, consent management, and compliance with marketing regulations. Option B is wrong because Power Apps is a low-code application platform for building custom apps, not for sending marketing emails or managing customer journeys. Option C is wrong because Power BI is a data visualization and analytics tool; it cannot send emails or execute marketing campaigns.

Practice this question →

142

Multi-Selecthard

Which THREE actions can be performed using Dynamics 365 Customer Insights? (Choose three.)

Select 3 answers

A.Predict customer churn

B.Create dynamic segments based on customer behavior

C.Unify customer data from multiple sources

D.Manage IT device compliance

E.Design email marketing campaigns

AnswersA, B, C

Prediction models include churn.

Why this answer

Options A, B, and C are correct. Customer Insights can unify customer data from multiple sources, create dynamic segments based on customer behavior, and predict customer churn. Option D is incorrect because managing IT device compliance is not a feature of Customer Insights; that would be related to endpoint management.

Option E is incorrect because designing email marketing campaigns is done in Dynamics 365 Marketing, not Customer Insights.

Practice this question →

143

Multi-Selecteasy

A company uses Dynamics 365 Customer Insights - Data to unify customer records. They want to enrich their customer profiles with data from external sources. Which THREE enrichment sources are available in Customer Insights - Data? (Choose three.)

Select 3 answers

A.Experian

B.Sales Insights

C.Power Query

D.Microsoft enrichment

E.Acxiom

AnswersA, D, E

Experian is a built-in enrichment partner.

Why this answer

Experian is a third-party data provider integrated with Dynamics 365 Customer Insights - Data, allowing organizations to enrich customer profiles with demographic, financial, and lifestyle data. This enrichment source is available out-of-the-box to append external attributes to unified customer records, improving segmentation and personalization.

Exam trap

The trap here is that candidates confuse data transformation tools like Power Query with pre-built enrichment sources, or mistake Sales Insights (a separate product) for an enrichment service within Customer Insights - Data.

Practice this question →

144

MCQhard

A customer data platform administrator notices that duplicate customer records appear after unification. They want to review and adjust the matching rules. Where in Customer Insights can they do this?

A.Duplicate detection

B.Data sources

C.Admin settings

D.Data unification

AnswerD

Correct: In the Data unification process, you can configure match rules and conditions.

Why this answer

In Dynamics 365 Customer Insights, the matching rules that determine how duplicate customer records are identified and merged during the unification process are configured within the Data unification section. Specifically, after selecting data sources and mapping fields, the administrator defines match conditions (e.g., exact or fuzzy matching on email, phone) under the 'Match' step. Adjusting these rules directly controls how duplicates are detected and resolved during unification.

Exam trap

The trap here is that candidates confuse the general 'Duplicate detection' feature in Dynamics 365 (Option A) with the specific matching rule configuration within Customer Insights' data unification workflow, leading them to select a feature that exists in a different module.

How to eliminate wrong answers

Option A is wrong because 'Duplicate detection' is a feature in Dynamics 365 Sales (and other model-driven apps) that runs on-demand or via workflows to find duplicates in existing records, but it is not the location to adjust matching rules within Customer Insights' data unification pipeline. Option B is wrong because 'Data sources' is where administrators add, configure, and refresh source data (e.g., CSV, Dataverse, Azure Data Lake), but it does not contain the matching rule settings for unification. Option C is wrong because 'Admin settings' in Customer Insights covers system-level configurations like permissions, environment settings, and data privacy, not the specific matching rules used during the unification process.

Practice this question →

145

MCQhard

A marketing team at a manufacturing company uses Customer Insights to create a segment of customers who have purchased a specific product in the last 30 days. They want to send a promotional email to this segment. However, the segment results are empty even though they know customers have purchased the product within that timeframe. What is the most likely cause?

A.The data retention policy is set to 7 days

B.The segment has not been refreshed since the purchases were ingested

C.The data source is offline

D.The segment definition is incorrect

AnswerB

Segments need to be refreshed to reflect new data.

Why this answer

In Dynamics 365 Customer Insights, segments are static snapshots of customer data at the time of creation or last refresh. Even if purchase data has been ingested into the system, the segment will not automatically include those new records until it is explicitly refreshed. Since the segment results are empty despite known purchases, the most likely cause is that the segment has not been refreshed after the purchases were ingested.

Exam trap

The trap here is that candidates may assume segments are dynamic and automatically update with new data, but in Customer Insights, segments are static and require an explicit refresh to reflect recent changes.

How to eliminate wrong answers

Option A is wrong because the data retention policy controls how long raw data is stored, not the freshness of segment results; a 7-day retention would still allow purchases within the last 30 days to be present. Option C is wrong because if the data source were offline, the purchases would not have been ingested at all, contradicting the premise that customers have purchased the product. Option D is wrong because the segment definition is described as correct (customers who purchased a specific product in the last 30 days), and an incorrect definition would typically return incorrect results, not an empty segment when purchases exist.

Practice this question →

146

MCQeasy

A retail company wants to create a unified customer profile by combining data from their online store, loyalty program, and in-store purchases. Which Dynamics 365 Customer Insights capability should they use?

A.Run data unification

B.Create a prediction model

C.Define a measure

D.Create a segment

AnswerA

Data unification matches and merges records from different sources.

Why this answer

The 'Run data unification' capability in Dynamics 365 Customer Insights is specifically designed to ingest data from multiple sources (e.g., online store, loyalty program, in-store purchases) and match, merge, and deduplicate records to create a single, unified customer profile. This process uses matching rules and deduplication logic to resolve identities across disparate systems, directly addressing the requirement for a combined customer view.

Exam trap

The trap here is that candidates often confuse 'unification' with 'segmentation' or 'measures,' mistakenly thinking that creating a segment or measure can combine data from multiple sources, when in fact unification is the prerequisite step that merges raw data into a single customer entity.

How to eliminate wrong answers

Option B is wrong because 'Create a prediction model' is used for predictive analytics (e.g., churn or purchase likelihood) and does not perform data ingestion or identity resolution; it requires already unified data. Option C is wrong because 'Define a measure' creates KPIs or aggregations (e.g., total spend) from existing data but does not combine or unify data from different sources. Option D is wrong because 'Create a segment' filters or groups existing unified profiles based on attributes or behaviors, but it cannot merge data from multiple sources into a single profile.

Practice this question →

147

Matchingmedium

Match each Dynamics 365 capability to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

AI-powered assistant that helps draft emails, summarize, and generate insights

Unify customer data from multiple sources to create a single view

Create and send surveys to measure customer satisfaction

Integrate IoT data to proactively detect and resolve issues

Use AI to prioritize leads and recommend next best actions

Why these pairings

Each Dynamics 365 app targets specific business functions. Sales manages leads and pipelines; Customer Service resolves cases; Marketing automates campaigns; Finance handles financials. The distractors swap Sales with Marketing and Sales with Customer Service.

Practice this question →

148

MCQmedium

A company wants to use Customer Insights to generate AI-driven product recommendations for their e-commerce site. Which feature should they configure?

A.Measures

B.Connections

C.Segmentation

D.AI suggestions

AnswerD

AI suggestions use machine learning to recommend products based on customer behavior.

Why this answer

AI suggestions in Dynamics 365 Customer Insights leverage built-in machine learning models to analyze customer behavior and transaction data, generating personalized product recommendations for e-commerce sites. This feature directly addresses the requirement for AI-driven recommendations without needing custom model training.

Exam trap

The trap here is that candidates confuse Segmentation (grouping customers) with AI-driven recommendations, but segmentation only defines audiences, while AI suggestions use machine learning to predict what products a specific customer is likely to buy.

How to eliminate wrong answers

Option A is wrong because Measures are used to define KPIs and aggregate data (e.g., total sales, average order value), not to generate AI-driven product recommendations. Option B is wrong because Connections manage data ingestion from various sources (e.g., CRM, ERP) and unify customer profiles, but they do not produce AI-based recommendations. Option C is wrong because Segmentation groups customers into segments based on attributes or behaviors; while segments can be used with AI suggestions, segmentation itself does not generate product recommendations.

Practice this question →

149

MCQeasy

You are configuring a match rule for data unification. What does this rule specify?

A.Records with the exact same email address are considered a match

B.Records with the same CustomerId are considered a match

C.Records with the same name are considered a match

D.Records with similar email addresses are considered a match

AnswerA

Correct: ExactMatch means identical values.

Why this answer

In Dynamics 365 Customer Insights, a match rule defines the conditions under which two or more records are considered to represent the same entity (e.g., a customer). Specifying that records with the exact same email address are considered a match is a common and valid rule, as email addresses are typically unique identifiers. The rule uses exact matching logic, not fuzzy or similarity-based matching, to determine duplicates during data unification.

Exam trap

The trap here is that candidates often confuse match rules (which require exact matching) with deduplication or fuzzy matching rules, leading them to choose Option D which implies similarity-based matching, but the MB-910 exam specifically tests that match rules for data unification use exact criteria like email or phone.

How to eliminate wrong answers

Option B is wrong because CustomerId is typically a system-generated unique identifier that is already used as the primary key; match rules are designed to find duplicates across different data sources where such IDs may not exist or may differ, so matching on CustomerId would not help unify records from separate systems. Option C is wrong because names are not unique and often have variations (e.g., 'Bob' vs 'Robert'), so matching solely on the same name would produce many false positives; Customer Insights requires more reliable attributes like email or phone for exact matching. Option D is wrong because match rules in Customer Insights use exact matching, not similarity or fuzzy logic; 'similar email addresses' would require fuzzy matching, which is not supported in standard match rules (though deduplication can use fuzzy matching in other contexts, the question specifies a match rule for data unification, which uses exact criteria).

Practice this question →

150

Multi-Selecthard

Which TWO of the following are AI-powered features available in Dynamics 365 Customer Insights?

Select 2 answers

A.Email response sentiment analysis

B.Lead scoring

C.Predictive models for churn and purchase propensity

D.Anomaly detection in transaction data

E.Sentiment analysis of customer feedback

AnswersC, E

These are built-in AI models in Customer Insights.

Why this answer

Dynamics 365 Customer Insights includes AI-powered predictive models that analyze historical customer data to forecast behaviors such as churn and purchase propensity. These models use machine learning algorithms to generate scores and insights directly within the Customer Insights platform, enabling proactive engagement strategies.

Exam trap

The trap here is that candidates confuse the AI features of Dynamics 365 Customer Insights (a CDP focused on predictive models and sentiment analysis of feedback) with those of other Dynamics 365 apps like Sales (lead scoring) or Customer Service (email sentiment), leading them to select options that are valid elsewhere but not in Customer Insights.

Practice this question →