SF-Data-Arch Master Data Management Practice Question
Which of the following is a classic symptom of poor Master Data Management in a Salesforce ecosystem?
⚠ Common exam trap
Candidates often look for technical symptoms like 'API errors' or 'slow page loads' rather than identifying business-level symptoms such as departmental silos and conflicting data views.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Sales and Marketing teams having conflicting views of the same customer.
Fragmented data silos often result in the same customer existing as multiple records across different systems (e.g., Salesforce, SAP, and Marketing Cloud). This leads to poor customer service, conflicting marketing messages, and inaccurate financial reporting. Identifying these symptoms is critical for a Data Architect to justify the investment in an MDM solution, as these issues directly impact the bottom line through operational inefficiency and missed sales opportunities.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Salesforce users reporting that their dashboards load slowly.
Why it's wrong here
Slow dashboards are typically a performance issue caused by inefficient SOQL queries, large report result sets, or complex data models. They are not an indicator of data quality or consistency issues, which are the core concerns of MDM, but rather a reflection of technical configuration and system optimization problems.
- ✓
Sales and Marketing teams having conflicting views of the same customer.
Why this is correct
When teams rely on disparate, un-synchronized data sources, they often have different versions of the truth for a single customer. This lack of a unified golden record leads to disconnected customer experiences, such as marketing sending promotional emails to a customer who has already churned in the CRM.
- ✗
Excessive use of Apex triggers that cause governor limit exceptions.
Why it's wrong here
Governor limit exceptions are a sign of suboptimal code architecture, such as performing DML inside loops or writing inefficient logic. While bad data can trigger excessive code execution, the root cause here is technical implementation and code quality, not the absence of an enterprise master data management strategy.
- ✗
Users forgetting their passwords frequently, requiring support tickets.
Why it's wrong here
Identity and Access Management (IAM) issues are related to security and user management. While authentication is a critical component of Salesforce, it has nothing to do with the quality, consistency, or lifecycle management of the business entities, which is the specific domain of Master Data Management.
About these practice questions
This SF-Data-Arch question is part of Courseiva's 222-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Data-Arch practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Data-Arch exam.