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

151

MCQmedium

A marketing team at a manufacturing company uses Dynamics 365 Customer Insights to target customers with personalized offers. They notice that the same customer receives multiple identical emails because the system treats each interaction as a separate profile. Which configuration step should they prioritize to resolve this issue?

A.Create new measures to track email engagement

B.Configure match rules to merge duplicate customer profiles

C.Verify that all data sources are correctly connected

D.Add more enrichment data to improve profile completeness

AnswerB

Match rules identify and merge duplicates, preventing duplicate emails.

Why this answer

Duplicate customer profiles cause the same person to receive multiple identical emails. Configuring match rules in Dynamics 365 Customer Insights allows the system to identify and merge duplicate profiles based on attributes like email or name, ensuring a single unified customer view and preventing redundant communications.

Exam trap

The trap here is that candidates may confuse data source connectivity (Option C) with profile deduplication, assuming that fixing data ingestion will automatically resolve duplicates, when in fact duplicates often arise from multiple sources even when all connections are healthy.

How to eliminate wrong answers

Option A is wrong because creating new measures to track email engagement would only monitor behavior after the fact, not prevent duplicate emails from being sent. Option C is wrong because verifying data source connections ensures data ingestion but does not address the core issue of duplicate profiles already in the system. Option D is wrong because adding enrichment data improves profile completeness but does not merge existing duplicates; enrichment adds attributes to profiles without resolving identity conflicts.

Practice this question →

152

MCQhard

A multinational corporation uses Dynamics 365 Customer Insights - Journeys to send personalized email campaigns. They want to ensure that customers in the European Union receive only emails for which they have given explicit consent, as required by GDPR. Which feature should they configure to manage consent at the contact level and enforce it in journey segments?

A.Segment filters

B.Compliance profiles

C.Subscription center

D.Data privacy search

AnswerB

Compliance profiles enforce consent settings required by GDPR.

Why this answer

Compliance profiles in Customer Insights - Journeys allow organizations to manage consent settings and enforce them in journey segments, ensuring that only contacts with explicit consent are included in email campaigns, as required by GDPR. Option B (Compliance profiles) is correct because it directly handles consent management and enforcement. Option A (Segment filters) can filter contacts but does not enforce consent compliance.

Option C (Subscription center) manages subscription preferences, but it does not enforce explicit consent for GDPR. Option D (Data privacy search) is used to respond to data subject requests, not for proactive consent management.

Practice this question →

153

MCQhard

A customer data platform administrator needs to ensure that Customer Insights complies with GDPR data deletion requests. What should they configure?

A.Data privacy

B.Segmentation

C.Data unification

D.Enrichment

AnswerA

Data privacy features allow administrators to delete or anonymize customer data to comply with GDPR.

Why this answer

The Data privacy page in Dynamics 365 Customer Insights is the dedicated area for managing GDPR compliance, including data deletion requests. Administrators can configure data deletion policies, run deletion jobs, and track the status of deletion requests to ensure customer data is removed in accordance with GDPR's right to erasure.

Exam trap

The trap here is that candidates may confuse data management features like Segmentation or Data unification with privacy compliance, not realizing that GDPR deletion is a specific administrative function isolated to the Data privacy configuration area.

How to eliminate wrong answers

Option B is wrong because Segmentation is used to create and manage customer segments based on data profiles, not to handle data deletion or privacy compliance. Option C is wrong because Data unification is the process of matching and merging duplicate customer records from different data sources, which does not involve configuring deletion policies or GDPR compliance. Option D is wrong because Enrichment refers to augmenting customer profiles with additional data from external sources (e.g., demographics or interests), which is unrelated to data deletion or privacy management.

Practice this question →

154

MCQmedium

Adventure Works Cycles uses Dynamics 365 Customer Insights to analyze customer behavior. They have ingested data from their online store, including browsing history, cart additions, and purchases. They want to create a segment of customers who have added items to the cart but not purchased in the last 7 days (abandoned cart). The data includes a 'CartAdd' table with fields: CustomerID, ProductID, Timestamp, and a 'Purchase' table with fields: CustomerID, ProductID, Timestamp, Amount. The segment is created with condition: CartAdd.Timestamp > 7 days ago AND NOT EXISTS (Purchase where CustomerID matches and ProductID matches and Purchase.Timestamp > CartAdd.Timestamp). However, the segment returns no members. What is the most likely reason?

A.The timestamp condition is reversed; it should be CartAdd.Timestamp < 7 days ago to find older carts

B.The segment requires a relationship between tables that is not defined

C.The 'NOT EXISTS' clause is not supported in Customer Insights segments

D.The Purchase table does not have the correct data

AnswerA

Correct logic for abandoned carts is older than 7 days.

Why this answer

The condition `CartAdd.Timestamp > 7 days ago` selects records where the cart addition occurred **less than** 7 days ago (i.e., within the last 7 days). To find customers who added items to the cart more than 7 days ago without purchase, the condition should be `CartAdd.Timestamp < 7 days ago` (older than 7 days). The segment returns no members because it is looking for recent cart additions instead of older ones.

The `NOT EXISTS` subquery logic is actually correct for abandoned carts (checking that no purchase occurred after the cart addition), but the primary issue is the reversed timestamp comparison.

Exam trap

The trap is that candidates may incorrectly focus on the `NOT EXISTS` subquery, thinking it's the cause of zero results, when the real issue is the timestamp direction. They might also confuse the meaning of '> 7 days ago' as 'older than 7 days' instead of 'newer than 7 days'.

How to eliminate wrong answers

Option B is wrong because Customer Insights supports defining relationships between tables (e.g., via keys like CustomerID) when creating segments, and the segment condition explicitly references matching CustomerID and ProductID, which implies a relationship can be defined. Option C is wrong because Customer Insights segments do support `NOT EXISTS` logic through the 'does not have' or 'exclude' conditions in the segment builder, so the clause itself is valid. Option D is wrong because the question states the data is ingested correctly, and the segment returns no members, which is a logic issue, not a data issue; if the Purchase table lacked data, the segment would likely return all customers with cart additions, not zero.

Practice this question →

155

Matchingmedium

Match each Dynamics 365 deployment option to its description.

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

Concepts

Matches

Microsoft-hosted, subscription-based, always up-to-date

Customer-managed servers and infrastructure, older version

Mix of cloud and on-premises components

Dynamics 365 deployed and managed by a third-party partner

Free, time-limited environment for evaluation purposes

Why these pairings

Dynamics 365 offers three main deployment options: Online (cloud, managed by Microsoft), On-premises (locally managed), and Hybrid (combination). Common mistakes include swapping the definitions of Online and On-premises, or misrepresenting Hybrid as purely cloud.

Practice this question →

156

MCQmedium

A company has multiple source systems with different customer IDs. They want to create a unified customer profile that links these IDs. Which entity in Customer Insights represents the unified customer?

A.Customer entity

B.Unified Activity entity

C.Contact entity

D.Profile entity

AnswerA

Correct: The Customer entity holds the unified customer profile after matching and merging.

Why this answer

The Customer entity in Dynamics 365 Customer Insights is the unified profile that merges records from multiple source systems using different customer IDs. It is the result of the data unification process, which matches and merges duplicate records into a single, comprehensive view of each customer. This entity is specifically designed to represent the unified customer profile, making it the correct answer.

Exam trap

The trap here is that candidates confuse the 'Customer entity' with the 'Contact entity' or 'Profile entity', not realizing that Customer Insights specifically uses the term 'Customer entity' for the unified profile after data unification.

How to eliminate wrong answers

Option B (Unified Activity entity) is wrong because it represents a consolidated view of activities (e.g., purchases, support cases) across sources, not the customer profile itself. Option C (Contact entity) is wrong because it is a standard Dynamics 365 entity for individual contacts, not a unified profile that merges IDs from multiple source systems. Option D (Profile entity) is wrong because while 'profile' is a general term, the specific entity in Customer Insights for the unified customer is named 'Customer entity', not 'Profile entity'.

Practice this question →

157

MCQmedium

A marketing manager wants to use AI to generate personalized content for email campaigns based on customer preferences. Which feature in Customer Insights should they use?

A.Predictions

B.Segmentation

C.Copilot

D.Measures

AnswerC

Correct: Copilot uses AI to generate personalized content and insights.

Why this answer

Copilot in Dynamics 365 Customer Insights uses generative AI to create personalized content, such as email copy, based on customer preferences and data. It directly addresses the marketing manager's need to generate tailored content without manual effort, leveraging natural language prompts and customer insights.

Exam trap

The trap here is that candidates may confuse Segmentation (defining the audience) with content generation, but Copilot is the only feature that actively creates personalized content using AI.

How to eliminate wrong answers

Option A is wrong because Predictions in Customer Insights are used for forecasting outcomes (e.g., churn or purchase likelihood) using machine learning models, not for generating personalized content. Option B is wrong because Segmentation groups customers into segments based on criteria (e.g., demographics or behaviors) but does not create or generate content; it defines the audience. Option D is wrong because Measures are used to define and calculate KPIs or metrics (e.g., total revenue or average order value) from customer data, not for content generation.

Practice this question →

158

MCQmedium

A company has configured a data unification rule as shown in the exhibit. After running the process, they find that customers with the same email but different phone numbers are not being merged. What is the most likely reason?

A.Deduplication is not enabled for the rule

B.The fuzzy match on Phone is overriding the exact match on Email

C.The Email field values contain slight differences like leading/trailing spaces

D.The output entity is not correctly configured

AnswerC

Exact match requires identical values; spaces or case differences can prevent matching.

Why this answer

Leading or trailing spaces in the Email field cause exact match comparisons to fail, even though the values appear identical visually. Customer Insights data unification rules use exact matching by default unless fuzzy matching is explicitly configured, so any whitespace discrepancy prevents the rule from recognizing duplicate records. Trimming or normalizing the Email field before matching would resolve this issue.

Exam trap

The trap here is that candidates assume 'exact match' means visually identical, but Microsoft tests the nuance that exact matching in Customer Insights is literal byte-level comparison, so invisible characters like spaces break the match.

How to eliminate wrong answers

Option A is wrong because deduplication is inherently part of the data unification process in Customer Insights; there is no separate 'enable deduplication' toggle for a rule—the rule itself performs deduplication based on the match conditions. Option B is wrong because fuzzy match on Phone does not override exact match on Email; the rule evaluates each match condition independently and merges records only when all specified conditions are satisfied. Option D is wrong because the output entity configuration affects where results are stored, not whether matching logic succeeds or fails.

Practice this question →

159

MCQeasy

A company wants to combine data from Microsoft 365, Dynamics 365, and their custom app into one customer data platform. Which Dynamics 365 Customer Insights capability enables this?

A.Measures

B.Data ingestion and unification

C.Customer segments

D.Prediction models

AnswerB

Data ingestion and unification enables connecting to and combining data from multiple sources (e.g., Microsoft 365, Dynamics 365, custom apps) into a unified customer data platform.

Why this answer

Data ingestion and unification (Option B) is the correct capability for combining data from Microsoft 365, Dynamics 365, and custom apps into a single customer data platform. This feature connects to various data sources, ingests the data, and unifies it into a unified customer profile. Option A (Measures) is for defining KPIs and metrics, not for data combination.

Option C (Customer segments) is for creating groups of customers after data is unified. Option D (Prediction models) uses unified data to predict outcomes, not to combine data sources.

Practice this question →

160

MCQhard

Refer to the exhibit. A Customer Insights analyst defines a measure for Customer Lifetime Value. What is the result of this measure definition?

A.The total transaction amount since 2025

B.The maximum transaction amount

C.The count of transactions after 2025

D.The average transaction amount

AnswerA

The sum of transaction_amount filtered for dates >= 2025-01-01.

Why this answer

The measure definition is configured to sum the Transaction Amount field, which calculates the total monetary value of all transactions. The filter restricts the calculation to transactions occurring on or after January 1, 2025, so the result is the total transaction amount since 2025. This aligns with the standard Customer Insights measure behavior where aggregation functions like Sum are applied to numeric attributes.

Exam trap

The trap here is that candidates may confuse the Sum aggregation with Count or Average, especially when the measure is named 'Customer Lifetime Value,' which often implies a cumulative total, but the filter date can mislead test-takers into thinking it's a count or average.

How to eliminate wrong answers

Option B is wrong because the measure uses the Sum aggregation, not Max, so it calculates the total, not the maximum transaction amount. Option C is wrong because the measure sums transaction amounts, not counts transactions; a Count aggregation would be required for that result. Option D is wrong because the measure uses Sum, not Average; an Average aggregation would divide the sum by the number of transactions.

Practice this question →

161

MCQhard

A company wants to use Dynamics 365 Customer Insights to personalize website content in real time based on customer behavior. Which feature should they implement?

A.Customer segments

B.Data unification

C.Real-time marketing and personalization

D.Measures

AnswerC

This feature enables real-time triggers and personalized content delivery.

Why this answer

Dynamics 365 Customer Insights includes a real-time marketing and personalization feature that uses customer behavior data (e.g., clicks, page views, purchases) to dynamically tailor website content. This capability leverages the Customer Data Platform (CDP) to trigger personalized experiences in milliseconds, meeting the requirement for real-time adaptation based on live customer actions.

Exam trap

The trap here is that candidates confuse the foundational data management features (segments, unification, measures) with the execution layer required for real-time personalization, leading them to pick a correct-sounding but non-functional option like customer segments.

How to eliminate wrong answers

Option A is wrong because customer segments are static groupings of customers based on shared attributes or behaviors; they do not inherently personalize content in real time—they require an additional personalization engine to act on the segments. Option B is wrong because data unification is the process of merging and deduplicating customer records from multiple sources to create a single customer view; it is a foundational step but does not itself deliver real-time personalization on a website. Option D is wrong because measures are aggregated metrics (e.g., average order value, churn rate) used for analytics and reporting; they do not directly control or trigger personalized content delivery.

Practice this question →

162

MCQmedium

A company uses Dynamics 365 Customer Insights - Data and wants to enrich customer profiles with demographic data from a third-party provider. Which feature should they use?

A.Enrichments

B.Data sources

C.Segments

D.Measures

AnswerA

Enrichments allow you to add data from third-party providers to customer profiles.

Why this answer

Enrichments in Dynamics 365 Customer Insights - Data allow you to augment existing customer profiles with additional data from third-party providers, such as demographic, firmographic, or interest data. This feature directly supports the goal of enriching profiles with external demographic information by matching customer identifiers against the provider's data and appending the results.

Exam trap

The trap here is that candidates confuse 'enrichments' with 'data sources,' thinking that adding a new data source from a third party is the same as enriching existing profiles, but enrichments specifically augment existing unified profiles rather than importing new raw tables.

How to eliminate wrong answers

Option B (Data sources) is wrong because data sources are used to ingest and connect raw data (e.g., from CRM, ERP, or transactional systems) into Customer Insights, not to enrich existing profiles with third-party demographic data. Option C (Segments) is wrong because segments are dynamic or static groupings of customer profiles based on defined criteria, used for targeting and analysis, not for importing external demographic attributes. Option D (Measures) is wrong because measures are calculated metrics (e.g., KPIs, aggregates) derived from your data, such as average purchase value, and have no role in pulling in external demographic enrichment data.

Practice this question →

163

MCQeasy

A company wants to use Customer Insights to enrich customer profiles with external demographic data. Which feature should they use to bring in this external data?

A.Data sources

B.Relationships

C.Measures

D.Predictions

AnswerA

Data sources allow importing external data.

Why this answer

To enrich customer profiles with external demographic data in Dynamics 365 Customer Insights, you use the 'Data sources' feature. This allows you to connect to and ingest data from external systems, such as third-party demographic providers, by configuring a new data source (e.g., via Power Query connectors). The ingested data is then unified into the customer profile, enabling enrichment without needing custom code.

Exam trap

The trap here is that candidates confuse 'Data sources' (ingestion) with 'Relationships' (data modeling), thinking that linking external data requires defining relationships rather than importing the data first.

How to eliminate wrong answers

Option B is wrong because 'Relationships' define how different entities (e.g., Customer and Order) are linked within the data model, not how external data is brought in. Option C is wrong because 'Measures' are used to create calculated KPIs or aggregations from existing data, not to import new external datasets. Option D is wrong because 'Predictions' leverage existing data to generate predictive models (e.g., churn or next purchase), not to ingest external demographic data for enrichment.

Practice this question →

164

MCQhard

A Customer Insights administrator receives an error when trying to ingest a CSV file from Azure Blob Storage. The error message says 'Access denied'. What is the most likely cause?

A.The connection string or SAS token is invalid or expired

B.The CSV format is incompatible

C.The CSV file is too large

D.The schema does not match the mapping

AnswerA

Invalid credentials lead to access denied.

Why this answer

The 'Access denied' error when ingesting a CSV file from Azure Blob Storage into Dynamics 365 Customer Insights indicates that the service cannot authenticate to the storage resource. The most common cause is an invalid or expired connection string or Shared Access Signature (SAS) token, as these credentials are required for secure access to Azure Blob Storage. Without valid credentials, Customer Insights cannot read the file, regardless of its format, size, or schema.

Exam trap

The trap here is that candidates may confuse an authentication error with data-related issues (format, size, schema) because they focus on the CSV file itself rather than the access mechanism to the storage location.

How to eliminate wrong answers

Option B is wrong because an incompatible CSV format would typically result in a parsing or data type error, not an 'Access denied' authentication error. Option C is wrong because file size limitations would produce a quota or timeout error, not an access permission error. Option D is wrong because a schema mismatch would cause a mapping or ingestion failure after the file is successfully read, not an access denial during the initial connection.

Practice this question →

165

MCQhard

A company uses Dynamics 365 Customer Insights - Data to create a unified customer profile. They notice that duplicate records exist from different sources. What should they do to resolve this?

A.Manually delete duplicate records in each source system

B.Create a dataflow to filter duplicates

C.Use Power Automate to remove duplicates

D.Configure deduplication rules within Customer Insights

AnswerD

Customer Insights has built-in deduplication to match and merge duplicates.

Why this answer

D is correct because Dynamics 365 Customer Insights - Data provides built-in deduplication rules that allow you to define matching criteria (e.g., name, email, phone) to identify and merge duplicate records from different sources into a single unified customer profile. This is the intended, native mechanism for resolving duplicates within the system, ensuring data integrity without manual intervention or external tools.

Exam trap

The trap here is that candidates may think deduplication requires external tools like Power Automate or manual cleanup, but the exam expects you to know that Customer Insights has native deduplication capabilities as part of its data unification process.

How to eliminate wrong answers

Option A is wrong because manually deleting duplicates in each source system is inefficient, error-prone, and does not address duplicates that are created during the unification process within Customer Insights itself. Option B is wrong because dataflows in Customer Insights are used for ingesting and transforming data, not for deduplication; filtering duplicates in a dataflow would not resolve matching across multiple sources or merge profiles. Option C is wrong because Power Automate is an automation tool for workflows and notifications, not designed for complex deduplication logic or merging unified customer profiles within Customer Insights.

Practice this question →

166

Multi-Selectmedium

Which TWO data sources can be used to ingest data into Dynamics 365 Customer Insights? (Choose two.)

Select 2 answers

A.Power Query

B.Azure DevOps

C.Excel file

D.Microsoft Dataverse

E.Microsoft Teams

AnswersA, D

Power Query connects to many sources.

Why this answer

Power Query is a native data ingestion tool within Dynamics 365 Customer Insights that allows users to connect to a wide variety of data sources, transform data using a graphical interface, and load it into the Customer Insights data lake. It supports connectors for databases, online services, and files, making it a primary method for importing customer data.

Exam trap

The trap here is that candidates often mistake Excel files as a direct data source option, but in Customer Insights, Excel files are ingested through Power Query or other connectors, not as a standalone selection in the exam's context.

Practice this question →

167

MCQmedium

A marketing manager wants to automatically send a personalized discount offer to customers who have a high propensity to churn. Which combination of Customer Insights capabilities should they use?

A.Predictive scoring and measures

B.Data unification and enrichment

C.Enrichment and Copilot

D.Segmentation and AI suggestions

AnswerA

Predictive scoring models churn propensity; measures can trigger actions like sending a discount offer.

Why this answer

Predictive scoring in Customer Insights uses machine learning models to calculate a churn probability score for each customer, identifying those with a high propensity to churn. Measures allow the marketing manager to define and compute key business metrics, such as customer lifetime value or churn risk thresholds, which can trigger automated actions like sending personalized discount offers. Together, they enable a data-driven, automated outreach to at-risk customers without manual intervention.

Exam trap

The trap here is that candidates often confuse 'segmentation and AI suggestions' (Option D) with predictive scoring, but segmentation alone cannot predict churn propensity—it only groups customers based on static criteria, whereas predictive scoring uses machine learning to dynamically assess risk.

How to eliminate wrong answers

Option B is wrong because data unification and enrichment focus on merging and enhancing customer data from multiple sources (e.g., CRM, transactional systems) to create a single customer view, but they do not include predictive scoring or automated action triggers for churn-based offers. Option C is wrong because enrichment and Copilot involve augmenting customer profiles with external data (e.g., demographic or firmographic data) and using AI-powered conversational assistance, not predictive churn scoring or automated discount sending. Option D is wrong because segmentation and AI suggestions allow grouping customers into segments and receiving AI-recommended actions, but they lack the predictive scoring capability to specifically identify high-propensity churn customers and the measures to define and execute the automated discount offer logic.

Practice this question →

168

MCQeasy

A marketing team wants to send personalized emails based on customer lifetime value (CLV) calculated in Dynamics 365 Customer Insights. Which Customer Insights capability should they use to define CLV?

A.Activities

B.Segments

C.Relationships

D.Measures

AnswerD

Measures allow you to define calculated KPIs such as CLV.

Why this answer

Measures in Dynamics 365 Customer Insights allow you to define and calculate key performance indicators (KPIs) like customer lifetime value (CLV) using predefined or custom formulas. This capability aggregates customer data (e.g., purchase history, frequency, monetary value) to produce a numeric metric that can be used for personalization. Activities, Segments, and Relationships do not perform such calculations.

Exam trap

The trap here is confusing Segments (which filter customers based on a condition) with Measures (which calculate the numeric value that the condition uses), leading candidates to pick Segments when they need to define the underlying metric first.

How to eliminate wrong answers

Option A is wrong because Activities track interactions (e.g., purchases, web visits) but do not compute aggregated metrics like CLV. Option B is wrong because Segments group customers based on conditions (e.g., CLV > $500) but cannot define or calculate the CLV value itself. Option C is wrong because Relationships define how tables (e.g., Customer and Order) are linked for data modeling, not for calculating numeric KPIs.

Practice this question →

169

MCQeasy

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

A.Connections

B.Customer Data Platform (CDP) capabilities

C.Predictions

D.Segmentation

AnswerB

CDP unifies data from disparate sources.

Why this answer

Dynamics 365 Customer Insights is a Customer Data Platform (CDP) that ingests, unifies, and resolves customer data from multiple sources—such as e-commerce platforms, POS systems, and loyalty programs—into a single, unified customer profile. This capability is specifically designed to create a 360-degree view of each customer by matching and merging records across disparate data sources.

Exam trap

The trap here is that candidates often confuse 'Connections' (data source setup) with the actual CDP unification capability, or they think 'Segmentation' is the primary tool for creating a single view, when in fact segmentation occurs after unification.

How to eliminate wrong answers

Option A is wrong because Connections in Dynamics 365 Customer Insights refer to the configuration of data sources and integrations, not the core capability of unifying data into a single customer view. Option C is wrong because Predictions is a feature that uses AI to forecast customer behaviors (e.g., churn or next purchase), not to unify or merge data from different systems. Option D is wrong because Segmentation is the process of grouping customers based on attributes or behaviors after unification, not the capability that performs the actual data unification.

Practice this question →

170

MCQmedium

A company uses Dynamics 365 Customer Insights to drive personalized marketing campaigns. They want to use AI to predict which customers are likely to purchase a new product line. Which capability should they use?

A.Enrich profiles with demographic data from third-party sources

B.Use the built-in prediction models for purchase intention

C.Ingest data from the new product's website analytics

D.Create a segment based on past purchases

AnswerB

Prediction models can forecast purchase likelihood.

Why this answer

Dynamics 365 Customer Insights includes prebuilt AI prediction models that can analyze historical customer data and behavioral patterns to forecast purchase intention. This capability directly addresses the requirement to predict which customers are likely to purchase a new product line without needing custom machine learning development.

Exam trap

The trap here is that candidates often confuse static segmentation (Option D) with AI-driven prediction, not realizing that predictive models in Customer Insights are purpose-built for forecasting future behaviors like purchase intention.

How to eliminate wrong answers

Option A is wrong because enriching profiles with demographic data from third-party sources enhances customer profiles but does not provide predictive analytics for purchase intention. Option C is wrong because ingesting data from the new product's website analytics captures raw behavioral data but lacks the built-in AI model to generate purchase predictions. Option D is wrong because creating a segment based on past purchases is a static, rule-based grouping that does not use AI to predict future purchase likelihood for a new product line.

Practice this question →

171

MCQhard

A marketing team notices that a segment based on 'high-value customers' returns fewer records than expected. The segment criteria include 'Total Purchase Amount > $500' and 'Last Purchase Date within 90 days'. The data source is updated nightly. What is the most likely cause?

A.The segment was not refreshed after data update

B.The data source credentials are expired

C.The segment includes too many conditions

D.The customer profiles are not unified

AnswerA

Segments need to be refreshed manually or on schedule; incremental refresh might not reflect latest data.

Why this answer

The segment criteria are evaluated against the data at the time the segment is created or last refreshed. Since the data source updates nightly, the segment must be manually or automatically refreshed to incorporate the new data. If the segment was not refreshed after the nightly update, it would still reflect the older, smaller dataset, resulting in fewer records than expected.

Exam trap

The trap here is that candidates may assume the segment automatically reflects the latest data, but in Customer Insights, segments are static snapshots until explicitly refreshed, and the exam tests this distinction between data ingestion and segment computation.

How to eliminate wrong answers

Option B is wrong because expired data source credentials would cause a data refresh failure, not a segment returning fewer records than expected; the segment would either fail to load or show no data. Option C is wrong because the segment includes only two conditions, which is not excessive; too many conditions could reduce the result set, but the question states the criteria are correct and the issue is the number of records, not the logic. Option D is wrong because ununified customer profiles would affect the accuracy of customer identity matching, not the count of records returned by a segment based on purchase data; the segment criteria are based on purchase attributes, not profile unification.

Practice this question →

172

MCQeasy

A company wants to use Customer Insights to send a birthday discount email to customers whose birthday is today. What should they create?

A.A measure

B.A dynamic segment with a date condition

C.A static segment

D.An enrichment

AnswerB

Dynamic segments recalculate on schedule.

Why this answer

A dynamic segment with a date condition is the correct approach because it automatically evaluates customer data each time the segment runs, selecting only those whose birthday matches today's date. This ensures the email is sent to the correct recipients on the specific day without manual intervention, leveraging Customer Insights' real-time data refresh capabilities.

Exam trap

The trap here is that candidates often confuse a dynamic segment with a static segment, thinking a one-time list is sufficient, but the exam tests the understanding that only a dynamic segment can automatically evaluate a date condition like 'birthday is today' on a recurring basis.

How to eliminate wrong answers

Option A is wrong because a measure is used to aggregate and calculate metrics (e.g., average spend) but cannot trigger or define a segment for sending emails. Option C is wrong because a static segment contains a fixed list of customers that does not update automatically, so it would not reflect today's birthday condition without manual re-creation. Option D is wrong because an enrichment enhances customer profiles with external data (e.g., demographic data from a third-party service) but does not create a condition-based segment for targeting.

Practice this question →

173

MCQeasy

A marketing manager wants to view a 360-degree view of a specific customer in Dynamics 365 Customer Insights. Which entity should they look at?

A.Customer profile

B.Activity

C.Segment

D.Measure

AnswerA

The unified customer profile shows all data about a customer.

Why this answer

The customer profile entity in Dynamics 365 Customer Insights is the unified, 360-degree view of a customer, aggregating data from multiple sources into a single record. It provides a comprehensive view of customer attributes, interactions, and relationships, enabling the marketing manager to see all relevant information in one place.

Exam trap

The trap here is that candidates confuse 'customer profile' with 'activity' because activities are often the most visible data in Dynamics 365, but the profile is the aggregate entity that provides the 360-degree view.

How to eliminate wrong answers

Option B is wrong because an activity represents a specific interaction or event (e.g., a purchase, email click) rather than the holistic customer view. Option C is wrong because a segment is a group of customers defined by a set of rules, not the individual customer's unified profile. Option D is wrong because a measure is a calculated metric (e.g., average spend) applied to profiles or segments, not the customer's 360-degree view.

Practice this question →

174

MCQeasy

A company wants to provide customer service agents with a 360-degree view of customers, including purchase history and support interactions. Which Dynamics 365 application can consume Customer Insights unified profiles?

A.Dynamics 365 Human Resources

B.Dynamics 365 Customer Service

C.Dynamics 365 Finance

D.Dynamics 365 Project Operations

AnswerB

Correct: Customer Service can display the unified customer profile from Customer Insights.

Why this answer

Dynamics 365 Customer Service can consume Customer Insights unified profiles to provide agents with a 360-degree view of customers, including purchase history and support interactions. This integration enriches the service experience by surfacing unified customer data directly within the agent interface, enabling personalized and context-aware support.

Exam trap

The trap here is that candidates may confuse the purpose of Dynamics 365 applications, assuming any app with customer data (like Finance) can provide a 360-degree view, but only Customer Service is designed to consume unified profiles for agent-facing support scenarios.

How to eliminate wrong answers

Option A is wrong because Dynamics 365 Human Resources is designed for HR operations like employee management and payroll, not for consuming customer unified profiles to support customer service scenarios. Option C is wrong because Dynamics 365 Finance focuses on financial management and accounting, lacking the customer service agent interface needed to leverage Customer Insights unified profiles for support interactions. Option D is wrong because Dynamics 365 Project Operations is built for project-based resource and cost management, not for providing a 360-degree customer view in a service agent context.

Practice this question →

175

MCQeasy

You are a consultant for a small e-commerce company that is new to Dynamics 365 Customer Insights. They have data in a CSV file containing customer names, email addresses, and purchase amounts. They want to create a segment of customers who have spent more than $500 in total. What is the first step they should take?

A.Define data unification rules.

B.Create a segment based on total spend.

C.Enrich profiles with demographic data.

D.Upload the CSV file as a data source.

AnswerD

First step is to ingest data.

Why this answer

Before any segmentation or data transformation can occur, the CSV data must first be ingested into Dynamics 365 Customer Insights. Uploading the CSV file as a data source is the foundational step because the system requires raw data to be available before it can be unified, enriched, or used to create segments. Without this initial import, all subsequent operations (unification, segmentation, enrichment) would have no data to act upon.

Exam trap

The trap here is that candidates may assume segmentation can be performed directly on raw imported data, overlooking the prerequisite that the data must first be ingested and made available as a data source before any transformation or segmentation logic can be applied.

How to eliminate wrong answers

Option A is wrong because data unification rules are applied after data is ingested, to merge and deduplicate records from multiple sources; they cannot be defined without first having the data in the system. Option B is wrong because a segment based on total spend cannot be created until the purchase data is imported and the necessary calculations (e.g., aggregating purchase amounts per customer) are performed on the ingested data. Option C is wrong because enriching profiles with demographic data is an advanced step that requires existing profiles built from imported data; it is not the first action when starting with a raw CSV file.

Practice this question →

176

MCQhard

A marketing team wants to send personalized email campaigns based on customer lifetime value (CLV) scores. They have already built a CLV prediction model in Customer Insights. What is the next step to use these scores in a marketing campaign?

A.Create a segment based on the CLV prediction in Customer Insights

B.Use the prediction directly in a Marketing journey

C.Use Power BI to visualize the CLV scores

D.Export the CLV scores to Excel and import into Dynamics 365 Marketing

AnswerA

Correct: Creating a segment from the prediction allows you to target customers in Marketing.

Why this answer

In Dynamics 365 Customer Insights, predictions like CLV are stored as data entities. To use them in a marketing campaign, you must first create a segment that filters customers based on the CLV prediction score. This segment can then be exported or used directly in Dynamics 365 Marketing journeys.

Option A is correct because segments are the bridge between Customer Insights data and Marketing campaign targeting.

Exam trap

The trap here is that candidates assume predictions can be used directly in journeys (Option B) because they see 'AI' and 'Marketing' together, but Microsoft requires an explicit segmentation step to ensure data governance and performance.

How to eliminate wrong answers

Option B is wrong because predictions cannot be referenced directly in a Marketing journey; they must be materialized into a segment first. Option C is wrong because Power BI is a visualization tool, not a mechanism to activate data for marketing campaigns. Option D is wrong because exporting to Excel and reimporting is unnecessary and error-prone; Customer Insights integrates natively with Dynamics 365 Marketing without manual data movement.

Practice this question →

177

Multi-Selectmedium

A company uses Dynamics 365 Customer Insights - Data to manage customer data. Which TWO features are part of Customer Insights - Data? (Select TWO.)

Select 2 answers

A.Event management

B.Data unification

C.Email marketing

D.Measures

E.Journey orchestration

AnswersB, D

Data unification is a core feature of Customer Insights - Data.

Why this answer

Data unification is a core feature of Dynamics 365 Customer Insights - Data that allows you to ingest data from multiple sources, map fields, and merge duplicate records into a single, unified customer profile. This process uses matching rules and deduplication logic to create a 360-degree view of each customer, which is essential for downstream analytics and segmentation.

Exam trap

The trap here is that candidates confuse the 'Data' and 'Journeys' modules, incorrectly assuming features like email marketing or journey orchestration are part of Customer Insights - Data when they actually belong to Customer Insights - Journeys.

Practice this question →

178

Multi-Selecthard

A global enterprise wants to use Dynamics 365 Customer Insights to create a 360-degree customer view. They have data from Dynamics 365 Sales, Dynamics 365 Customer Service, and external loyalty systems. They also need to comply with GDPR and CCPA. Which THREE capabilities should they prioritize?

Select 3 answers

A.Use AI to create predictive segments and measure customer lifetime value

B.Provide real-time chat support to customers

C.Automate LinkedIn lead generation campaigns

D.Ingest data from Dynamics 365, external systems, and third-party data sources

E.Apply built-in compliance with data privacy regulations like GDPR and CCPA

AnswersA, D, E

Correct: AI-driven segmentation and CLV are key.

Why this answer

A is correct because Dynamics 365 Customer Insights uses AI to build predictive segments (e.g., churn risk) and calculate customer lifetime value (CLV) using historical and behavioral data. This directly supports the goal of a 360-degree customer view by enriching unified profiles with forward-looking insights.

Exam trap

The trap here is confusing Customer Insights' data unification and compliance features with unrelated Dynamics 365 modules like Customer Service chat or Sales lead automation, leading candidates to select options that are valid in other contexts but not core to Customer Insights.

Practice this question →

179

Multi-Selectmedium

Which TWO of the following are valid data source types in Dynamics 365 Customer Insights?

Select 2 answers

A.Oracle Database

B.Microsoft Excel

C.Azure SQL Database

D.Salesforce

E.Adobe Analytics

AnswersB, C

Excel is a supported data source.

Why this answer

Microsoft Excel is a valid data source type in Dynamics 365 Customer Insights because it supports importing data from flat files, including .xlsx and .csv formats, via the ingestion pipeline. This allows users to bring in customer data from spreadsheets for unification and segmentation without requiring a database connection.

Exam trap

The trap here is that candidates often confuse 'valid data source types' with 'integration possibilities'—just because a system can be connected via Power Query or custom code does not mean it is a native, built-in data source type in Customer Insights.

Practice this question →

180

MCQmedium

An administrator is configuring a data source in Dynamics 365 Customer Insights using the provided JSON. What is the purpose of this configuration?

A.To run a prediction model

B.To ingest data from Dynamics 365

C.To create a customer segment

D.To calculate a measure

AnswerB

The data source is set to Dynamics365.

Why this answer

The JSON configuration defines a data source connection to Dynamics 365, specifying the entity and field mappings required to ingest data into Customer Insights. This is the foundational step for bringing customer data into the system for unification, enrichment, and analysis.

Exam trap

The trap here is that candidates confuse the initial data ingestion step with downstream activities like segmentation or prediction, not recognizing that the JSON's purpose is solely to define where and how data enters the system.

How to eliminate wrong answers

Option A is wrong because running a prediction model requires configuring a prediction schema and training data, not a data source connection. Option C is wrong because creating a customer segment is done after data ingestion and unification, using the unified customer profile, not during data source setup. Option D is wrong because calculating a measure involves defining KPIs based on existing data, not configuring the source of that data.

Practice this question →

181

MCQhard

A retail company uses Dynamics 365 Customer Insights - Data. They have multiple data sources: online transactions, loyalty program, and social media. They need to create a unified customer profile that resolves identities across these sources. Which process in Customer Insights should they configure to achieve this?

A.Data unification

B.Measures

C.Data transformation

D.Enrichment

AnswerA

Data unification performs identity resolution and merges records into a unified profile.

Why this answer

Data unification in Dynamics 365 Customer Insights - Data is the process that matches and merges customer records from multiple data sources (online transactions, loyalty program, social media) into a single, unified customer profile. It resolves identity conflicts by using matching rules and deduplication to link records belonging to the same individual across disparate systems, enabling a 360-degree view of the customer.

Exam trap

The trap here is that candidates often confuse 'Data transformation' (a preparatory step for cleaning data) with 'Data unification' (the actual identity resolution process), leading them to select transformation when unification is the correct answer.

How to eliminate wrong answers

Option B (Measures) is wrong because Measures are used to define KPIs and calculated metrics (e.g., total spend, churn risk) on top of unified data, not to resolve identities or merge profiles. Option C (Data transformation) is wrong because Data transformation refers to cleaning, mapping, or reshaping raw data (e.g., changing data types, merging columns) before unification, but it does not perform identity resolution or profile merging. Option D (Enrichment) is wrong because Enrichment adds external data (e.g., demographic or firmographic data) to existing profiles after unification, but it does not reconcile identities from different sources.

Practice this question →

182

MCQmedium

A marketing manager notices that the customer churn prediction model in Dynamics 365 Customer Insights is not updating with new data. What is the most likely cause?

A.The segment is not refreshed

B.The measure is not calculated

C.The data source connection is lost

D.The prediction model is not scheduled to refresh

AnswerD

Models need a defined schedule to retrain with new data.

Why this answer

In Dynamics 365 Customer Insights, prediction models are machine learning models that must be explicitly scheduled to refresh on a recurring basis. If the model is not scheduled to refresh, it will not automatically ingest new data, causing the churn predictions to become stale. Option D correctly identifies this as the most likely cause because the model's refresh schedule controls when it re-trains or updates with fresh data.

Exam trap

The trap here is that candidates confuse the refresh of a segment or measure with the refresh of a prediction model, assuming all data artifacts update automatically, when in fact prediction models require an explicit schedule to retrain or re-score with new data.

How to eliminate wrong answers

Option A is wrong because a segment refresh controls which customer records belong to a segment, not the underlying prediction model's data ingestion or retraining. Option B is wrong because a measure is a calculated metric (e.g., average purchase value) and does not control the refresh of a prediction model; measures refresh independently. Option C is wrong because a lost data source connection would typically generate an explicit error or warning in the system, not simply cause the model to stop updating silently; the question states the model is 'not updating,' which points to a scheduling issue rather than a connectivity failure.

Practice this question →

183

MCQmedium

A company uses Dynamics 365 Customer Insights - Journeys to send email campaigns. They want to trigger a journey when a customer's predicted churn score exceeds 0.8. Which source should they use to trigger the journey?

A.Manual trigger

B.Event registration

C.Segment membership

D.Marketing form submission

AnswerC

A segment of customers with churn score >0.8 can be used as a trigger in journeys.

Why this answer

In Dynamics 365 Customer Insights - Journeys, a segment membership trigger starts a journey when a customer enters or leaves a defined segment. Since the predicted churn score is a calculated attribute that can be used to define a segment (e.g., customers with churn score > 0.8), the journey can be triggered by membership in that segment. This allows the system to react automatically to real-time customer insights without manual intervention.

Exam trap

The trap here is that candidates may confuse 'segment membership' with other trigger types like 'event registration' or 'form submission', not realizing that predictive scores are best handled by creating a segment based on the score threshold and then using that segment as the journey trigger.

How to eliminate wrong answers

Option A is wrong because a manual trigger requires a human to initiate the journey, which is not suitable for an automated, condition-based trigger like a churn score threshold. Option B is wrong because event registration triggers are designed for live or virtual events (e.g., webinars, conferences) and do not evaluate customer attributes or scores. Option D is wrong because marketing form submission triggers only when a customer submits a specific form, not based on predictive scores or segment membership.

Practice this question →

184

MCQmedium

You are a data analyst for a financial services company that uses Dynamics 365 Customer Insights. The company has unified customer profiles and wants to use AI to predict which customers are likely to respond to a new credit card offer. They have historical data on previous offers, customer demographics, and transaction history. You have been asked to create a predictive model. After configuring the model, you notice that the model's accuracy is very low. You suspect that the data used for training is not representative. What is the most likely cause?

A.The historical data has a low response rate, creating class imbalance.

B.The data unification process merged records incorrectly.

C.The training data includes data from too many time periods.

D.The data source connection to the transactional system is failing.

AnswerA

Imbalanced data reduces model accuracy.

Why this answer

The historical data may not include enough examples of customers who responded, leading to imbalanced data. Option B is wrong because missing data can be handled, but imbalance is more critical. Option C is wrong because the model can handle different time periods.

Option D is wrong because the data source configuration is probably correct.

Practice this question →

185

MCQhard

An administrator notices that Customer Insights data is not refreshing as scheduled. What should they check first?

A.Data source refresh settings

B.Unification rules

C.Enrichment providers

D.Segment definitions

AnswerA

The refresh schedule for each data source must be correctly configured.

Why this answer

Data source refresh settings are the most common cause of refresh issues. Verifying the data source refresh settings is the first step in troubleshooting because if the refresh schedule is not configured correctly or the data source connection is broken, the data will not refresh. Option A is correct as it directly addresses the refresh schedule.

Practice this question →

186

MCQeasy

A business analyst needs to share a view of unified customer profiles from Dynamics 365 Customer Insights with the sales team. Which method should they use?

A.Embed Customer Insights in Dynamics 365 Sales

B.Set up a Power Automate flow

C.Create a Power BI report

D.Export the unified customer entity to Dataverse

AnswerD

Makes profiles available in Dynamics 365 apps.

Why this answer

Exporting the unified customer entity to Dataverse makes the unified profile data available as a standard Dataverse table, which can then be shared with the sales team through Dynamics 365 Sales or any other Dataverse-connected app. This method directly provides the sales team with access to the unified customer profiles without requiring additional integration or reporting layers.

Exam trap

The trap here is that candidates often confuse 'sharing a view' with 'embedding' or 'visualizing,' leading them to choose Power BI or embedding options, when the correct method is to export the data to a shared data source like Dataverse.

How to eliminate wrong answers

Option A is wrong because embedding Customer Insights in Dynamics 365 Sales is a feature for displaying insights within the Sales app, but it does not inherently share a specific view of unified customer profiles with the entire sales team; it requires the user to have appropriate licenses and permissions. Option B is wrong because setting up a Power Automate flow is used for automating workflows and notifications, not for sharing a static view of unified customer profiles; it would be an overly complex and indirect method for this purpose. Option C is wrong because creating a Power BI report is for visualizing and analyzing data, but it does not directly share the underlying unified customer entity with the sales team; it would require additional steps to export data and manage access.

Practice this question →

187

MCQmedium

A customer administrator configures the unification shown. After running unification, they notice that some records from the Web_Submissions source have empty email fields. What will happen to those records?

A.They will cause an error and stop unification

B.They will match to CRM contacts with empty email

C.They will remain as unmatched profiles

D.They will be deleted from the data source

AnswerC

No match possible, so they stay separate.

Why this answer

In Dynamics 365 Customer Insights, when a unification rule is configured and a record from a source (e.g., Web_Submissions) has an empty email field, that record cannot be matched to any existing customer profile based on the email attribute. Instead of causing an error or being deleted, the record is retained as an unmatched profile. Unmatched profiles are stored separately and can be reviewed, merged, or acted upon later, ensuring no data loss occurs during the unification process.

Exam trap

The trap here is that candidates often assume empty fields cause errors or are ignored entirely, but Microsoft tests the specific behavior that empty match attributes result in unmatched profiles rather than failures or deletions.

How to eliminate wrong answers

Option A is wrong because empty email fields do not cause an error or stop unification; Customer Insights gracefully handles missing data by treating such records as unmatched. Option B is wrong because matching requires non-empty, identical values in the selected match attributes (e.g., email); records with empty email fields cannot match to CRM contacts that also have empty email, as the system does not match on null or blank values. Option D is wrong because records are never deleted from the data source during unification; they remain in the source table and are only excluded from the unified customer profile if they fail to match.

Practice this question →

188

MCQhard

A data engineer is reviewing the unification configuration in Dynamics 35 Customer Insights. What does this configuration accomplish?

A.Calculates average revenue

B.Predicts customer churn

C.Creates a segment of customers with email

D.Matches customer records by exact email

AnswerD

The matching rule uses exact matching on email.

Why this answer

The matching rule uses exact match on the email field to unify records. Option A is wrong because it doesn't segment. Option B is wrong because it doesn't create predictions.

Option C is wrong because it doesn't calculate measures.

Practice this question →

189

MCQeasy

A small business wants to unify customer data from their online store, email list, and social media interactions using Dynamics 365 Customer Insights. They have limited technical resources. What is the recommended first step?

A.Build segments based on customer location

B.Create measures to calculate key performance indicators

C.Enrich profiles with demographic data from a third-party provider

D.Ingest data from their existing sources and configure match rules

AnswerD

Data ingestion and matching are the first steps to create unified profiles.

Why this answer

The recommended first step is to ingest data from existing sources and configure match rules (Option D). This foundational step unifies customer profiles by matching and merging records from different sources, enabling further analysis. Options A, B, and C are premature: building segments (A) and creating measures (B) require unified profiles first, while enriching profiles with third-party data (C) is optional and best done after unification.

Practice this question →

190

Multi-Selecteasy

Which TWO activities are part of the data unification process in Dynamics 365 Customer Insights?

Select 2 answers

A.Creating segments based on customer attributes

B.Configuring match rules to identify duplicates

C.Mapping data fields from source systems

D.Defining measures for customer metrics

E.Enriching profiles with external data

AnswersB, C

Match rules are key to merging duplicate profiles.

Why this answer

Configuring match rules is a core step in the data unification process in Dynamics 365 Customer Insights. Match rules define the conditions (e.g., fuzzy matching on email or phone) used to identify duplicate customer records across source systems, enabling deduplication and merging into a single unified profile. This is distinct from segmentation or enrichment, which occur after unification.

Exam trap

The trap here is that candidates often confuse post-unification activities like segmentation or enrichment with the core unification steps, but Microsoft explicitly tests that match rules and field mapping are the two key activities within the unification process.

Practice this question →

191

MCQhard

A company wants to provide customer service agents with a 360-degree view of the customer including recent interactions, purchases, and sentiment. Which Dynamics 365 Customer Insights feature should they use?

A.Prediction models

B.Measures

C.Segments

D.Unified customer profile

AnswerD

The unified profile aggregates all customer data into one view.

Why this answer

The unified customer profile in Dynamics 365 Customer Insights aggregates data from multiple sources (e.g., sales, service, marketing) into a single, 360-degree view of each customer. This includes recent interactions, purchase history, and sentiment scores, enabling agents to see the complete customer journey. The other options focus on analytics or grouping, not on providing a holistic, real-time profile.

Exam trap

The trap here is that candidates often confuse 'segments' (grouping customers) with 'unified profiles' (individual customer view), leading them to pick Option C because they think a 360-degree view is about grouping data rather than consolidating it per customer.

How to eliminate wrong answers

Option A is wrong because prediction models are used to forecast future outcomes (e.g., churn likelihood), not to present a historical 360-degree view of customer data. Option B is wrong because measures are calculated metrics (e.g., total spend) that summarize data but do not provide a unified, entity-level profile with interaction details. Option C is wrong because segments are groups of customers defined by specific criteria (e.g., high-value customers), not a single customer's comprehensive view.

Practice this question →

192

MCQeasy

A marketer creates a segment in Dynamics 365 Customer Insights using the JSON shown. What will this segment contain?

A.Customers with low spending

B.Customers who have spent more than $10,000

C.Customers likely to churn

D.New customers acquired this month

AnswerB

The criteria is TotalSpend > 10000.

Why this answer

The JSON segment definition includes a condition that filters customers based on 'totalSpend' being greater than 10000. In Dynamics 365 Customer Insights, segments are built using attribute-based rules, and this JSON explicitly defines a numeric comparison on the 'totalSpend' field, which directly corresponds to customers who have spent more than $10,000.

Exam trap

The trap here is that candidates may confuse a static attribute-based segment (like spend threshold) with predictive segments (like churn) or time-based segments (like new customers), leading them to pick options that sound plausible but are not supported by the JSON condition shown.

How to eliminate wrong answers

Option A is wrong because the JSON condition uses 'gt' (greater than) 10000, not 'lt' (less than), so it targets high spenders, not low spenders. Option C is wrong because the segment is based on a static spending attribute, not on predictive churn models or propensity scores, which would require a different segment type (e.g., predictive segment) in Customer Insights. Option D is wrong because the JSON does not reference any acquisition date or time-based filter; it only checks a numeric spend threshold, not a recency or new customer attribute.

Practice this question →

193

Drag & Dropmedium

Drag and drop the steps to manage a case lifecycle in Dynamics 365 Customer Service into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

Case lifecycle includes creation, assignment, resolution, verification, and closure.

Practice this question →

194

Multi-Selectmedium

Which TWO actions can you perform using Customer Insights measures? (Choose two.)

Select 2 answers

A.Track monthly revenue trends

B.Create a segment of high-value customers

C.Unify customer records from multiple sources

D.Enrich customer profiles with demographic data

E.Calculate average order value per customer

AnswersA, E

Measures can compute time-series aggregates.

Why this answer

Measures in Customer Insights are used for calculations and aggregations, such as tracking revenue trends (A) and calculating average order value per customer (E). Creating segments (B), unifying customer records (C), and enriching profiles with demographic data (D) are separate features, not measures.

Practice this question →

195

MCQeasy

A user wants to export a segment of high-value customers from Customer Insights to Dynamics 365 Marketing to send a campaign. What is the recommended way to do this?

A.Use the Customer Insights API

B.Use the Dynamics 365 Marketing connector

C.Export the segment as a CSV file and import it

D.Use Power Automate to copy data

AnswerB

Built-in connector syncs segments automatically.

Why this answer

The Dynamics 365 Marketing connector is the recommended, native integration between Customer Insights and Dynamics 365 Marketing. It enables direct, real-time export of customer segments without manual steps, preserving data integrity and supporting automated campaign triggers. This built-in connector is the designed path for high-volume, low-latency segment sharing.

Exam trap

The trap here is that candidates often choose the CSV export (Option C) because it seems straightforward, but Microsoft explicitly recommends the connector for automated, reliable data synchronization in a Dynamics 365 ecosystem.

How to eliminate wrong answers

Option A is wrong because the Customer Insights API is a programmatic interface for custom integrations, not the recommended out-of-the-box method for exporting segments to Dynamics 365 Marketing; it requires custom development and lacks the automated synchronization features of the connector. Option C is wrong because exporting a segment as a CSV file and importing it is a manual, error-prone process that breaks the real-time data flow and is not the recommended approach for production campaigns. Option D is wrong because Power Automate can copy data but introduces unnecessary complexity and latency compared to the dedicated Marketing connector, which is purpose-built for this integration.

Practice this question →