MICROSOFT CERTIFICATION
MB-260 Dynamics 365 Customer Insights (Data) Specialty Practice Exam
Exam Number: 3124 | Last updated 16-Apr-26 | 795+ questions across 4 vendor-aligned objectives
The MB-260 Dynamics 365 Customer Insights (Data) Specialty certification validates the skills of data analysts and architects who implement Dynamics 365 Customer Insights – Data for unified customer profiles. This exam measures your ability to work with Dynamics 365 Customer Insights – Data, Azure Synapse Analytics, Power Query, Dataverse, Segments, Measures, demonstrating both conceptual understanding and practical implementation skills required in today’s enterprise environments.
The heaviest exam domains include Unify Customer Data (25–30%), Configure Source Data and Transformations (20–25%), and Enrich and Manage Customer Data (20–25%). These areas collectively represent the majority of exam content and require focused preparation across their respective subtopics.
Additional domains tested include Create Segments and Measures (15–20%), and Set Up Connections and Exports (10–15%). Together, these areas round out the full exam blueprint and ensure candidates possess well-rounded expertise across the certification scope.
Every answer links to the source. Each explanation below includes a hyperlink to the exact Microsoft documentation page the question was derived from. PowerKram is the only practice platform with source-verified explanations. Learn about our methodology →
376
practice exam users
92.3%
satisfied users
90.1%
passed the exam
4.2/5
quality rating
Test your MB‑260 D365 CI Data Specialty knowledge
10 of 795+ questions
Question #1 - Unify Customer Data
A retail chain has customer data in three systems: an e-commerce platform, a loyalty program, and in-store POS. The same customer may appear with slightly different names and emails across systems.
Which Customer Insights – Data capability resolves these duplicates into a single profile?
A) Import all records as separate profiles
B) Data unification with match rules on name, email, and phone using fuzzy matching
C) Delete duplicates from source systems first
D) Manual spreadsheet merging
Show solution
Correct answers: B – Explanation:
Data unification applies match rules with fuzzy matching to identify and merge records representing the same customer across sources. Manual merging does not scale. Separate profiles defeat the purpose. Deleting from sources risks losing data. Source: Check Source
Question #2 - Unify Customer Data
A retail chain has customer data in e-commerce, loyalty, and POS systems. The same customer may appear with slightly different names and emails.
Which CI-Data capability resolves these duplicates into a single profile?
A) Delete duplicate records from each source system before ingesting any data into CI-Data
B) Data unification with intelligent match rules using fuzzy matching on name, email, and phone
C) Import all records from every system as separate independent profiles without deduplication
D) Manual spreadsheet merging combining exported CSV files and removing duplicates by hand
Show solution
Correct answers: B – Explanation:
Data unification applies configurable match rules with fuzzy matching to identify and merge records representing the same customer across different source systems. Manual spreadsheet merging does not scale for large customer bases and lacks automated matching. Separate profiles without deduplication defeat the purpose of unified customer views. Deleting from source systems risks losing valid data and may not be feasible for production databases. Source: Check Source
Question #3 - Unify Customer Data
After unification, two clearly different customers are being merged because they share a common name. The match rule is too aggressive.
How should the team refine the unification?
A) Add conditions requiring both name AND email match with higher precision threshold settings
B) Remove all match rules entirely to prevent any false-positive merges from occurring
C) Accept the incorrect merge as an unavoidable limitation of automated matching systems
D) Switch to a completely different customer data platform to avoid the matching issue
Show solution
Correct answers: A – Explanation:
Tightening match rules by requiring multiple fields to match simultaneously and increasing precision thresholds reduces false-positive merges while maintaining valid matches. Accepting errors degrades customer data quality and downstream targeting accuracy. Removing all rules eliminates the unification capability entirely, creating duplicate profiles everywhere. Platform changes are disproportionate to a match rule configuration adjustment. Source: Check Source
Question #4 - Unify Customer Data
A bank needs to deduplicate customer records within a single source system before cross-source unification.
Which unification feature addresses same-source duplicates?
A) Only cross-source matching between different data sources is supported by the platform
B) Deduplication rules applied during unification processing on individual source entity tables
C) Export the source data, manually deduplicate in Excel, and reimport the cleaned dataset
D) Ignore within-source duplicates and address them only through cross-source matching logic
Show solution
Correct answers: B – Explanation:
Deduplication rules can be configured per source table to merge same-source duplicates before cross-source matching begins, improving overall profile quality. CI-Data does support within-source deduplication as a standard unification step. Manual export and reimport is not scalable for large banking customer databases. Ignoring within-source duplicates inflates customer counts and creates duplicate unified profiles. Source: Check Source
Question #5 - Configure Source Data and Transformations
A healthcare provider ingests patient data from Azure SQL Database with daily refresh and needs Power Query transformations to standardize date formats.
Which ingestion method should be used?
A) Power Query data source connector to Azure SQL with scheduled refresh and inline transforms
B) Azure Data Factory pipeline deployed independently with no integration to CI-Data platform
C) A direct database connection link with no transformation capability for date standardization
D) Manual CSV export from the SQL database uploaded to CI-Data through the browser each day
Show solution
Correct answers: A – Explanation:
Power Query connectors ingest from Azure SQL on a configurable schedule and apply inline transformations like date format standardization during the data loading process. Manual CSV export requires daily human effort and is error-prone. Direct connections without transformation leave date format inconsistencies that break unification rules. ADF without CI-Data integration requires additional custom development to land data in the platform. Source: Check Source
Question #6 - Configure Source Data and Transformations
Insurance policy data has a premium column containing both numeric values and text like “N/A”. The unification process fails on this column.
What should the data engineer configure?
A) Delete all rows containing N/A values from the source dataset before ingesting into CI-Data
B) Change the source system application to prevent N/A values from being entered going forward
C) Apply a Power Query transformation replacing N/A with null and casting the column to decimal
D) Ignore the premium column entirely and exclude it from all unification and enrichment steps
Show solution
Correct answers: C – Explanation:
Power Query transformations clean data at ingestion time — replacing invalid text values and type-casting ensures downstream unification and enrichment processes succeed. Deleting rows loses valid policy data for customers who happen to have N/A premiums. Excluding the column removes potentially useful enrichment and segmentation attributes. Source system changes may require significant application development and may not be feasible. Source: Check Source
Question #7 - Enrich and Manage Customer Data
A luxury brand wants to enrich profiles with brand affinity and demographic data not available in their own systems.
Which CI-Data feature provides third-party enrichment?
A) Purchasing a separate demographic dataset and importing it as an unrelated CI-Data source
B) Guessing demographic attributes from purchase history using simple rule-based assumptions
C) Manual per-customer internet research performed by a marketing team member for each profile
D) Built-in enrichment connectors using Microsoft and third-party providers like Experian
Show solution
Correct answers: D – Explanation:
CI-Data offers built-in enrichment connectors that append brand affinity, demographics, and interest data from trusted third-party providers to unified profiles automatically. Manual per-customer research does not scale for large customer databases. Separate dataset imports require additional unification configuration without the streamlined enrichment workflow. Rule-based guessing from purchases is unreliable and may introduce bias into targeting decisions. Source: Check Source
Question #8 - Enrich and Manage Customer Data
After enrichment, some profiles have conflicting data between the original source and the enrichment provider.
How should conflict resolution be configured?
A) Configure merge preferences prioritizing source system data with enrichment filling empty gaps
B) Delete all enriched fields entirely to eliminate any possibility of data conflict occurrence
C) Create separate customer profiles for enriched data maintaining them independently from originals
D) Always trust the enrichment provider data overwriting original source system values entirely
Show solution
Correct answers: A – Explanation:
Merge preferences specify data source priority so trusted original data takes precedence while enrichment values fill gaps in empty fields without overwriting. Always trusting external data may overwrite accurate internally managed records. Deleting enrichment wastes the investment in third-party data acquisition. Separate profiles fragment the unified customer view that CI-Data is designed to create. Source: Check Source
Question #9 - Create Segments and Measures
A marketing team needs a segment of high-value customers who spent over $5,000 last year with fewer than two support interactions.
Which CI-Data feature should the marketer use?
A) A static list manually compiled by exporting customer data and filtering in Excel spreadsheets
B) A Power BI visual filter applied to a dashboard showing high-value customers interactively
C) A dynamic segment built with compound conditions on unified spending and support activity data
D) An Excel pivot table created from exported CI-Data records and manually updated each week
Show solution
Correct answers: C – Explanation:
Dynamic segments evaluate conditions on unified profiles and related activity entities, automatically updating membership as customer data changes daily. Static lists become stale immediately after creation and require manual refresh. Power BI filters visualize data interactively but do not create exportable audience segments for campaign targeting. Excel pivot tables are disconnected from the platform and require manual weekly maintenance effort. Source: Check Source
Question #10 - Create Segments and Measures
A subscription business needs a customer-level measure calculating total lifetime revenue from all orders for each unified profile.
Which CI-Data capability should be used?
A) A manual calculation performed per customer and entered into a custom attribute on each profile
B) A customer measure aggregating total order amounts across the relationship to each unified profile
C) A calculated column formula added to the Orders source entity table computing per-order totals
D) A Power Automate flow summing order values for each customer and writing results to a field
Show solution
Correct answers: B – Explanation:
Customer measures aggregate related entity values like total order amount to the unified profile level, available for segmentation, enrichment, and export targeting. Calculated columns operate at the entity row level, not aggregated to the customer profile. Power Automate flows running per-customer are inefficient for bulk aggregation across thousands of profiles. Manual per-customer calculations do not scale and become immediately outdated with new orders. Source: Check Source
Get 795+ more questions with source-linked explanations
Every answer traces to the exact Microsoft documentation page — so you learn from the source, not just memorize answers.
Exam mode & learn mode · Score by objective · Updated 16-Apr-26
Learn more...
What the MB‑260 D365 CI Data Specialty exam measures
- Unify Customer Data (25–30%) — Evaluate your ability to implement and manage tasks within this domain, including real-world job skills and scenario-based problem solving.
- Configure Source Data and Transformations (20–25%) — Evaluate your ability to implement and manage tasks within this domain, including real-world job skills and scenario-based problem solving.
- Enrich and Manage Customer Data (20–25%) — Evaluate your ability to implement and manage tasks within this domain, including real-world job skills and scenario-based problem solving.
- Create Segments and Measures (15–20%) — Evaluate your ability to implement and manage tasks within this domain, including real-world job skills and scenario-based problem solving.
- Set Up Connections and Exports (10–15%) — Evaluate your ability to implement and manage tasks within this domain, including real-world job skills and scenario-based problem solving.
How to prepare for this exam
- Review the official exam guide to understand every objective and domain weight before you begin studying
- Complete the relevant Microsoft Learn learning path to build a structured foundation across all exam topics
- Get hands-on practice in an Azure free-tier sandbox or trial environment to reinforce what you have studied with real configurations
- Apply your knowledge through real-world project experience — whether at work, in volunteer roles, or contributing to open-source initiatives
- Master one objective at a time, starting with the highest-weighted domain to maximize your score potential early
- Use PowerKram learn mode to study by individual objective and review detailed explanations for every question
- Switch to PowerKram exam mode to simulate the real test experience with randomized questions and timed conditions
Career paths and salary outlook
Earning this certification can open doors to several in-demand roles:
- Customer Data Platform Specialist: $95,000–$130,000 per year (based on Glassdoor and ZipRecruiter data)
- CRM Data Analyst: $85,000–$120,000 per year (based on Glassdoor and ZipRecruiter data)
- Customer Insights Architect: $110,000–$145,000 per year (based on Glassdoor and ZipRecruiter data)
Official resources
Microsoft provides comprehensive free training to prepare for the MB-260 Dynamics 365 Customer Insights (Data) Specialty exam. Start with the official Microsoft Learn learning path for structured, self-paced modules covering every exam domain. Review the exam study guide for the complete skills outline and recent updates.